CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

79

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%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, actionable overview that delegates detail to genuine reference files and includes explicit verification and feedback loops for risky batch git operations. It is concise and respects Claude's competence.

DimensionReasoningScore

Conciseness

Lean body of bullet points and executable commands that assumes Claude's competence and avoids explaining concepts it already knows; minor duplication of the commit format and a routing table that re-states inline references keep it just shy of perfect but still efficient.

3 / 3

Actionability

Provides copy-paste-ready commands — 'gh pr list --state open --json ...', 'git stash', 'git checkout -B <branch> github/<branch>', 'gh pr checks <number>' — plus a concrete commit template, with details deferred to real reference files.

3 / 3

Workflow Clarity

Clear four-phase sequence with explicit validation in Phase 4 ('If CI still fails, loop back to Phase 3'), git safety rules, and a minimum self-check checklist providing feedback loops for batch branch operations.

3 / 3

Progressive Disclosure

Body is an overview with well-signaled one-level-deep references via a routing table; all referenced files (discovery, triage, fix-workflow, ci-pipeline, fix-recipes) exist in ./references/, so navigation is real and shallow.

3 / 3

Total

12

/

12

Passed

Description

100%

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, well-scoped description that states concrete capabilities and provides explicit, natural trigger phrases covering both what and when. It is third-person, concise, and unlikely to misfire.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'analyze open pull requests for CI failures, code review feedback, and quality issues, then fix them in batch' — naming domain and specific operations rather than vague language.

3 / 3

Completeness

Explicitly answers both what (analyze and fix open PRs in batch) and when ('Use this skill when the user asks to check PR status, triage CI failures...'), with explicit trigger guidance.

3 / 3

Trigger Term Quality

Covers natural phrasings a user would say — 'check PR status, triage CI failures, fix review comments, analyze open PRs, run a scheduled PR health check' — with good variation coverage.

3 / 3

Distinctiveness Conflict Risk

Carves a clear PR-review-and-fix niche with distinct triggers unlikely to conflict with general code or git skills; written in third person as required.

3 / 3

Total

12

/

12

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.

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