CtrlK
BlogDocsLog inGet started
Tessl Logo

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").

78

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

The canonical home for this skill is merge-ready in every-app/open-seo

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

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

The content is a tightly-scoped, highly actionable workflow with explicit checkpoints and validation feedback loops, and it is well-organized without relying on external bundle files. It assumes Claude's competence and provides concrete commands and taxonomies rather than abstraction.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no explanations of git, pnpm, or CI basics — with every section earning its place, matching the score-3 lean-and-efficient anchor rather than the slight padding of a 2.

3 / 3

Actionability

Concrete commands and well-defined taxonomies throughout (git diff variants, pnpm ci:check, blocker/should-fix/nitpick severities, APPLY/APPLY-MODIFIED/REJECT verdicts, enumerated PR-description requirements) meet the score-3 fully-executable anchor rather than the incomplete guidance of a 2.

3 / 3

Workflow Clarity

Numbered phases 0–5 with explicit 'Checkpoint' callouts and feedback loops ('Loop until ci:check passes and no verified findings remain unaddressed') match the score-3 clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

No bundle files exist, so per the simple-skill scoring note the well-organized self-contained sections (0–5) and clearly-signaled by-name cross-skill pointers (maintain-greptile-rules, papercuts) meet the score-3 bar without external references.

3 / 3

Total

12

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 states the specific pipeline of actions, includes an explicit 'Use whenever...' trigger with natural phrasing, and occupies a clear niche. Voice is correctly third person, so no specificity penalty applies.

DimensionReasoningScore

Specificity

The description enumerates concrete actions — 'multi-axis subagent review with verified findings, fixes, ci:check, checkpoint commits, and an updated PR' — matching the score-3 anchor of multiple specific concrete actions rather than the partial coverage of a 2.

3 / 3

Completeness

It answers 'what' (take a branch to ready-for-review via review/fix/ci/checkpoint/PR) and 'when' with an explicit 'Use whenever the user says...' trigger clause, satisfying the score-3 requirement for both.

3 / 3

Trigger Term Quality

Natural user-facing phrases like 'merge ready', 'make it merge-ready', and 'get changes ready for review' give good coverage of terms a user would actually say, meeting the score-3 anchor and exceeding the partial-coverage of a 2.

3 / 3

Distinctiveness Conflict Risk

The distinctive 'merge ready' niche with its own trigger phrasing is unlikely to fire for the wrong skill, matching the score-3 clear-niche anchor.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.