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.

An excellent operational skill: fully executable gh/git commands, a clearly sequenced five-step train with validation checkpoints and failure-feedback loops at every stage, and well-signaled one-level-deep cross-references. The only improvements are minor: trimming the invariant-justification and tagging-rationale prose would tighten the overview further.

DimensionReasoningScore

Conciseness

The body is dense and operational — commands over prose, no explanations of concepts Claude already knows — but the shared-invariant justification paragraph ("It does not weaken shared invariant §7…") and the release-tagging rationale ("an untagged bump is a release no consumer can reach…") could each be tightened by a few lines, matching the efficient-with-minor-trimming anchor.

4 / 5

Actionability

Fully executable throughout: `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 checks "$PR" --watch`, `gh pr merge "$PR" --merge`, `gh run watch <databaseId>`, and `git tag -a v<version> <merge sha>` — copy-paste ready commands covering the common cases.

5 / 5

Workflow Clarity

A five-step procedure with explicit validation checkpoints at every risky point (per-PR green verification, checks re-run after update-branch, post-merge workflow watch) and three distinct failure-recovery feedback loops (red after update → skip → /pr-iterate; rejected merge → re-read state; failed post-merge workflow → stop, escalate), so the batch-operation cap does not apply.

5 / 5

Progressive Disclosure

No bundle files exist; the single ~150-line body is well sectioned with a dedicated Cross-references section pointing one level deep to clearly signaled repo docs (`constitution/local-workflow.md`, `docs/adr/INDEX.md`). It exceeds the under-50-lines simple-skill exception, and the inline invariant/tagging justification is somewhat long for the overview, keeping it at good-structure rather than fully optimized.

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.

A strong description: concrete, comprehensive action list with explicit dual invocation modes and a clear operator-only trigger policy, plus explicit boundary marking against the nearest sibling skill. The only gap is a handful of natural synonym phrases a user might say instead of the ones present.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions covering the workflow end-to-end — "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" — which matches the comprehensive-coverage anchor, not the minor-gaps anchor below it.

5 / 5

Completeness

It explicitly answers both questions: what ("Serially land a batch of green PRs through the forge's own merge API") and when ("Invoke as `/merge-train` (discover all green PRs) or `/merge-train <PR#> [<PR#>…]` (explicit batch). Operator-invoked only") — concrete trigger guidance that satisfies the equivalent-of-'Use when' requirement, so no cap applies.

5 / 5

Trigger Term Quality

Good natural keyword coverage ("merge", "land", "green PRs", "batch", "update-branch", "post-merge workflows") plus explicit invocation forms, but a few natural synonyms like "merge queue" or "batch merge" are absent, so it falls just short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

A clear niche (operator-side serialized merge train) with explicit disambiguation — "Operator-invoked only; complements /pr-iterate, which never merges" — giving minimal conflict risk with sibling skills.

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/tic-tac-toe-with-agentic-sdlc

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.