merge-ready

Take a branch from "code exists (or is about to)" to "ready for the maintainer's final review" — multi-axis subagent review with verified findings, fixes, ci:check, checkpoint commits, and an updated PR. Use whenever the user says a feature/fix/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").

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

100%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tightly written, highly actionable orchestration skill with an explicit numbered workflow, validation checkpoints, feedback loops, and adversarial verification. It assumes Claude's intelligence and adds only non-obvious, project-specific guidance.

Dimension	Reasoning	Score
Conciseness	Lean and dense throughout — assumes Claude's competence, never explains git/PR/SSRF/TanStack, and every bullet carries specific actionable guidance rather than padding.	5 / 5
Actionability	Concrete commands (git diff origin/main...HEAD, pnpm ci:check), structured verdicts (APPLY/APPLY-MODIFIED/REJECT), severity levels, and an explicit PR-description spec make the orchestration fully executable.	5 / 5
Workflow Clarity	Clear numbered 0–5 sequence with explicit validation (pnpm ci:check, re-review after substantial fixes), a fix-check-loop, checkpoint commits, and an adversarial verification stage before applying fixes.	5 / 5
Progressive Disclosure	A single well-organized self-contained doc with clear section headers, no monolithic wall, and no nested references; no bundle files are needed for this orchestration skill.	5 / 5
	Total	20 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An excellent description: concrete actions, natural and varied trigger phrases, and explicit what/when guidance in third-person imperative voice. It is distinguishable from generic review skills and unlikely to trigger incorrectly.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'multi-axis subagent review with verified findings, fixes, ci:check, checkpoint commits, and an updated PR' — giving comprehensive coverage of the merge-readiness pipeline.	5 / 5
Completeness	Explicitly answers both what (branch from code-exists to maintainer-review-ready) and when ('Use whenever the user says a feature/fix/branch should be merge ready…') with concrete triggers.	5 / 5
Trigger Term Quality	Natural trigger phrases users would actually say — 'merge ready', 'get changes ready for review', 'build X and make it merge-ready' — with several synonymous phrasings.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear merge-readiness niche with distinctive triggers unlikely to fire for unrelated skills; minimal overlap risk.	5 / 5
	Total	20 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: every-app/open-seo
Path: .claude/skills/merge-ready/SKILL.md
Commit: bd40284

Reviewed: 14 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.