stitchlisted

# /stitch — Cross-repo stitch layer Generate a cross-repo binding artifact (`STITCH.md`) for a product group (backend + one or more frontends). Tables only, not narrative. Drift detection uses CODEMAP endpoint sections by default with explicit opt-in fallback to grep. ## Step 0: Load config <!-- shared-block: group-loader --> Read `~/.claude/aria-knowledge.local.md`. Parse YAML frontmatter `projects_groups` (multi-line YAML block — see `CONFIG.md` "Skill-only fields" for canonical schema, including the optional `stitch_path` sub-field and custom-role conventions). Look up `<tag>` in `projects_list` (get `project_root`) and `projects_groups` (get role → folder dict). - If `<tag>` missing from `projects_list`: stop with *"unknown project tag: <tag>"*. - If `<tag>` in `projects_list` but missing from `projects_groups` and `<project_root>` has multiple sub-dirs with repo markers: trigger **auto-propose bootstrap**. - If `<tag>` is a single-repo project (no multi-repo sub-dirs detected): load `<project_root>/CODEMAP.md` only. **Auto-propose bootstrap** (when `projects_groups[<tag>]` is missing but `<project_root>` contains multiple repo-marker sub-directories): 1. Scan `<project_root>` one level deep for sub-directories with repo markers: - `manage.py` + `settings.py` → `backend` (Django) - `composer.json` + `artisan` → `backend` (Laravel) - `Gemfile` with `rails` → `backend` (Rails) - `package.json` with `express`/`fastify`/`nestjs` → `backend` (Node) - `next