CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pr-iterate

One closed-loop iteration on an open PR — read CI checks + bot and human review comments, triage against this repo's decision records, apply valid suggestions, reply with reasoning on rejected ones, push fixes as Conventional Commits, and report status. Invoke as `/pr-iterate <PR#>`. Compose with `/loop /pr-iterate <PR#>` for continuous monitoring until green.

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/pr-iterate/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 unusually concrete, well-gated operational procedure: executable commands throughout, explicit validation and fail-closed checks, and clear iteration/stop semantics. It is dragged down by baroque run-on prose with repeated protocol text, a non-executable spec for the safety-critical subagent spawn, and a progressive-disclosure structure whose referenced sidecar files and scripts are entirely absent from the bundle.

Suggestions

Ship the referenced bundle files (LANE.md, RISK.md, RELEASE-BOUND.md, REPEATED-FAILURE.md, DISMISSALS.md, NO-LENS.md, CHECK-TABLE.md, and scripts/trace.sh, scripts/vocab.sh, scripts/agents.lib.sh, scripts/vocab.config.sh) or remove the references — every sidecar link currently dangles.

Move the ~80-line fence shell block (fetch_bodies, vocab_checker, span_ok, typed_return_ok, checked_returns) into a scripts/ file and reference it, keeping only the call sequence and the shape contract in the body.

Rewrite the multi-hundred-word run-on paragraphs (subagent spawn spec, stop-condition bullet 1, the 'check fails closed' prose) as numbered sub-steps or bullet lists, and state the Trace-Run/Trace-Spawn hand-off protocol once instead of twice.

DimensionReasoningScore

Conciseness

No filler explaining things Claude already knows — nearly every sentence carries repo-specific policy — but several passages are conspicuously over-written: the ~600-word single-paragraph subagent-spawn spec ("A tool-restricted subagent reads those files..."), the stop-conditions bullet 1 run-on, and the fence prose at "The check fails closed". The Trace-Run hand-off protocol is stated twice nearly verbatim (step 1 and step 2), and the vocab_checker discovery rule is explained both in code comments and again in prose. Not 2 because there is no generic padding; the density is high but the tightening opportunities are real.

3 / 5

Actionability

Mostly copy-paste executable: prereq guard script, gh api snapshot commands with jq filters, a GraphQL review-thread query, five complete shell functions (fetch_bodies, vocab_checker, span_ok, typed_return_ok, checked_returns), commit templates, reply endpoints, and an output-format template. Not 5: the subagent reader spawn — the core of the trust fence — is described only in prose with no executable command ("How an agent harness withholds those tools is the adapter's, not this skill's, to say"), leaving the most safety-critical step non-concrete.

4 / 5

Workflow Clarity

Clear numbered sequence (prereqs → snapshot → review → triage → act → wait → stop) with genuine validation checkpoints: worktree/branch/staleness aborts (exit 2), the fail-closed checked_returns gate, explicit convergence stop conditions, and a 5-iteration stuck cap — well above the batch/destructive cap concern. Not 5: step 5's structure is muddled ("Two modes:" followed by "Either way..." before the modes are listed) and stop-condition bullet 1 buries the re-review/verdict protocol in a several-hundred-word run-on, degrading followability at exactly the decision points that matter most.

4 / 5

Progressive Disclosure

The body is structured as an overview with clearly signaled one-level sidecar references ([RELEASE-BOUND.md], [DISMISSALS.md], [CHECK-TABLE.md], [LANE.md], [RISK.md], [NO-LENS.md], [REPEATED-FAILURE.md], scripts/trace.sh, scripts/vocab.sh) — but the bundle ships none of them: no references/, scripts/, or assets/ directories exist, so every sidecar link dangles. Additionally ~80 lines of fence shell are inlined in the body where the scripts/ file it names would go. Not 4: references cannot actually be navigated and content that belongs in a separate file is inline.

3 / 5

Total

14

/

20

Passed

Description

83%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 enumerates concrete actions across the whole iteration lifecycle, states explicit invocation and loop-composition triggers, and occupies a distinct niche. The only weakness is that natural-language trigger phrases (e.g., "pull request", "code review feedback") are thinner than the invocation syntax, leaving the when-side slightly implicit for the single-shot case.

DimensionReasoningScore

Specificity

Enumerates the full iteration lifecycle in concrete actions — "read CI checks + bot and human review comments, triage against this repo's decision records, apply valid suggestions, reply with reasoning on rejected ones, push fixes as Conventional Commits, and report status" — matching the comprehensive multi-action anchor. Not 4: coverage spans every phase (read → triage → act → report) with no notable gap.

5 / 5

Completeness

The "what" is explicit and enumerated, and the "when" is addressed via "Invoke as `/pr-iterate <PR#>`. Compose with `/loop /pr-iterate <PR#>` for continuous monitoring until green" — explicit trigger guidance that avoids the completeness cap. Not 5: there is no concrete "Use when..." phrase for the common single-shot case (after a push, when review feedback arrives), so the when-side could be more explicit.

4 / 5

Trigger Term Quality

Contains natural terms users would say — "PR", "CI checks", "review comments", "push fixes", "Conventional Commits", "continuous monitoring until green". Not 5: common variations like "pull request" spelled out, "code review feedback", or "failing checks" are missing; the invocation syntax "/pr-iterate <PR#>" is command syntax rather than user vocabulary.

4 / 5

Distinctiveness Conflict Risk

"One closed-loop iteration on an open PR" carves a clear niche — iterating an existing PR to green — distinct from review, implement, or merge skills, with explicit composition boundaries ("Compose with `/loop`..."). Minimal conflict risk; not 4 because no closely-related skill would claim this trigger set.

5 / 5

Total

18

/

20

Passed

Validation

75%

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

Validation — 12 / 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

relative_links

Relative link issues: 7 possibly missing (CHECK-TABLE.md, DISMISSALS.md, LANE.md, NO-LENS.md, RELEASE-BOUND.md, +2 more)

Warning

referenced_paths_exist

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

Warning

Total

12

/

16

Passed

Repository

agranado2k/agentic-sdlc

Path

.agents/skills/pr-iterate/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.