CtrlK
BlogDocsLog inGet started
Tessl Logo

handhold-pr

Watch a PR's CI, diagnose every failing check, fix what's actually broken, resolve CodeRabbit's major findings, and keep iterating until the PR is green. Use when the user says "handhold the PR", "check CI", "get CI green", "resolve any issues until green", or asks why a PR's checks are failing.

80

Quality

100%

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

100%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.

The body is dense with actionable, repo-specific guidance, clearly sequenced with validation checkpoints and feedback loops, and well-structured without unnecessary external references. It respects Claude's intelligence while surfacing the non-obvious gotchas that matter.

DimensionReasoningScore

Conciseness

Lean and efficient throughout; it assumes Claude's competence and restricts itself to repo-specific knowledge Claude lacks (Nx DTE ordering flakes, auth-gated Nx Cloud URLs, CodeRabbit commenting on passing checks) with no concept padding.

5 / 5

Actionability

Provides copy-paste-ready commands for every step — `gh pr checks <n>`, `gh run view --job <jobId> --log-failed`, `gh run rerun <runId> --failed`, `nx test <project>` — covering the common cases concretely.

5 / 5

Workflow Clarity

A clear 7-step sequence with explicit validation checkpoints ('Classify the failure before fixing anything', 'Verify every finding against the current code before acting'), a feedback loop (step 5 wait-and-reloop), and a stop condition after two failed attempts.

5 / 5

Progressive Disclosure

No bundle files exist and none are needed; the body is well-organized into numbered sections plus a Notes section, keeping all process guidance inline and navigable without nested references.

5 / 5

Total

20

/

20

Passed

Description

100%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.

The description is specific, trigger-rich, complete, and clearly distinct from neighboring skills. It concisely conveys both the capability set and the exact invocation conditions without padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Watch a PR's CI, diagnose every failing check, fix what's actually broken, resolve CodeRabbit's major findings, and keep iterating until the PR is green' — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both 'what' (watch/diagnose/fix/resolve/iterate) and 'when' via a concrete 'Use when...' clause with multiple trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases a user would actually say — 'handhold the PR', 'check CI', 'get CI green', 'resolve any issues until green', and asking 'why a PR's checks are failing' — with several synonymous formulations.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (driving a PR to green CI) with distinct triggers, and explicitly differentiates from the sibling open-pr skill, minimizing conflict risk.

5 / 5

Total

20

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
analogjs/analog
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.