prp-debug

Diagnoses a bug, error, stack trace, regression, or unexplained behavior and publishes the evidence-backed root cause to GitHub. Use when the user says "debug this", "find the root cause", provides a bug report or stack trace, asks to investigate a GitHub issue, or invokes /prp-debug. Defaults to commenting on the matching open issue or creating one when none exists.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

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 tightly written, well-sequenced orchestration skill with explicit validation feedback loops and good structure. The only minor gap is that concrete diagnostic execution is delegated to another skill rather than specified inline.

Dimension	Reasoning	Score
Conciseness	Lean and efficient: every line is actionable guidance with no padded explanations of concepts Claude already knows; no fluff or over-explanation.	5 / 5
Actionability	Provides concrete, specific orchestration guidance — spawn the named prp-core:root-cause-analyzer with explicit inputs, exact comment/issue contents, and flag handling — but the actual diagnostic mechanics are delegated rather than given as copy-paste code.	4 / 5
Workflow Clarity	Clear four-step sequence (resolve → diagnose → reconcile → publish) with explicit validation checkpoints: a regression check that fails before and passes after, read-back verification of the published issue, and UNRESOLVED/CONDITIONAL handling.	5 / 5
Progressive Disclosure	Under 50 lines with no external references needed; content is well-organized into numbered sections with clear headers and no nested reference chains.	5 / 5
	Total	19 / 20 Passed

Description

100%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, specific description that clearly states what the skill does and when to invoke it, with natural trigger terms and a distinct niche. Third-person voice is used throughout.

Dimension	Reasoning	Score
Specificity	Names the debugging domain and multiple concrete actions — 'Diagnoses a bug, error, stack trace, regression', 'publishes the evidence-backed root cause to GitHub', commenting on a matching issue, or creating one — giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both what (diagnose and publish the evidence-backed root cause to GitHub) and when via a concrete 'Use when...' clause with several trigger phrases, plus default publication behavior.	5 / 5
Trigger Term Quality	Includes natural phrases users would actually say — "debug this", "find the root cause", bug report, stack trace, investigate a GitHub issue — plus the /prp-debug slash invocation and synonyms.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (evidence-backed diagnosis routed to GitHub issues/comments) with a distinct /prp-debug trigger, making overlap with generic debugging skills minimal.	5 / 5
	Total	20 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: Wirasm/prp
Path: .claude/skills/prp-debug/SKILL.md
Commit: 9724799

Reviewed: ~13 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.