commit
Skill309 starsChanged 4 months agoApache-2.0View on GitHub
Lint, run the pre-PR checks, commit, push, and author or update the branch's pull request in the required plain-text format. Use when committing, pushing, or creating/updating a PR.
- Reads credentials
- Commits and pushes
187 other projects use a version of this.
Adopted by
Most recently taken up by
- yagizdo/quivertheir own version, first seen Nov 15, 2026
- markmhendrickson/neotomatheir own version, first seen Nov 15, 2026
- ShipfoxHQ/shipfoxtheir own version, first seen Nov 15, 2026
- atomicinnovation/acceleratortheir own version, first seen Nov 14, 2026
- Integralist/agent-skillstheir own version, first seen Nov 14, 2026
- gtapps/claude-code-hermittheir own version, first seen Nov 13, 2026
Used with
Projects with it also use validate-plan, act-on-feedback and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
shawn-dumasSkillvalidate-plan
Validate an orchestration plan after pre-flight certification. Runs adversarial review, deep review (verify prompt data against codebase), and PoC gate for risky approaches. Auto-invoked by orchestrate-* skills at Step 8.
Also in 5 projects that use this
MicrosoftSkillact-on-feedback
Act on user feedback attached to the current session. Use when the user submits feedback on the session's changes via the Submit Feedback button.
Also in 3 projects that use this
decocmsSkilladd-mcp-tools
Guide for adding new MCP tools with consistent patterns for schemas, tool definitions, registry updates, and Better Auth integration
Also in 3 projects that use this
MicrosoftSkillgenerate-run-commands
Generate or modify run commands for the current session. Use when the user wants to set up or update run commands that appear in the session's Run button.
Also in 3 projects that use this
mitsuhikoSkilloebb-scotty
Austrian rail travel planner (ÖBB Scotty). Use when planning train journeys in Austria, checking departures/arrivals at stations, or looking for service disruptions. Covers ÖBB trains, S-Bahn, regional trains, and connections to neighboring countries.
Also in 3 projects that use this
mitsuhikoSkillpi-share
Load and parse session transcripts from shittycodingagent.ai/buildwithpi.ai/buildwithpi.com/pi.dev (pi-share) URLs. Fetches gists, decodes embedded session data, and extracts conversation history.
Also in 3 projects that use this
Other versions187 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 187
- microsoft/vscode★ 195ksame name
- TryGhost/Ghost★ 56ksame name
- ToolJet/ToolJet★ 41ksame name
- ShareX/ShareX★ 41ksame name
- openai/symphony★ 27ksame name
- ryoppippi/ccusage★ 19ksame name
- ccusage/ccusage★ 19ksame name
- windmill-labs/windmill★ 19ksame name
- EverMind-AI/EverMemOS★ 14ksame name
- EverMind-AI/EverOS★ 14ksame name
177 more not listed
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 repository50 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- analyze-datagen-campaign-summarySkill
- analyze-dataset-token-lengthSkill
- analyze-id-eval-rankingSkill
- analyze-job-history-irisSkill
- analyze-rl-behaviorSkill
- analyze-training-run-irisSkill
- build-tpu-image-irisSkill
- code-create-staged-planSkill
- code-execute-staged-planSkill
- crud-archive-runSkill
- crud-otagent-supabaseSkill
- crud-purge-below-gate-evalsSkill
- crud-purge-stale-eval-placeholdersSkill
- datagen-create-task-datasetSkill
- datagen-job-cleanupSkill
- datagen-launch-irisSkill
- datagen-launchSkill
- datagen-reduce-dataset-snapshotsSkill
- datagen-standard-launchSkill
- debugSkill
- docs-deslopSkill
- eval-agentic-cleanupSkill
- eval-agentic-launch-irisSkill
- eval-agentic-launchSkill
- eval-standard-cleanupSkill
- eval-standard-launchSkill
- file-issueSkill
- monitor-cron-sweep-irisSkill
- monitor-cron-sweepSkill
- monitor-job-tablesSkill
- monitor-restore-irisSkill
- monitor-restoreSkill
- monitor-restore-unifiedSkill
- rl-agentic-job-cleanupSkill
- rl-agentic-launch-irisSkill
- rl-agentic-launch-jupiterSkill
- rl-job-health-deep-diveSkill
- rl-standard-job-cleanupSkill
- rl-standard-launch-leonardoSkill
- serve-model-vibe-testSkill
- sft-cleanup-hf-onlySkill
- sft-job-cleanupSkill
- sft-launchSkill
- supervisor-initSkill
- utils-cleanup-stale-sandboxesSkill
- utils-fix-permissionsSkill
- utils-reclaim-stale-snapshotsSkill
- write-testsSkill
- writing-styleSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. 0 are common, 11 are distinctive, and 9 are very specific to this project.
0
Common
Most of the 167 edited versions we read keep these.
11
Distinctive
This author's own choices. Worth a look.
9
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
- Distinctive: line 13
Before authoring a commit or PR title or body, read:
- Distinctive: line 36
Commit. ← natural checkpoint.
- Distinctive: line 43
Read your own git diff before anything else.
- Very specific: line 48
If the diff touches tests and this commit is intended for a PR or review, read TESTING.md as part of this self-review.
- Very specific: line 70
Run the repo's test command over the test directories your change touches (e.g.
- Distinctive: line 72
If the change is docs-heavy, build the docs and fix any broken links or strict-mode failures.
- Very specific: line 81
Never stage secrets (.env, credentials, tokens).
- Distinctive: line 82
If unrelated changes are present, ask the user before including them.
- Very specific: line 91
Do not use a conventional-commit prefix such as feat: or fix:.
- Very specific: line 92
No emoji, no markdown, no bullets in the subject.
- Distinctive: line 100
Create the commit. If a pre-commit hook fails, fix the issue and make a new commit — never amend (unless the user asks) and never …
- Distinctive: line 112
Run this after the commit and before opening a PR.
- Distinctive: line 125
If asked, or if the branch has an upstream, push to the remote tracking branch (git push -u origin HEAD if no upstream is set).
- Very specific: line 131
Do this once the branch is ready for review.
- Very specific: line 151
Issue linking: If the work came from a GitHub issue, add Fixes #NNNN (auto-closes on merge) or Part of #NNNN (partial work).
- Very specific: line 173
Always add the agent-generated label.
- Distinctive: line 174
Never credit yourself in commits or PR descriptions.
- Very specific: line 200
Commit before you run --review.
- Distinctive: line 201
Never amend a commit unless the user explicitly asks.
- Distinctive: line 202
If there are no changes to commit, say so and stop.
“Common” is measured: kept by at least 6 in 10 of the 167 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- Vendored from marin-community/marin-style v0.3.0 — do not edit; re-run `marin-style sync`. -->Skill: Commit & PR
Get the branch clean, commit it, run the advisory lint review over the committed diff, then — when it is ready — open or update the pull request.
Before authoring a commit or PR title or body, read:
.agents/skills/writing-style/SKILL.md.agents/skills/writing-style/pull-requests.md.agents/skills/writing-style/ai-writing-donts.md
Order matters. Your own cleanups and the mechanical fixes come first, then the
commit, and only then the --review pass. Committing before the review gives
you a clean checkpoint to review against (the review reads the whole branch diff
versus the merge base) and a natural place to land any follow-up fixes as a new
commit. The review is read-only: it never edits, commits, or pushes for you.
Checklist
Work top to bottom. For a quick work-in-progress checkpoint, do 1, 2, 4, 5, 7 (clean up, lint, stage, commit, push) and stop. The changed-test cleanup in step 1 is a PR-readiness gate, not required for disposable WIP checkpoints. Run the whole list before you open or update a PR.
- Clean up your own diff (self-review).
- Mechanical lint & format —
infra/pre-commit.py --changed-files --fix. - Tests & docs checks, when relevant.
- Stage the specific files for this work.
- Commit. ← natural checkpoint; the working tree is now clean.
- Lint-catalog review —
infra/pre-commit.py --review; fix or answer every finding. - Push (maybe).
- Open or update the PR.
1. Clean up your own diff
Read your own git diff before anything else. Drop dead code, debugging
leftovers, and stale comments; tighten names; make the change say only what it
means to. The review in step 6 is advisory and read-only — it will not clean up
for you.
If the diff touches tests and this commit is intended for a PR or review, read
TESTING.md as part of this self-review. Review every changed test for slop:
tautological assertions, disposable smoke probes left as pytest tests, internal
call-count assertions, incidental string or command-fragment assertions,
over-mocking, weakened tolerances, sleeps, skipped tests, and marker/fake/mock
violations.
Fix or delete low-value tests before a PR-ready commit. Scratch probes are fine during development and WIP checkpointing, but they must not survive into a PR.
2. Lint and format
infra/pre-commit.py --changed-files --fix # diff-scoped; use --all-files for a full sweepinfra/pre-commit.py is the required entry point — never uv run pre-commit,
never --no-verify. If --fix cannot resolve something, fix it by hand. Do not
skip or weaken checks.
3. Tests and docs checks (when relevant)
- Run the repo's test command over the test directories your change touches
(e.g.
uv run pytest -m 'not slow'). - If the change is docs-heavy, build the docs and fix any broken links or strict-mode failures.
4. Stage changes
Review git status and git diff, then stage the specific files that are part
of this work.
- Stage specific files — avoid
git add -A/git add .. - Never stage secrets (
.env, credentials, tokens). - If unrelated changes are present, ask the user before including them.
5. Commit
- Subject: imperative sentence (at most 72 characters), optional
[scope]prefix. - Body (optional, blank-line separated): what changed and why — the context a future reader needs. Keep relevant evidence and caveats; do not inventory files or tests.
- Do not use a conventional-commit prefix such as
feat:orfix:. - No emoji, no markdown, no bullets in the subject. Do not credit yourself —
this includes any
Co-Authored-By,Generated with, provider, or session URL trailer. Omit it even if a harness default suggests adding one.
Review the exact message before committing. After the commit, inspect it with
git show -s --format='%s%n%n%b' HEAD; do not push if a tool added attribution,
a session trailer, or other text that was not in the reviewed message.
Create the commit. If a pre-commit hook fails, fix the issue and make a new commit — never amend (unless the user asks) and never force-push.
This is the checkpoint the rest of the flow builds on: the working tree is clean and the branch diff is settled before the review reads it.
6. Lint-catalog review (before every PR)
infra/pre-commit.py --reviewRun this after the commit and before opening a PR. It fans out read-only agents over the branch diff against the merge base with the default branch — committed and uncommitted work alike — so the clean checkpoint from step 5 is exactly what gets reviewed.
The review is advisory and read-only: it reports findings on stdout and does not edit, stage, commit, or push anything. Then fix or answer every finding, reporting your actions to the user, and land any fixes as a new commit. Treat findings as guidelines — apply them when they make the code better; the goal is high-quality code, not blind adherence.
7. Push
If asked, or if the branch has an upstream, push to the remote tracking branch
(git push -u origin HEAD if no upstream is set). If the push is rejected
(diverged history), stop and ask the user — do not force-push.
8. Open or update the PR
Do this once the branch is ready for review. The PR description becomes the
squash-merge commit message. Follow
.agents/skills/writing-style/pull-requests.md exactly: an imperative title of
at most 72 characters and an information-dense body. Most bodies are a few plain
paragraphs. They state what changes and why; they do not reproduce the diff,
test plan, or implementation notes.
Example:
Title: [RL] Normalize DAPO loss over global tokens
Body:
Normalize DAPO loss over all response tokens instead of normalizing each
example separately. Per-example normalization over-weights short responses,
hurting math tasks where correct answers need longer derivations.
Fixes #1234Issue linking. If the work came from a GitHub issue, add Fixes #NNNN
(auto-closes on merge) or Part of #NNNN (partial work). Do not invent an issue
just to satisfy this — omit the link when none exists.
Specifications (>500 LOC only). A genuinely large PR must link a spec in an issue or design doc. Name the important design decisions in the PR body and link the spec for module maps, code excerpts, and detailed rationale.
Inspect the payload. Draft the body in a uniquely named temporary file and
use --body-file. Re-open that file and apply the final compression pass before
publishing. After creating or editing the PR, fetch the exact title,body with
gh pr view --json title,body and immediately correct text inserted by a tool
or stale template.
Create it. Unless the user says otherwise and permissions allow, push to a branch on the main repository and open the PR from it (use a fork only when direct push is unavailable or the user asks):
gh pr create --title "<title>" --body-file "<body-file>" --label agent-generated- Always add the
agent-generatedlabel. - Never credit yourself in commits or PR descriptions.
- Include
Fixes #NNNNwhen addressing a pre-existing issue.
9. Monitor the PR
Opening the PR does not end your turn. Watch CI to completion and respond to review activity until the PR is merged or closed, or the user tells you to stop.
- Watch checks with
gh pr checks <N> --watch. When a check finishes, read its conclusion — finishing is not passing. - On a CI failure, read the failing job log and fix it. A failure in a file you did not touch is not automatically pre-existing: confirm the same job fails on the default branch without your change before calling it unrelated. If your change caused it — even in an untouched file — fix it. Push the fix as a new commit, which restarts CI.
- Respond to every human and agent comment: address obvious ones directly (commit
the fix, then reply, prefixing agent replies with
🤖) and resolve them. CI being green does not mean there is nothing to do — reviewers comment after CI passes. For comments you are unsure about, report your analysis and proposed action to the user.
Exit conditions: the PR is merged or closed, or the user tells you to stop.
Rules
infra/pre-commit.pyis the only pre-commit entry point.- Commit before you run
--review; the review never commits, pushes, or edits. - Never amend a commit unless the user explicitly asks.
- If there are no changes to commit, say so and stop.
AGENTS.md— coding guidelines.
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.

