CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pr-iterate

One closed-loop iteration on an open PR — read CI checks + Claude / human review comments, triage against this repo's ADRs, 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

88%

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

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: executable commands at every step, hard safety rules, upfront validation with abort conditions, and explicit stop/escalation criteria — exactly the structure a risky push-to-remote workflow needs. It is token-efficient for its complexity, with only minor repetition (ADR-0044 rationale appears twice) and no progressive-disclosure offloading of detail into reference files.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence — no explanations of what CI, git, or Conventional Commits are — with every section carrying operational weight. A few spots could be tightened (e.g., the bot-vs-local-review comparison in step 2 and repetition of the ADR-0044 rationale in both hard rule 6 and the step-4 comment), matching the 4 anchor's "minor instances of over-explanation" rather than the 5 anchor's every-token-earns-its-place.

4 / 5

Actionability

Fully executable throughout: copy-paste-ready `gh`/`git` commands for snapshotting, log triage, replies (REST + GraphQL resolve mutation), a heredoc commit-message template, and a concrete output-format block. The only near-gap ("Get the threadId from the gh api listing") is immediately actionable in context.

5 / 5

Workflow Clarity

A clearly sequenced 6-step procedure (snapshot → review → triage → act → wait → stop) with explicit validation checkpoints up front (clean worktree, correct branch, up-to-date with origin — each with abort behavior), feedback loops (husky hook rejection → fix message and retry, never --no-verify), failure-classification tables, and explicit stop/escalation conditions. Pushes (risky operations) are guarded by hard rules and pre-push checks.

5 / 5

Progressive Disclosure

No bundle files exist, and the single-file organization is good: clean section headers, a dedicated Cross-references section with exact paths for every ADR and sibling skill, and pointers to repo sources (docs/diary.md, CLAUDE.md, workflow files) instead of inlining their content. It sits at the 4 anchor rather than 5 because all detail lives in SKILL.md itself — some reference material (e.g., the ADR index or failure-classification table) could be offloaded to a references/ file to slim the always-loaded context.

4 / 5

Total

18

/

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, specific description that names concrete actions across the whole iterate-loop and gives explicit invocation guidance. Voice is appropriately third-person/imperative with no fluff. The only gap is that trigger phrasing is command-invocation style rather than a "Use when…" clause with natural user-side synonyms, which keeps trigger quality and completeness at 4 rather than 5.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "read CI checks + Claude / human review comments", "triage against this repo's ADRs", "apply valid suggestions", "reply with reasoning on rejected ones", "push fixes as Conventional Commits, and report status" — covering the full loop comprehensively with no vague filler.

5 / 5

Completeness

Both halves are present: the "what" is the full action list, and the "when" is given as equivalent explicit trigger guidance — "Invoke as `/pr-iterate <PR#>`" and "Compose with `/loop /pr-iterate <PR#>` for continuous monitoring until green". It matches the 4 anchor ('when' could be more explicit, e.g., a "Use when…" clause naming user-side triggers) rather than the 5 anchor's concrete trigger phrases.

4 / 5

Trigger Term Quality

Good natural-term coverage for the domain: "open PR", "CI checks", "review comments", "Conventional Commits", "continuous monitoring until green". It falls short of the 5 anchor's comprehensive synonym coverage (e.g., no "pull request", "drive to green", "fix CI" phrasings), but well above the 3 anchor's missing-common-variations level.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche — one closed-loop iteration on an open PR with a named command, distinct from the sibling skills it composes with (/loop, /review-and-evaluate, /review-pr) — so it is unlikely to trigger for the wrong skill.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

agranado2k/ai-report-platform

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.