CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

resolve-fixed-pr-comments

Verify what PR review comments have been addressed (committed/pushed OR uncommitted local changes) and resolve the threads that are genuinely fixed or no longer relevant.

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./antigravity/skills/resolve-fixed-pr-comments/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 highly actionable and workflow-safe: every step has executable commands, explicit validation gates, fallbacks, and error recovery, which is exactly what a risky write-operation skill needs. The main weakness is redundancy — the same safety rules are repeated across three dedicated sections plus troubleshooting — which inflates token cost without adding new information.

Suggestions

Consolidate the "Critical Guidelines", "Red Flags", and "Rationalization Table" sections into one guardrail section (e.g. a single excuse-vs-reality table); the current three formats restate the same rules nearly verbatim.

Remove filler and typos: the "If you fail the task, you will be killed!" threat adds no operational value, and "or simular command" should be "similar".

Consider moving the Parameters Explained table and the rationalization examples into a reference file (e.g. references/guardrails.md) to keep SKILL.md as a lean overview, since no bundle files currently exist.

DimensionReasoningScore

Conciseness

The operational Steps 0–5 are tight and concrete, but the same guardrails are restated three times in different formats ("Critical Guidelines" bullets, "Red Flags" bullets, the "Rationalization Table") and repeated again in Troubleshooting rows, plus filler like "If you fail the task, you will be killed!". Not 2 because the majority of the body is efficient, executable instruction; not 4 because the guardrail duplication is genuine padding by token-efficiency standards.

3 / 5

Actionability

Fully executable throughout: `gh auth status`, `gh pr view --json number,url,headRefName`, a complete GraphQL query with the jq filter, the `resolveReviewThread` mutation, MCP invocation blocks with concrete parameters, a parameter table, and error-message-specific troubleshooting entries. Copy-paste ready and covering the common cases.

5 / 5

Workflow Clarity

Clear Steps 0–5 with a disposition decision table and explicit validation checkpoints ("No verification → no resolve", confirm `isResolved` is `true`, leave-unresolved-when-unsure default, fallback paths when a tool is unavailable, and wrong-thread recovery guidance). Although this is a batch operation, validation is thoroughly present, so the workflow-clarity cap does not apply.

5 / 5

Progressive Disclosure

No bundle files exist; the skill is a single, well-sectioned SKILL.md with clear headers and easy navigation. Not 5 because at ~248 lines, content such as the Rationalization Table and the Parameters Explained reference table is inlined where a separate reference file would keep the overview leaner; not 3 because structure and placement are otherwise good.

4 / 5

Total

17

/

20

Passed

Description

66%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, in third person, and states concrete conditioned actions with a distinct niche. Its main gap is the complete absence of a "Use when…" trigger clause, and it lacks common synonyms like "pull request" or "GitHub" that users would naturally say.

Suggestions

Add an explicit trigger clause, e.g. "Use when asked to resolve, close, or clean up PR review comments/threads that have been addressed."

Include natural synonyms such as "pull request", "GitHub", and "review feedback" so the description matches how users would phrase the request.

Optionally name the evidence dimension (current codebase state) to sharpen what "verify" means.

DimensionReasoningScore

Specificity

Concrete, conditioned actions are stated — "Verify what PR review comments have been addressed (committed/pushed OR uncommitted local changes)" and "resolve the threads that are genuinely fixed or no longer relevant" — going beyond minimal naming of the domain. Not 5 because only two top-level actions are listed, less comprehensive than the top anchor's multi-action coverage.

4 / 5

Completeness

The "what" is clear (verify addressed comments and resolve genuinely fixed threads), but there is no "Use when…" clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because the "when" is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Includes natural phrases users would say — "PR review comments", "resolve", "threads", "addressed", "committed/pushed", "uncommitted local changes". Not 5 because common variations like "pull request", "GitHub", and "review feedback" are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — resolving review threads that are verified fixed — with little chance of triggering the wrong skill; only minor overlap risk with general code-review skills. Not 5 because it shares "PR review" vocabulary with review-adjacent skills without a fully distinct trigger phrase.

4 / 5

Total

15

/

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

NeoLabHQ/context-engineering-kit

Path

antigravity/skills/resolve-fixed-pr-comments/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.