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

85%

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

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.

A highly actionable, well-sequenced workflow skill: executable commands cover every step, validation checkpoints and stop conditions are explicit, and escalation paths are unambiguous. The main cost is token efficiency from systematic repetition of the hook-bypass rules and the confirm-list taxonomy, and the flat single-file structure offers no progressive disclosure for its longer reference tables.

Suggestions

State the never-bypass-hooks rule once (in Hard rules) and drop the repetitions in rule 5 and the Tooling reminders, keeping only the non-duplicated detail about PUSH_WITHOUT_DOCS/PUSH_WITHOUT_TESTS being logged deferrals.

Move the ✅/❌/⚠️/🔀 taxonomy explanation out of hard rule 4's parenthetical — section 2 already defines it — leaving rule 4 with just the directive.

Consider moving the failure-classification table and the output-format template into a references/ file so the main loop stays lean and the detail is loaded only when triaging or reporting.

DimensionReasoningScore

Conciseness

The body is operational with no concept-explaining padding, but the hook-bypass prohibition is stated three times (hard rule 1, hard rule 5's "that hook is the safety net — never bypass it", and the Tooling reminders' "never bypass the hook"), and hard rule 4's long parenthetical re-explains the ✅/❌/⚠️/🔀 taxonomy that section 2 already covers. This is more than minor trimming, fitting the 3 anchor ('could be tightened') rather than 4 ('minor instances'), and well above 2 (no padded sections).

3 / 5

Actionability

Guidance is copy-paste ready throughout: exact gh endpoints ("repos/{owner}/{repo}/pulls/$PR/comments"), a heredoc commit-message template, a GraphQL resolveReviewThread mutation, and a triage table mapping every failure class to a specific commit type. The only placeholders ($PR, $COMMENT_ID, $REPLY_BODY) are self-evident, matching the fully-executable top anchor.

5 / 5

Workflow Clarity

Six numbered steps with explicit validation checkpoints at the top of every iteration (clean worktree, correct branch, synced with origin), enumerated stop conditions, and genuine feedback loops ("If either blocks you, that is the signal working — fix the cause"; "Don't guess at fixes — escalate"). Checklists plus error recovery match the top anchor.

5 / 5

Progressive Disclosure

No bundle files exist; the skill is a single well-sectioned file with a dedicated, clearly signaled Cross-references section for peer skills and repo records, and the inline content is needed on every iteration. This fits the 4 anchor (good structure, appropriately placed, minor gaps) rather than 5, since there is no one-level-deep reference structure at all — material like the detailed failure-classification table and output template is entirely inline — and not 3, because organization and signaling are genuinely good.

4 / 5

Total

17

/

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 that concretely covers the entire iterate-a-PR loop and scopes invocation unambiguously via slash commands. Its only weakness is that situational triggering relies on command syntax rather than natural user phrases and synonyms (e.g., "pull request", "address review feedback").

Suggestions

Add natural trigger phrases to the 'when' portion, e.g., "Use when the user asks to address review feedback, fix failing CI, or drive a pull request to green."

Include common synonyms such as "pull request" spelled out and "failing checks" so the skill triggers from conversational mentions, not just explicit /pr-iterate invocation.

DimensionReasoningScore

Specificity

The description enumerates the complete loop concretely — "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" — with comprehensive coverage and no vague filler, matching the top anchor rather than the 'minor gaps' level below.

5 / 5

Completeness

"What" is explicit (the full closed loop) and "when" is addressed via invocation guidance ("Invoke as `/pr-iterate <PR#>`", "Compose with `/loop /pr-iterate <PR#>` for continuous monitoring until green"), so both are present. It sits below 5 because the 'when' is command syntax rather than concrete situational trigger phrases ("when the user mentions…"), and above 3 because trigger guidance is explicit, not merely implied.

4 / 5

Trigger Term Quality

Natural terms like "PR", "CI checks", "review comments", and "push fixes" are present, but common variations are missing — "pull request" never appears spelled out and there are no phrases like "address review feedback" or "get checks green". Good coverage with a few natural terms missing fits the 4 anchor; it is above 3 (coverage is solid, not sparse) but below 5 (no synonyms or variations).

4 / 5

Distinctiveness Conflict Risk

"One closed-loop iteration on an open PR" plus a named slash-command invocation carves out a clear niche (iterate an existing PR to green) that is unlikely to fire for general review, implementation, or merge skills. Minimal conflict risk matches the top anchor.

5 / 5

Total

18

/

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-with-agentic-sdlc

Path

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