CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

merge-train

Serially land a batch of green PRs through the forge's own merge API — migration-aware ordering, update-branch for stale PRs, wait for the post-merge workflows 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

91%

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

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

The body is an exemplar of actionable operator guidance: exact gh commands, explicit boarding criteria, validation checkpoints with error-recovery branches at every stage, and a concrete output format. Its only weaknesses are mild — some repeated safety assurances inflate the rationale section, and the whole procedure lives in one file with no bundle split. Anti-drift checks against neighboring anchors confirmed each score.

DimensionReasoningScore

Conciseness

The body is command-first and tight, and its explanatory passages (invariant §7, why local rebases strip signatures) are genuinely project-specific rather than concepts Claude already knows. It falls short of the lean anchor at 5 because the not-bypassed/branch-protection assurances repeat between the intro and hard rule 4, and the invariant discussion runs three paragraphs that could be trimmed — fitting 'minor instances of over-explanation' at 4.

4 / 5

Actionability

The procedure gives copy-paste-ready commands with exact flags and JSON fields (gh pr list --state open --json number,title,isDraft,…; gh api -X PUT "repos/{owner}/{repo}/pulls/$PR/update-branch"; gh run watch <databaseId>), concrete drop criteria for candidates, and a filled-in output template. The only deferral (merge-method flag) is explicitly justified by pointing to the authority document, so it matches the fully-executable anchor at 5 rather than 'minor gaps' at 4.

5 / 5

Workflow Clarity

The five-step sequence has explicit validation checkpoints at every stage — green-check verification before boarding, `gh pr checks --watch` after update-branch, waiting on post-merge workflows between merges — plus feedback loops for error recovery (red after update → skip and record for /pr-iterate; failed post-merge workflow → hard stop and escalate). The batch-operation validation cap does not apply because validation is thorough, matching the anchor at 5 with recovery paths rather than 'most checkpoints' at 4.

5 / 5

Progressive Disclosure

Sections are well organized (What this does, Hard rules, Procedure, Output format, Cross-references) and the external references (constitution/local-workflow.md, docs/adr/INDEX.md) are clearly signaled in a dedicated section, one level deep. At ~140 lines everything is inlined in one file — the rationale/governance discussion is long enough that a split or tighter overview could apply, and the under-50-line simple-skill exception does not apply, so 'good structure; minor organization gaps' at 4 is the best fit.

4 / 5

Total

18

/

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.

The description is highly specific, action-oriented, and written in third-person imperative style. It answers both what the skill does and when to invoke it with concrete trigger syntax, and explicitly disambiguates it from the adjacent /pr-iterate skill. Only minor synonym coverage keeps trigger term quality from a perfect score.

DimensionReasoningScore

Specificity

"Serially land a batch of green PRs through the forge's own merge API — migration-aware ordering, update-branch for stale PRs, wait for the post-merge workflows between merges, then run /worktree-cleanup" lists multiple specific concrete actions covering the entire workflow end to end, matching the comprehensive-coverage anchor at 5 rather than the 'minor gaps' anchor at 4.

5 / 5

Completeness

The 'what' is explicit (serialized landing with ordering, update-branch, workflow waits, cleanup) and the 'when' is explicit trigger guidance ("Invoke as `/merge-train` (discover all green PRs) or `/merge-train <PR#> [<PR#>…]` (explicit batch). Operator-invoked only"), matching the both-what-and-when anchor at 5 rather than the 'when could be more explicit' anchor at 4.

5 / 5

Trigger Term Quality

Natural terms are strong — "green PRs", "merge", "land", "batch", "update-branch", "post-merge workflows" — plus both concrete invocation forms (/merge-train and /merge-train <PR#>…). A few natural variations are missing (e.g. "pull requests" spelled out, "batch merge"), so it fits the 'good coverage, a few natural terms missing' anchor at 4 rather than comprehensive synonym coverage at 5.

4 / 5

Distinctiveness Conflict Risk

"Operator-invoked only; complements /pr-iterate, which never merges" carves out a clear niche and explicitly separates this skill from its nearest sibling, giving minimal conflict risk — the clear-niche anchor at 5 rather than 'minor overlap risk' at 4.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 possibly missing (scripts/guards.config.sh)

Warning

Total

15

/

16

Passed

Repository

agranado2k/google-books-clojure

Path

.claude/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.