CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

merge-train

Serially land a batch of green PRs as signed web-flow merge commits — migration-aware ordering, GitHub update-branch for stale PRs, wait for prod migrate/release between merges, then run /worktree-cleanup. Invoke as `/merge-train` (discover all green PRs) or `/merge-train <PR#> [<PR#>…]` (explicit batch). Operator-invoked only; complements /pr-iterate, which never merges.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

An excellent operator procedure: hard safety rules up front, a fully executable gh-based pipeline with validation checkpoints and failure branches for every risky step, and a crisp output contract. The only flaw is repetition — the signed-merge-commit rationale is stated several times where one authoritative statement plus back-references would do.

DimensionReasoningScore

Conciseness

The body is dense with project-specific, non-inferable knowledge (ADR-0044 signing rationale, migration journal collisions, workflow names) and assumes Claude's competence with gh/CI. However, the web-flow-signature fact is restated roughly five times (intro, hard rules 3 and 5, steps 4a and 4c) and the /pr-iterate complementarity appears twice, which is over-explanation that could be trimmed.

4 / 5

Actionability

Fully executable throughout: exact gh commands with flags, JSON fields, and jq filters ('gh pr list --state open --json number,title,isDraft,reviewDecision,mergeable,mergeStateStatus,headRefName', 'gh api -X PUT "repos/{owner}/{repo}/pulls/$PR/update-branch"', 'gh pr merge "$PR" --merge'), named workflows to watch, and a concrete output template. Common cases including stale-PR and failure paths are covered.

5 / 5

Workflow Clarity

A clearly sequenced 5-step procedure with explicit validation checkpoints (per-PR green verification, 'gh pr checks "$PR" --watch' after update-branch, watching migrate-db.yml and release.yml before the next merge) and explicit error-recovery branches at each step (red after update → skip and route to /pr-iterate; merge rejected → stop unless transient; migrate-db failure → hard stop). The batch-operation cap does not apply because feedback loops are present.

5 / 5

Progressive Disclosure

No bundle files exist, so structure is judged on organization: the body is a cohesive ~95-line procedure with clear sections (What this does, Hard rules, Procedure, Output format) and a well-signaled one-level-deep Cross-references section pointing to ADR-0077/ADR-0044/ADR-0035 and the sibling skills. Nothing inlined here belongs in a separate file; navigation is easy.

5 / 5

Total

19

/

20

Passed

Description

92%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 names the concrete capability set (signed web-flow merge commits, update-branch for stale PRs, migration-aware ordering, migrate/release waits), gives explicit dual-mode invocation syntax, and cleanly separates itself from /pr-iterate and /worktree-cleanup. The only gap is a few missing natural synonyms ('pull requests' spelled out, 'land', 'ship').

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with exact mechanisms: 'Serially land a batch of green PRs as signed web-flow merge commits — migration-aware ordering, GitHub update-branch for stale PRs, wait for prod migrate/release between merges, then run /worktree-cleanup.' Coverage is comprehensive for the domain, matching the top anchor rather than the 'minor gaps' of a 4.

5 / 5

Completeness

Both 'what' and 'when' are explicitly answered with concrete triggers: the what is 'Serially land a batch of green PRs as signed web-flow merge commits', and the when is 'Invoke as `/merge-train` (discover all green PRs) or `/merge-train <PR#> [<PR#>…]` (explicit batch). Operator-invoked only'. This is explicit invocation guidance, so the missing-'Use when' cap does not apply.

5 / 5

Trigger Term Quality

Natural terms a user would say are present — 'merge', 'land a batch', 'green PRs', 'merge train' — giving good keyword coverage. A few natural variants are missing (e.g. 'pull requests' spelled out, 'ship'/'deploy'), keeping it below the comprehensive-synonyms anchor of 5.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (operator-side serialized merge of green PR batches) and explicitly disambiguates from siblings: 'Operator-invoked only; complements /pr-iterate, which never merges.' Minimal conflict risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

agranado2k/ai-report-platform

Path

.agents/skills/merge-train/SKILL.md

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.