cross-synthlisted

# /cross-synth - Cross-Synthesis Compare any N subjects (repos, files, documents, configs, processes, features, test suites) side-by-side. Find what's shared, what's missing, what's inconsistent, and what one subject can teach the others. **This is horizontal analysis.** `/deep-dive` goes deep on one thing. `/cross-synth` goes wide across many. --- ## When to use - "Do RepoA and RepoB handle auth the same way?" - "Cross-synthesise the test coverage across all three repos" - "Compare the error handling patterns across these files" - "What can RepoA's upload deduplication teach RepoB?" - "Are our security controls consistent across tools?" - "Compare how each tool handles config validation" - "Any time I want to know if the other repos are doing something the same as/better than this one" --- ## Input parsing - **No args:** Ask what to compare (subjects or theme). - **`/cross-synth [theme]`:** Cross-synthesise a specific theme (e.g. `auth`, `error-handling`, `config`, `security`). - **`/cross-synth <subject1> [subject2] [...]`:** Compare the listed subjects. Can be repos, file globs, doc paths, or abstract topics. - **`/cross-synth [description of what to compare]`:** Natural language works - parse the intent and proceed. --- ## The Process (5 phases) ### Phase 1 - Inventory For each subject, collect the raw material: - Code: grep for patterns, function signatures, class names, test names - Docs: read the key sections - Config: read the schema and defaults - Tests: