commits-and-prs
Skill5 starsChanged 15 days agoMITView on GitHub
How to split work into commits, write commit messages, and prepare and describe pull requests. Use when committing, writing a commit message, opening or describing a pull request, or splitting a large change.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- manuelLandreau/claude-skillstheir own version, first seen Oct 11, 2026
- stormlightlabs/thunderustheir own version, first seen Sep 19, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- stormlightlabs/thunderus★ 4same name
- manuelLandreau/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- context-mdSkill
- debuggingSkill
- diagramsSkill
- implementationSkill
- project-profileSkill
- project-scanSkill
- session-retroSkill
- task-plansSkill
- tddSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 12
Check the project's conventions before applying this skill: recent messages (git log --oneline -20), a pull request template …
- Distinctive: line 16
Commit, push or open a pull request only when the user asked for it.
- Distinctive: line 17
Never force-push a shared branch or rewrite pushed history without the user's explicit agreement.
- Very specific: line 18
Never skip hooks (--no-verify).
- Distinctive: line 30
Don't narrate the process ("fixed tests", "addressed review") or list the files changed.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- From agentic-defaults. Kit updates replace this file except a "## This project" section at the end, which belongs to the project. Edit nothing else. Rules for all work go in AGENTS.md "This project". -->Commits and pull requests
Follow the project first
Check the project's conventions before applying this skill: recent messages (git log --oneline -20), a pull request template (.github/pull_request_template.md), and CONTRIBUTING.md. Where they differ from this skill, the project wins.
Safety
- Commit, push or open a pull request only when the user asked for it.
- Never force-push a shared branch or rewrite pushed history without the user's explicit agreement.
- Never skip hooks (
--no-verify). If a hook fails, fix the cause.
Commits
- One logical change per commit. Tests go in the same commit as the code they test. Keep refactoring, formatting and behavior changes in separate commits.
- Every commit builds and passes the tests, so the history stays usable for
git bisectand reverts. - Stage by path and check what you're committing (
git diff --staged). Leave out secrets, local configuration, generated files, debug code, commented-out code and unrelated changes.
Commit messages
- Subject: imperative mood, under about 60 characters, no full stop. Say what the change does: "Reject expired tokens in session middleware", not "Fix bug" or "Update auth.ts".
- Body, only when the reason isn't obvious from the subject: why the change was needed, what alternative you rejected, and any side effects. Wrap at about 72 characters. Reference the issue if there is one.
- Don't narrate the process ("fixed tests", "addressed review") or list the files changed; the diff shows that.
Pull requests
- One purpose per pull request, small enough to review in one sitting. Split larger work: put preparatory refactoring in its own pull request first, then the feature.
(production): hide unfinished features behind a switch rather than holding back a huge branch. - Before opening one, bring the branch up to date, run the tests, read your own diff once as a reviewer would, and update any affected
CONTEXT.md. - Title: written like a commit subject.
- Description: short, with only the sections that apply:
## What and why
Two to four sentences. Link the issue.
## How it was verified
Tests added, commands run and their results, manual steps. Screenshots for UI changes.
## Risks and rollout
Migrations, configuration changes, feature flags, backwards compatibility.
## Notes for reviewers
Where to start reading, what deserves a close look, and what is deliberately out of scope.- Review comments: answer every one, either with a change or with a reason for not changing.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

