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

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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.

Excellent procedural content: every step is concrete and executable, validation and feedback loops are explicit at each phase, and the single-file structure is appropriately lean with no padding or concept re-teaching. The review-axis definitions and verify-then-fix loop make the workflow unambiguous end to end.

Dimension	Reasoning	Score
Conciseness	The body is dense, imperative procedure with zero concept explanations; every aside carries project-specific context Claude cannot know ("Credits are billed via Autumn; uncounted spend is a revenue leak", "This codebase deliberately stays simple"). Every token earns its place, matching the top anchor rather than the minor-trimming anchor at 4.	5 / 5
Actionability	Gives copy-paste-ready commands (git fetch origin main, git diff origin/main...HEAD, git diff --cached, git status --short, pnpm ci:check with its four checks), a concrete severity taxonomy (blocker/should-fix/nitpick), verdict labels (APPLY/APPLY-MODIFIED/REJECT), five named review axes, and explicit PR-description requirements. As an instruction-only skill the guidance is fully executable across both invocation modes.	5 / 5
Workflow Clarity	Steps 0–5 are clearly sequenced with explicit validation and feedback loops: adversarial verification subagents in step 3, "Fix failures and re-run until clean", and "Loop until ci:check passes and no verified findings remain unaddressed", plus auditable checkpoint commits after merge resolution and after fixes. Matches the top anchor; validation is present so no destructive-operation cap applies.	5 / 5
Progressive Disclosure	A single-file skill with no bundle files; sections are well-organized and all content is core process that belongs inline. Its only file references (docs/maintainers/review-guidelines.md, .agents/PAPERCUTS.md, the papercuts skill) are clearly signaled and one level deep, so navigation is trivial — matching the top anchor.	5 / 5
	Total	20 / 20 Passed

Description

83%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.

A strong description: it explicitly states what the skill does and when to use it, with quoted natural trigger phrases covering both standalone and build-request-composed invocation. Slight room to broaden trigger synonyms and make the PR-authoring actions explicit.

Suggestions

Add one or two more natural trigger variants (e.g., "finalize this PR", "review my branch before merge") to broaden trigger_term_quality coverage.

Make the PR-creation/update action explicit in the description (e.g., "opens or updates the PR with review instructions") to close the specificity gap.

Sharpen the distinctiveness of the "get changes ready for review" trigger (e.g., "ready for the maintainer's review") to reduce overlap with generic code-review skills.

Dimension	Reasoning	Score
Specificity	Names several concrete actions — "multi-axis subagent review with verified findings, fixes, ci:check, checkpoint commits, and an updated PR" — matching the anchor for several specific actions with minor gaps. Not 5: coverage is not fully comprehensive (syncing with main, pushing, and PR-description authorship are only implied by "updated PR").	4 / 5
Completeness	Explicitly answers both what ("Take a branch from 'code exists (or is about to)' to 'ready for the maintainer's final review'") and when ("Use whenever the user says a feature/fix/branch should be 'merge ready'...") with concrete trigger phrases — a direct match to the top anchor.	5 / 5
Trigger Term Quality	Includes natural user phrasings with quoted variants ("merge ready", "build X and make it merge-ready", "asks to get changes ready for review"), giving good keyword coverage. Not 5: a few natural synonyms are missing (e.g., "review my branch", "finalize the PR"); not 3 since multiple genuine trigger phrases are present.	4 / 5
Distinctiveness Conflict Risk	A clear niche with distinct triggers ("merge ready", "maintainer's final review", ci:check, checkpoint commits), but the trigger "asks to get changes ready for review" has minor overlap risk with generic code-review skills. Matches anchor 4 rather than 5 due to that overlap.	4 / 5
	Total	17 / 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: .agents/skills/merge-ready/SKILL.md
Commit: db8bde1

Reviewed: 4 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.