merge-ready
π―SkillGets a code branch ready for the project maintainer's final review. It checks for security problems, needless complexity, and ways to get paid features for free, fixes real issues, runs the checks, and opens or updates the pull request without merging it.
Installation
npx skills add every-app/open-seo --skill merge-readyRun it in a terminal; it asks which AI coding tools to install it for (Claude Code, Codex, Cursor and more).
Uses skills.sh Β· Node.js 22.20+
After installing
Ask for related work and the agent uses it on its own, or call it yourself.
/merge-readyInstall by hand
Copy the whole skill folder from GitHub to the place below. Copying only SKILL.md can leave out files the skill uses.
Open the skill folder β- This project
.claude/skills/merge-ready/ - All projects
~/.claude/skills/merge-ready/
These paths are for Claude Code. For other tools, the command above puts it in the right place.
SKILL.md
View 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").
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.
More from this repository10
OpenSEO is an open-source tool for improving how your website shows up in search results, as a cheaper option to Semrush or Ahrefs. Your AI agent can use its data to do keyword research, track rankings and check your site.
Helps you find search words worth targeting for your website using OpenSEO data. It checks how often people search them and how hard they are to rank for, saves the good ones, and delivers a report.
Studies one competitor's website to see how it gets visitors from search engines. It looks at the search words it ranks for, its topics and links from other sites, then shows gaps you can use, in an OpenSEO report.
Groups search words by what people are looking for and decides which page on your site should target each group. It uses OpenSEO tools and delivers the plan as a report.
A friendly coach for OpenSEO that explains how to get your site found in search engines in plain words. It reads your project details, suggests one clear next step, and points you to a fuller report when you want more depth.
Finds websites, pages and authors that might link to your page or product, then looks up public ways to contact them. It drafts outreach messages and saves the findings as a report in OpenSEO.
Shows who wins the most search traffic in your market, what content works for them, and where openings remain for you. It uses OpenSEO data and delivers the result as a saved report.
Interviews you once about your website's search goals, competitors, key pages and writing preferences, and saves the answers in your OpenSEO project. Other OpenSEO skills then reuse this information in later sessions.
Prepares a new release of the OpenSEO project from start to finish. It raises the version number, writes short release notes from the changes since the last release, double-checks them, and opens a pull request.
Skill