gitlisted

# Git Route first: each action's actual rules live in a `references/` file. Open the matching one before planning or acting; rules like commit grouping and branch naming shape the plan, so reading them late means redoing it. Several actions, several references. ## Router **Branches** (create, name, stack) -> [`references/branches.md`](references/branches.md) Switching branches, naming rules, ticket references, switching with a dirty tree, stacked PRs (conventions here, mechanics via the gh-stack skill), the gh-stack/manual path probe, cascade conflicts and verification, manual restacking fallback (after merge, chain of 3+, mid-stack push), force-pushing. **Committing** -> [`references/commits.md`](references/commits.md) Pre-staging walk, file confirmation, message style, hook-failure handling, scoping, editor-free squash, empty commits. **Pull Requests** (open, update) -> [`references/pull-requests.md`](references/pull-requests.md) Pre-flight survey, title format (including the stacked `[n/N]` marker), body skeleton and how to write descriptions, `--attach` exists on create/edit/comment, when a screenshot or video is worth attaching, AI footers, post-create flow, finishing PRs after `gh stack submit`, linking PRs, updating a body without clobbering it. **Attach a screenshot or video** -> [`references/attach.md`](references/attach.md) `--attach` on create/edit/comment, body-file placement, screenshot framing guidance. **Responding to review comments** (on your own/targe