review-and-ship
Skill1 starsChanged 7 months agoNo licenceView on GitHub
Implement changes, use `/review-bugbot` before pushing, fix critical issues, then handle the full Git + GitHub workflow — branch, commit, push, PR. Use when the user wants to ship with validation, says "review and ship", "ship after review", "run bugbot then push", "review before PR", or asks to implement a feature/fix and submit it only after a Bugbot pass. Prefer this over `ship` when code quality review is expected before the PR goes up.
- Installs packages
- Commits and pushes
5 other projects use a version of this.
Adopted by
Most recently taken up by
- catesandrew/skillstheir own version, first seen Nov 8, 2026
- ArchitektApx/cursor-skills-for-claudetheir own version, first seen Nov 1, 2026
- dhanji4U/skillstheir own version, first seen Oct 2, 2026
- ElyzeSolutions/skillstheir own version, first seen Aug 6, 2026
- cogine-ai/cogine-dev-skillsettheir own version, first seen Jun 25, 2026
Used with
Projects with it also use fix-merge-conflicts.
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.
jaydubya818Skillfix-merge-conflicts
Use when a branch needs conflicts resolved and the merged result verified.
Also in 3 projects that use this
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- cogine-ai/cogine-dev-skillset★ 4same name
- dhanji4U/skills★ 2same name
- catesandrew/skills★ 1same name
- ElyzeSolutions/skills★ 1same name
- ArchitektApx/cursor-skills-for-claude★ 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 repositoryOne other file it gives its agents.
- shipSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. 0 are common, 10 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
10
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 5 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.
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.