CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pr-review-fix

Periodically analyze open pull requests for CI failures, code review feedback, and quality issues, then fix them in batch. Use this skill when the user asks to check PR status, triage CI failures, fix review comments, analyze open PRs, or run a scheduled PR health check across the repository.

Quality

87%

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

92%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 well-engineered skill body: fully executable commands, a four-phase workflow with explicit validation and an error-recovery feedback loop, and exemplary progressive disclosure via a routing table to five real, one-level-deep reference files. The only weakness is mild redundancy between the when-to-use section, the safety rules, and the workflow steps.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no padding about what PRs or CI are — with every section operational (commands, routing table, safety rules). Minor trimmable redundancy: "When to use this skill" restates the frontmatter description, and the Git safety rules repeat steps already in Phase 3 ("Always stash", "Always verify"), so it falls just short of the every-token-earns-its-place level-5 anchor.

4 / 5

Actionability

Copy-paste-ready commands throughout: `gh pr list --state open --json number,title,headRefName,statusCheckRollup,reviewDecision,mergeable --limit 30`, `gh pr checks <number>`, `git checkout -B <branch> github/<branch>`, plus a concrete commit format `fix(<scope>): 🔧 <english description>` with real scope examples. The only uncommanded steps ("Reproduce the issue locally (build, test, or lint)") are project-specific and appropriately delegated to references, matching the level-5 anchor of executable commands covering common cases.

5 / 5

Workflow Clarity

Four clearly sequenced phases with explicit validation ("Reproduce the issue locally", "Verify locally: build → test → lint", post-push `gh pr checks`), a genuine feedback loop ("If CI still fails, loop back to Phase 3 for that PR"), and a closing checklist — the exact shape of the level-5 anchor. The batch-operation validation cap does not apply because local verification and CI re-checking are both present; it is above level 4 because the error-recovery loop and self-check checklist are explicit rather than implied.

5 / 5

Progressive Disclosure

The SKILL.md is a concise overview with a dedicated routing table mapping each task to its reference file; all five referenced files (discovery, triage, fix-workflow, ci-pipeline, fix-recipes) exist in `references/`, and inspection confirms they are one level deep (a single sibling cross-reference, no nested chains). This matches the level-5 anchor of a clear overview with well-signaled, one-level-deep references and easy navigation.

5 / 5

Total

19

/

20

Passed

Description

78%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 clearly states what the skill does and gives five natural trigger phrases, including the PR/pull-request synonym pair. Its main limitation is action specificity — only two verbs (analyze, fix) — and minor overlap risk with general code-review/CI-fix skills.

DimensionReasoningScore

Specificity

Names the domain ("open pull requests", "CI failures, code review feedback, and quality issues") with two concrete action verbs — "analyze" and "fix them in batch" — which matches the 'names domain and 1-2 concrete actions' anchor rather than the several-distinct-verbs pattern of level 4 (e.g., 'extracts, fills, converts').

3 / 5

Completeness

Explicitly answers both questions with concrete trigger phrases: what — "Periodically analyze open pull requests for CI failures, code review feedback, and quality issues, then fix them in batch"; when — "Use this skill when the user asks to check PR status, triage CI failures, fix review comments, analyze open PRs, or run a scheduled PR health check". This matches the level-5 anchor exactly; it is not level 4 because the 'when' clause is fully explicit with enumerated triggers, not merely adequate.

5 / 5

Trigger Term Quality

Five natural phrases users would actually say — "check PR status", "triage CI failures", "fix review comments", "analyze open PRs", "run a scheduled PR health check" — plus the PR/pull-requests synonym pair, but common variations like "broken build", "failing checks", or "red CI" are missing, keeping it short of comprehensive level-5 coverage.

4 / 5

Distinctiveness Conflict Risk

A clear niche (responding to CI/review feedback on open PRs) with distinct triggers like "triage CI failures" and "scheduled PR health check", but "fix review comments" and "fix them in batch" carry minor overlap risk with generic code-review and CI-fixing skills. Not level 5 because the description does not explicitly disambiguate against those closely related neighbors; not level 3 because the trigger set is far more targeted than 'somewhat specific'.

4 / 5

Total

16

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

TencentCloudBase/CloudBase-AI-Toolkit

Path

skills/pr-review-fix/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.