Skip to content

alisterpineda/git-workflow

v0.22.1MIT

Deprecated: commit-message and pr-description moved to swe (pr-description as pr-writeup); review is partly superseded by swe:code-review; conflict-triage has no successor. Its skills still work but get no further updates. Git-related skills: commit staging and message conventions, PR title and description generation, adversarial multi-perspective code review, merge/rebase conflict triage and resolution.

commit-message

Deprecated — if swe:commit-message is available, use it instead of this skill. Defines how git commits should be handled — what to stage, how to format the message, and how to run the commit. Use this skill whenever the user asks to commit changes, make a commit, or write a commit message — even if they don't mention formatting or staging. This ensures commits only include relevant changes and follow the user's preferred message style.

conflict-triage

Deprecated, with no successor — this skill still works but gets no further updates. Triages conflicts from a merge, rebase, cherry-pick, revert, or stash pop — or predicts them for a GitHub / Azure DevOps pull request — and reports a per-file resolution plan with its risks. Read-only unless --fix is passed. Usage: /git-workflow:conflict-triage [--fix] [target]. Flags come before the target. User-invoked only — never invoke this skill on your own initiative.

pr-description

Deprecated — if swe:pr-writeup is available, use it instead of this skill. Generates a pull-request title and description based on the diff between a source and target branch. Use this skill whenever the user asks to create, write, draft, or generate a PR title, PR description, pull request message, or pull-request summary — even if they phrase it casually like "write me a PR" or "what should the PR say".

review

Deprecated — superseded by /swe:code-review; this skill still works but gets no further updates. Adversarial multi-perspective code review. Spawns independent reviewer agents (correctness, security, maintainability, tests, performance), sharpened by domain lenses where the diff calls for them, then puts every finding through a skeptic verification pass before reporting. Report-only. With no target, reviews the staged changes — or all uncommitted changes if nothing is staged. Small diffs get a reviewer budget scaled to their size, with perspectives beyond it folded into the reviewers that run; --full lifts the budget. User-invoked only — never invoke this skill on your own initiative.