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

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 operationally excellent skill body: fully executable commands, exhaustively validated batch workflow with explicit failure branches, and clear structure. Its one real weakness is conciseness — the trace-emit policy paragraphs are written in a dense, repetitive run-on style that costs significant tokens without adding policy content.

Suggestions

Rewrite the `feedback` emit paragraph (lines 184–216) as a short table or bulleted enumeration of the `data.by`/`outcome` cases; the current ~30-line single sentence restates the quote-character rule and the "operator's words are data" boundary twice each.

Move the verbatim `merge.land` emit field specification (lines 170–182) and the `sed` filter into a `references/emit-formats.md` file, keeping only the field semantics and the one-line pointer in the body.

State each error-handling rule (update-branch red, merge rejected, post-merge failure) once in a compact failure-mode list instead of interleaving full prose restatements within step 4 and the hard rules.

DimensionReasoningScore

Conciseness

The procedure and command blocks are tight, but the trace-emit policy sections are written as enormous single-sentence paragraphs (e.g. the ~30-line `feedback` paragraph where the "quote character" rule and "the operator's words… are data" point are each stated twice) that could be cut roughly in half without losing policy content. It is not padding — nothing explains concepts Claude already knows — but the tightening opportunity is substantial rather than minor.

3 / 5

Actionability

Fully executable throughout: `gh pr list --state open --json …`, `gh api -X PUT "repos/{owner}/{repo}/pulls/$PR/update-branch"`, `timeout 30m gh pr checks "$PR" --watch`, `git tag -a v<version> <merge sha>`, complete `trace.sh emit` field syntax, and an exact `sed` filter for the `<!-- implement: -->` line — all copy-paste ready.

5 / 5

Workflow Clarity

A numbered five-step procedure with validation at every checkpoint for a batch/destructive operation: green-check verification before boarding, re-watching checks after update-branch (4b), watching post-merge runs (4d), explicit timeout semantics (exit 124 vs. other non-zero), and feedback loops for each failure mode ("skip the PR, record it as a `/pr-iterate` candidate, continue the train" vs. hard rule 6's stop-and-escalate). The batch-operation cap does not apply — validation is thorough.

5 / 5

Progressive Disclosure

No bundle files exist, and the body is well-sectioned (What this does, Hard rules, Procedure 1–5, Output format, Cross-references) with clearly signaled one-level references to `constitution/local-workflow.md` and `docs/adr/INDEX.md`. Minor gap: the long inline `merge.land`/`feedback` emit-format specifications are exactly the kind of verbatim material that could live in a reference file.

4 / 5

Total

17

/

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 states concrete capabilities across the whole merge-train lifecycle, gives explicit invocation forms and operator-only gating, and clearly distinguishes itself from adjacent skills. The only weakness is that a handful of natural user phrasings for the same intent are not covered.

DimensionReasoningScore

Specificity

"Serially land a batch of green PRs… migration-aware ordering, update-branch for stale PRs, wait for the post-merge workflows between merges, then run /worktree-cleanup" lists multiple concrete actions covering the entire lifecycle (ordering, stale handling, merging, waiting, cleanup) with no coverage gaps.

5 / 5

Completeness

Explicitly answers both: 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#>…]`… Operator-invoked only"), with concrete invocation triggers.

5 / 5

Trigger Term Quality

Natural domain terms are present — "land", "merge", "green PRs", "batch", "stale", "update-branch" — but a few phrasings an operator might actually use ("ship", "deploy", "batch merge") are absent, fitting the good-but-not-comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

"Operator-invoked only" plus explicit delineation from sibling skills — "complements /pr-iterate, which never merges" and the hand-off to "/worktree-cleanup" — gives it a clear niche with minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_version

'metadata.version' is missing

Warning

referenced_paths_exist

Referenced path issues: 4 possibly missing (scripts/agents.lib.sh, scripts/guards.config.sh, scripts/trace.sh, scripts/vocab.sh)

Warning

Total

13

/

16

Passed

Repository

agranado2k/agentic-sdlc

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.