review-and-ship
Skill0 starsChanged 15 days agoMITView on GitHub
Review the current branch for bugs, intent fit, and test coverage; run or write tests; commit focused work; open or update a PR.
6 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- upamune/skillsword for word, first seen Nov 15, 2026
- catesandrew/skillsedited, first seen Nov 8, 2026
- ArthurMor4is/skillstheir own version, first seen Nov 1, 2026
- dhanji4U/skillsedited, first seen Oct 2, 2026
- ElyzeSolutions/skillsword for word, first seen Aug 6, 2026
- cogine-ai/cogine-dev-skillsetword for word, first seen Jun 25, 2026
Other versions6 projects use a version of this.
Word for word · 3
- cogine-ai/cogine-dev-skillset★ 3100% same
- ElyzeSolutions/skills★ 1100% same
- upamune/skills★ 1100% same
Edited · 2
- dhanji4U/skills★ 285% same
- catesandrew/skills★ 185% same
Wrote their own version · 1
- ArthurMor4is/skills★ 1same 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 repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- check-compiler-errorsSkill
- control-cliSkill
- control-uiSkill
- deslopSkill
- fix-ciSkill
- fix-merge-conflictsSkill
- get-pr-commentsSkill
- loop-on-ciSkill
- make-pr-easy-to-reviewSkill
- new-branch-and-prSkill
- pr-review-canvasSkill
- run-smoke-testsSkill
- thermo-nuclear-code-quality-reviewSkill
- verify-thisSkill
- weekly-reviewSkill
- what-did-i-get-doneSkill
- workflow-from-chatsSkill
The file
We split this skill into the rules it gives an agent
5 rules. 4 are common, 0 are distinctive, and 1 is very specific to this project.
4
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 15
Run targeted tests for changed behavior.
- Common: line 18
Commit selective files with a concise message.
- Common: line 33
Keep commits focused and avoid unrelated file changes.
- Common: line 34
If pre-commit checks fail, fix the issues rather than bypassing hooks.
- Very specific: line 35
Use gh pr checks instead of GitHub Actions-only commands when judging PR readiness.
“Common” is measured: kept by at least 6 in 10 of the 3 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
Review and ship
Trigger
Reviewing changes before shipping. Close key issues, verify behavior, and open or update a PR.
Workflow
- Gather context: diff against base branch, uncommitted changes, recent commits, changed files, and user intent from recent relevant chats if useful.
- Run targeted tests for changed behavior. If no focused tests exist, decide whether to add them or document the gap.
- Review for correctness, regressions, security, and intent fit. Use parallel subagents for larger diffs.
- Fix critical issues before finalizing and re-run affected tests.
- Commit selective files with a concise message.
- Push branch and open or update a PR.
Suggested Checks
git fetch origin main
git diff origin/main...HEAD
git status
gh pr checks --json name,bucket,state,workflow,linkGuardrails
- Prioritize correctness, security, and regressions over style-only comments.
- Keep commits focused and avoid unrelated file changes.
- If pre-commit checks fail, fix the issues rather than bypassing hooks.
- Use
gh pr checksinstead of GitHub Actions-only commands when judging PR readiness.
Output
- Findings summary (critical, warning, note)
- Tests run and outcomes
- PR URL
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.

