merge-ready
Skill4 starsChanged 13 days agoMITView on GitHub
Get a branch ready for the maintainer's final review. Review it for security, simplicity, and billing abuse, fix what's real, get checks passing, and open or update the PR. Use whenever the user says a feature, fix, or branch should be "merge ready", asks to get changes ready for review, or appends this to a build request ("build X and make it merge-ready").
5 other projects use a version of this.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- Koroqe/claude-code-sdlctheir own version, first seen Oct 23, 2026
- jwuthri-cloud/Tracely-aitheir own version, first seen Oct 20, 2026
- VladSez/easy-invoice-pdftheir own version, first seen Oct 8, 2026
- every-app/open-seoword for word, first seen Oct 8, 2026
- Jwuthri/Tracely-aitheir own version, first seen Jul 28, 2026
Other versions5 projects use a version of this.
Word for word · 1
- every-app/open-seo★ 28k100% same
Edited · 0
None found.
Wrote their own version · 4
- Jwuthri/Tracely-ai★ 1.3ksame name
- VladSez/easy-invoice-pdf★ 1.1ksame name
- jwuthri-cloud/Tracely-ai★ 979same name
- Koroqe/claude-code-sdlc★ 52same 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 repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- ai-prompt-researchSkill
- ai-visibility-auditSkill
- competitive-landscapeSkill
- competitor-analysisSkill
- create-repo-skillSkill
- deslopSkill
- evaluate-skillSkill
- keyword-clusteringSkill
- keyword-researchSkill
- link-prospectingSkill
- local-seoSkill
- observability-triageSkill
- openseo-release-notesSkill
- openseo-review-web-contentSkill
- papercutsSkill
- review-briefSkill
- review-simplifySkill
- review-ui-statesSkill
- seo-auditSkill
- seo-coachSkill
- seo-project-setupSkill
- seo-reportSkill
- setup-openseoSkill
- simple-issue-descriptionSkill
- stageshowSkill
- test-auditSkill
- verify-local-mcpSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
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 26
Never merge. The maintainer reviews last.
“Common” is measured: kept by at least 6 in 10 of the 4 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
Get this branch ready for the maintainer's final review. If you were also asked to build something, build it first.
Fetch and merge origin/main if the branch is behind. Then review everything on the branch against it, including uncommitted and untracked files. Make sure you understand every product decision and change in functionality.
Is it secure?
Is it as simple as it can be? What can be deleted or simplified given the end state of the branch? Did an unlikely edge case lead to overengineering? We prefer to delete code.
Does it use APIs and SDKs (TanStack, DataForSEO, Autumn, Cloudflare) idiomatically? Watch for code that reinvents what they already do, works around limits they don't have, or pays for more than it needs. Check the docs only when something looks off.
Is there a significant way to abuse billing, like getting credits, paid features, or provider calls without paying? Ignore small leaks nobody would bother exploiting.
Beyond that, review it however you think best. Work out which parts could do the most damage if they're wrong and spend your time there. docs/maintainers/review-guidelines.md lists the repo's invariants and the things that look wrong but are intentional.
Fix what's real. Commit as you go. Get pnpm ci:check and pnpm test passing locally, then push. Those local runs stand in for CI, so don't wait for GitHub CI to finish.
Open or update the PR against main. Write the description in the simple-issue-description format, and put anything you left for the maintainer's judgment under Extra context.
Never merge. The maintainer reviews last.
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.

