CtrlK
BlogDocsLog inGet started
Tessl Logo

review-fix-loop

Self-review a PR, fix all issues, and re-review in a loop until clean. Coordinates code-review, address-pr-comments, and fix-ci-tests skills.

61

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

The content is highly actionable with strong workflow sequencing and validation feedback loops, but it is verbose and monolithic — large duplicated code blocks and repeated warnings waste tokens, and no reference files are used to shed detail. Extracting the repeated GraphQL query and severity rubric into a reference file would improve both conciseness and progressive disclosure.

Suggestions

De-duplicate the GraphQL pagination query: define it once in a referenced script or reference file and invoke it from both Step 2E and Step 3.

Move the P0–P3 severity rubric and the long iteration-decision detail into a reference file, keeping SKILL.md as a lean overview.

Collapse the repeated 'do not read comment body' warnings into a single stated-once security rule.

DimensionReasoningScore

Conciseness

The body is actionable and avoids explaining concepts Claude already knows, but it repeats material — the ~40-line GraphQL pagination query appears verbatim in both Step 2E and Step 3, and the 'do not read comment bodies' security warning is stated multiple times — so it could be tightened.

2 / 3

Actionability

Provides fully executable bash commands, a concrete GraphQL query, exact TaskCreate subjects, and copy-paste-ready commit-message examples with clear placeholders — matching the executable-code anchor.

3 / 3

Workflow Clarity

Clear sequencing with explicit gate checks, completion checks, a decision matrix, and a validate→reset→retry feedback loop (Step 3) embodies the explicit-validation-and-feedback-loops anchor.

3 / 3

Progressive Disclosure

Section organization is good, but the skill is a ~400-line monolith with no bundle files; content that could be split out (the GraphQL query, the severity rubric) is inline rather than in one-level-deep reference files.

2 / 3

Total

10

/

12

Passed

Description

67%

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 and distinctive, naming concrete actions and coordinated skills, but it omits an explicit "Use when..." trigger clause and a few natural keyword variations. Adding trigger guidance would raise completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when you want to self-review and harden a PR before requesting human review.'

Include common natural variations such as 'pull request', 'review comments', and 'CI failures' for better trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Self-review a PR, fix all issues, and re-review in a loop until clean" — and names the three coordinated skills, matching the multiple-specific-actions anchor.

3 / 3

Completeness

Clearly states what the skill does but lacks a "Use when..." clause or equivalent explicit trigger guidance, so the "when" is only implied — capping completeness at 2 per the rubric guidelines.

2 / 3

Trigger Term Quality

Includes relevant keywords ("PR", "self-review", "fix all issues", "re-review in a loop") but omits common variations a user might say such as "pull request", "review comments", or "CI failures".

2 / 3

Distinctiveness Conflict Risk

The loop-until-clean framing and explicit naming of coordinated skills (code-review, address-pr-comments, fix-ci-tests) carve a clear niche unlikely to trigger the wrong skill.

3 / 3

Total

10

/

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
DataDog/rshell
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.