gitlisted

Load when planning or about to git commit, branch, push, rebase, resolve a merge conflict, open PR, stack PR, or write/update the description of a Pull Request (PR / stacked diff), respond to review comments, review a PR, or watch/babysit a PR's CI. Carries the user's git conventions and style you are expected to match. Load as early as possible, the moment git or GitHub work is anywhere in the chat's future.
sherifabdlnaby/skills · ★ 6 · Code & Development · score 71

Install: claude install-skill sherifabdlnaby/skills

# 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, restacking (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, empty commits, CI refresh. **Pull Requests** (open, update) -> [`references/pull-requests.md`](references/pull-requests.md) Title format (including stacked PRs), body format, how to write descriptions, AI footers, post-create flow, linking PRs. **Responding to review comments** (on your own/target PR) -> [`references/review-responses.md`](references/review-responses.md) Classify the reviewer (automated bot/AI tool, an AI-disclosed agent behind a human account, or a human), then fix / push back / escalate; replies, thread resolution, re-requesting review. **Rebasing, squashing, resolving conflicts** -> [`references/rebase.md`](references/rebase.md) Backup-branch convention, force-with-lease, range-diff verification, conflict procedure, non-interactive squash recipes. Stacked-PR restack mechanics and `--ont