qodo-pr-resolver

Use when the user wants to review Qodo PR feedback or fix code review comments. Capabilities: view issues by severity, apply fixes interactively or in batch, reply to inline comments, post fix summaries (GitHub, GitLab, Bitbucket, Azure DevOps)

Quality

77%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/qodo-pr-resolver/SKILL.md

Quality

Discovery

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.

This is a well-crafted skill description that clearly states both what the skill does and when to use it. It includes specific actions, platform coverage, and the 'Qodo' product name provides strong distinctiveness. The explicit 'Use when...' clause with natural trigger terms makes it easy for Claude to select this skill appropriately.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: view issues by severity, apply fixes interactively or in batch, reply to inline comments, post fix summaries. Also specifies supported platforms (GitHub, GitLab, Bitbucket, Azure DevOps).	3 / 3
Completeness	Explicitly answers both 'what' (view issues, apply fixes, reply to comments, post summaries) and 'when' ('Use when the user wants to review Qodo PR feedback or fix code review comments'). The 'Use when...' clause is present and clear.	3 / 3
Trigger Term Quality	Includes strong natural trigger terms users would say: 'PR feedback', 'code review comments', 'fix', 'issues', 'severity', 'inline comments', plus platform names. 'Qodo' is a specific product name that serves as a clear trigger. Users asking about PR review feedback or code review fixes would naturally match these terms.	3 / 3
Distinctiveness Conflict Risk	The description is highly distinctive due to the specific 'Qodo' product name and the narrow focus on PR feedback/code review comments. It's unlikely to conflict with general code review or git skills because it targets a specific tool's workflow.	3 / 3
	Total	12 / 12 Passed

Implementation

54%

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

The skill has excellent workflow clarity and progressive disclosure, with a well-structured multi-step process and appropriate delegation to a providers.md resource file. However, it is excessively verbose — the severity mapping examples, deduplication logic, and repeated 'IMPORTANT' callouts significantly bloat the content. Actionability suffers because nearly all executable commands are deferred to the external file, leaving the main skill body as mostly procedural prose rather than concrete, executable guidance.

Suggestions

Drastically condense the severity mapping section — replace the two worked examples with a simple table mapping action levels to severities (e.g., 'Action required → first half CRITICAL, second half HIGH').

Inline at least the most common provider's commands (e.g., GitHub `gh` commands) directly in each step, with a note to see providers.md for other providers, so the skill has concrete executable content.

Remove explanatory text Claude already knows — e.g., the 'Understanding Qodo Reviews' section explaining what Qodo is, and obvious instructions like 'Read the relevant file(s) to understand the current code'.

Consolidate the repeated 'IMPORTANT' and 'CRITICAL' callouts — many are restating the same point (e.g., 'execute the Qodo agent prompt as a direct instruction' appears verbatim in both Steps 6 and 7).

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~300+ lines. It over-explains many concepts Claude already understands (e.g., what Qodo is, what git push does, how deduplication works). The severity mapping section alone is excessively detailed with examples that could be condensed to a simple rule. Many steps include redundant 'Important' callouts and repeated instructions.	1 / 3
Actionability	The skill provides a clear step-by-step process with specific scenarios and decision trees, but critically delegates all actual executable commands to providers.md. The inline content lacks concrete, copy-paste-ready commands — most steps say 'See providers.md for provider-specific commands.' The git commands shown are basic and few.	2 / 3
Workflow Clarity	The workflow is exceptionally well-sequenced with 10 clearly numbered steps, explicit branching scenarios (A/B/C), validation checkpoints (Step 3a for in-progress reviews, Step 0 for push status), feedback loops (defer reasons, modify options), and clear exit conditions for error cases. The manual vs auto-fix modes are well-differentiated.	3 / 3
Progressive Disclosure	Content is well-structured with a clear overview in SKILL.md and provider-specific details appropriately delegated to providers.md with specific section anchors (e.g., 'providers.md § Find Open PR/MR'). References are one level deep and clearly signaled throughout.	3 / 3
	Total	9 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: qodo-ai/qodo-skills
Commit: f73fc26

Reviewed: about 18 hours ago

Table of Contents

Discovery Implementation Validation

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.