Git shipping
my agent skills
npx -y skills add h3y6e/agent-skills --skill git-shippingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when making code changes in a git repo, switching branches, or when asked to `push`, `commit`, `pr`, or manage branches. Use before starting implementation to confirm you're on the right branch.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.9 KB, 610 tokens by cl100k_base, as published. Nobody here has run it
Git Shipping
Code changes flow through: branch → commit → push → PR.
Intent Expansion
Treat short git requests as workflow shorthand.
| User says | What it means |
|---|---|
commit | Inspect, stage coherent chunks, commit |
push | Inspect, create commits if needed, push |
pr | Inspect, move off default branch if needed, commit, push, open PR |
Ask only when the intended change scope is unclear enough that you might include unrelated work.
Language Rule
Check visibility with gh repo view --json visibility -q '.visibility'.
- PUBLIC: Use English for commit messages, PR titles, and PR bodies.
- PRIVATE / INTERNAL: Use the language the user is currently using.
Branch
Start new feature work in a clean worktree from the remote default branch, not in the default-branch checkout.
Before creating it, check git wt -h, then use git wt <branch> origin/<default-branch> --nocd.
Never call raw git worktree.
Do not move already-started work into a new worktree just to satisfy this workflow. If files are already being edited in the current checkout, keep working there and create or switch to the appropriate branch in place when safe.
Commit
REQUIRED SUB-SKILL: Use cxg skill for commit message format.
Pull Request
- PR titles use Conventional Commit subject format:
type(scope): subject. - Prefer a repository PR template when one applies.
- Without a template, use only:
## Summary,## Background,## Changes, optional## Impact. - Use
## Impactonly for merge behavior changes. Omit unchanged behavior, non-goals, and work not done. - Do not add ad hoc
Testing,Verification,Checklist,Related issues, orScreenshots. Never dump local verification commands into the PR body. - New PRs default to draft (
gh pr create --draft); preserve existing PR draft/ready state unless asked.
Common Mistakes
| Mistake | Fix |
|---|---|
| Starting new work on the default branch | Create a clean feature worktree |
| Moving already-started work just to satisfy this workflow | Keep the current checkout; branch in place when safe |
| Copying modified or untracked files into new worktrees by default | Create clean worktrees; transfer in-progress changes only on request |
Treating push / commit as one git command | Follow Intent Expansion |
| Using a prose PR title | Use Conventional Commit subject format: type(scope): subject |
Using raw git worktree | Use git wt <branch> origin/<default-branch> --nocd; check git wt -h first |
Skipping cxg lint | Pipe through cxg lint before committing |
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most pr commit review skills give in 610 tokens
Counted across 888 of the 1,342 authors here whose files we hold, read 2026-08-07
- Use conventional commits formatin 127 of 888, across 115 files
- Keep subject line under 72 charactersin 62 of 888, across 48 files
- Delete branches after mergein 51 of 888, across 38 files
- Use imperative mood in subject linein 51 of 888, across 42 files
- Use imperative mood in commit messagesin 44 of 888
- Verify directory is ignored before creating worktreein 43 of 888, across 12 files
- Generate a conventional commit messagein 43 of 888
- Add unignored worktree directories to gitignorein 42 of 888, across 10 files
- Make atomic commitsin 39 of 888, across 27 files
- Run tests before committingin 36 of 888, across 25 files
- Verify clean test baselinein 35 of 888, across 9 files
- Split unrelated changes into separate commitsin 35 of 888, across 30 files
Said here and by no other author read
- treat short git requests as workflow shorthand
- match PR language to repository visibility
- create new work from the remote default branch
- use the cxg skill for commit messages
- omit unneeded sections from the PR body
- restrict impact section to merge behavior changes
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.