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

86%

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

The canonical home for this skill is pr-iterate in agranado2k/tic-tac-toe-with-agentic-sdlc

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 exceptionally actionable, well-sequenced operational skill: every step is executable, guarded by explicit validation and stop conditions, and closed out with a required output format. The only refinements are minor trimming of explanatory asides and potentially splitting a reference table out of the main file.

DimensionReasoningScore

Conciseness

The body is dense and operational — commands, tables, and rules with essentially no explanation of concepts Claude already knows. Minor instances of over-explanation could be trimmed, e.g., the rationale for treating local and third-party reviewers as complementary in step 2 and some long parentheticals in hard rule 4.

4 / 5

Actionability

Fully executable throughout: concrete `gh pr view`/`gh api`/`git` commands, copy-paste-ready commit-message heredoc, exact GraphQL mutation for resolving threads, and a triage table mapping each failure classification to a specific Conventional Commits type. Placeholder variables ($PR, $PR_BRANCH, $COMMENT_ID) are all defined by prior commands.

5 / 5

Workflow Clarity

A clear six-step sequence with explicit validation checkpoints and feedback loops: prerequisite guards that abort with exit codes before any action, per-failure diagnostic commands (`gh run view --log-failed`), hook-blocking push guidance ('fix the cause, don't reach for the bypass'), bounded polling, and five explicit stop conditions with escalation paths. This is exactly the validate → fix → retry structure the anchor describes.

5 / 5

Progressive Disclosure

No bundle files exist, and the skill is appropriately self-contained: well-organized sections with a clear procedure, output format, and a Cross-references section pointing one level deep to sibling skills (/review-pr, /implement, /diagnose, /merge-train) and repo records (constitution/local-workflow.md, docs/adr/INDEX.md). At ~230 lines some inline material (e.g., the failure-classification table) could arguably live in a reference file, which keeps it at 'good structure, minor gaps' rather than optimal split.

4 / 5

Total

18

/

20

Passed

Description

80%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, dense description that names every concrete action in the loop and gives explicit invocation guidance. Its only weakness is that natural-language trigger phrases and boundary distinctions versus adjacent PR skills are implicit rather than spelled out.

Suggestions

Add explicit trigger phrases for the 'when' half, e.g. 'Use after pushing a PR, when CI is red, or when bot/human review feedback needs answering'.

Include common user phrasings as triggers (e.g., 'address review comments', 'get the PR green', 'drive PR to green') to broaden natural keyword coverage.

Briefly distinguish the skill from one-shot alternatives (e.g., 'one iteration only — not a full review or merge skill') to reduce overlap risk.

DimensionReasoningScore

Specificity

The description enumerates multiple 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" — giving comprehensive, concrete coverage of the skill's capabilities.

5 / 5

Completeness

Both "what" (the full closed-loop action list) and "when" ("Invoke as `/pr-iterate <PR#>`" and "Compose with `/loop /pr-iterate <PR#>` for continuous monitoring until green") are present, so the missing-'Use when' cap does not apply. However, the natural trigger conditions (e.g., 'after pushing and CI is red', 'when review feedback needs addressing') are only implied by the invocation syntax rather than stated as explicit trigger phrases, matching the anchor where 'when' could be more specific.

4 / 5

Trigger Term Quality

Good natural keyword coverage — "open PR", "CI checks", "bot and human review comments", "Conventional Commits", "iteration", "until green" — plus explicit invocation syntax. A few natural phrases users might say are missing (e.g., "address review feedback", "fix a red PR", "pull request" spelled out), keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

The closed-loop, drive-to-green, re-iterable framing ("One closed-loop iteration", "Compose with /loop... until green") carves a clear niche distinct from one-shot review or merge skills. Minor overlap risk remains with a generic 'address PR feedback' skill because the description doesn't delineate itself from adjacent single-shot PR skills.

4 / 5

Total

17

/

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/check.sh)

Warning

Total

15

/

16

Passed

Repository

agranado2k/tic-tac-toe-haskell

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.