New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Prp Debug

by Wirasm in Wirasm/prp

Diagnoses a bug, error, stack trace, regression, or unexplained behavior and publishes the evidence-backed root cause to GitHub.

MITAuto-check passedDevelopment

Install Prp Debug

skills CLI
$ npx skills add Wirasm/prp --skill prp-debug -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Wirasm/prp prp-debug --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Wirasm/prp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/prp-debug .claude/skills/prp-debug && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
prp-debug
GitHub stars
2.3k
Token cost
~1.1k tokens
SKILL.md length
537 words
Files
1
Skills in repo
37
Repo updated
First seen
Licence
MIT

At a glance

Diagnoses a bug, error, stack trace, regression, or unexplained behavior and publishes the evidence-backed root cause to GitHub.

  • Works in 4 steps: Resolve the report and publication target → Run the root-cause analysis → Reconcile duplicates with the diagnosis → …
  • The user says debug this
  • SKILL.md covers 1. Resolve the report and…, 2. Run the root-cause analysis, 3. Reconcile duplicates with… and 4. Publish the durable artifact
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Prp Debug is an agent skill from Wirasm/prp. 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.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Debugging, Root cause analysis and QA and bug reports. It works with GitHub. The repository describes itself as: Prompts, workflows and more for agentic engineering. The licence is MIT.

When your agent uses it

  • The user says debug this
  • Find the root cause
  • Provides a bug report
  • Asks to investigate a GitHub issue

Example prompts

  • “debug this”
  • “find the root cause”
  • “Use the prp-debug skill to diagnose a bug, error, stack trace, regression, or unexplained behavior and publishes the evidence-backed root cause to…”
  • “/prp-debug”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Resolve the report and publication target
  2. Run the root-cause analysis
  3. Reconcile duplicates with the diagnosis
  4. Publish the durable artifact

What it can do on your machine

Read from SKILL.md and the folder at commit 4352925. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Prp Debug loads about 1.1k tokens when it runs. Until then it costs about 95 tokens; SKILL.md has 537 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~95
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Wirasm/prp at commit 4352925, republished under its MIT licence (© Wirasm). 537 words, ~1,069 tokens.

Download SKILL.mdSave it as .claude/skills/prp-debug/SKILL.md (or your agent's skills folder).
name
prp-debug
description
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.
argument-hint
<issue | error | stacktrace | behavior> [--no-publish] [--rewrite-body]

PRP Debug

Diagnose broken current behavior through the prp-core:root-cause-analyzer, then make the finding durable in the appropriate GitHub issue. Do not implement the fix.

Input: $ARGUMENTS (if absent, use the conversation).

1. Resolve the report and publication target

Read repository guidance and establish the complete report: symptom, expected behavior, environment, reproduction, logs, and any supplied stack trace.

When the input points to a GitHub issue, read its body, relevant comments, linked issues, duplicates, pull requests, and attachments before diagnosing. Treat the body as historical context, not verified causality.

When no issue is specified, search open issues in the current GitHub repository using the symptom, distinctive errors, affected feature, and likely underlying behavior. Inspect candidate bodies and discussion; title similarity alone is not a duplicate.

  • One clear match → use it.
  • Several plausible matches → ask the user which issue should own the finding.
  • No clear match → plan to create an issue after diagnosis.

If GitHub access or the repository cannot be resolved, complete the diagnosis but stop before publication and state what access is missing. Honor --no-publish or an equivalent explicit request without treating publication as a failure.

2. Run the root-cause analysis

Spawn prp-core:root-cause-analyzer with the original report, complete tracker context, repository path, and any decisive runtime evidence already available. Do not give it a preferred cause or fix.

Require:

  • reproduction at the cheapest authoritative boundary when reasonably possible;
  • competing hypotheses and focused falsification;
  • a causal chain from observed symptom to the smallest fixable cause;
  • the violated invariant and its smallest responsible fix boundary: the existing or missing primitive that should own it, not merely the smallest patch;
  • rejected alternatives and explicit uncertainty;
  • a regression check that fails before the fix and passes after it.

Do not publish a UNRESOLVED diagnosis as fact. Report the missing evidence and the next investigation step instead. Publish a CONDITIONAL diagnosis only with its condition prominent.

Show full SKILL.md (226 more words)Show less

3. Reconcile duplicates with the diagnosis

For an unspecified issue, re-check the open candidates against the diagnosed behavior and cause. Reuse an issue only when it represents the same underlying problem, not merely a similar symptom.

If the diagnosis reveals that a supplied issue is a duplicate, comment on the issue the user supplied with the evidence and link the canonical open issue. Do not silently move the conversation elsewhere.

4. Publish the durable artifact

Unless publication was disabled or the current harness says its driver owns external publication:

  • Existing issue: add a concise comment containing the corrected problem statement, reproduction evidence, root cause or explicit condition, causal chain, fix boundary, regression proof, and remaining uncertainty.
  • No matching issue: create one with a concise problem-oriented title that states the observed impact and the same evidence as its body. Include expected and actual behavior and a reproducible procedure.
  • Wrong assumptions in an existing body: correct them in the comment. Rewrite the body only when the user explicitly requests --rewrite-body or its natural-language equivalent; preserve still-useful original report details.

Do not create a separate local RCA document. The GitHub issue or comment is the artifact.

Read the created or updated issue back to verify the content and capture its URL. Report the diagnosis status, one-sentence cause, publication action, issue URL, fix boundary, regression proof, and any remaining uncertainty.

© Wirasm, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/prp-debug of Wirasm/prp.

Open the folder on GitHubat commit 4352925

Compare with similar skills

Prp Debug next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Prp Debug compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Prp Debug this skillWirasm/prp2.3k—~1.1kAutomated safety check: PassMIT
Triage Issuesoftspark/ai-toolkit179—~1.3kAutomated safety check: NotesApache-2.0
Bug To Patch GeneratorArabelaTso/Skills-4-SE253—~4.4kAutomated safety check: PassApache-2.0
Issue Fixmono/SkiaSharp5.6k—~5.1kAutomated safety check: PassMIT
OpenROAD Bug FixerThe-OpenROAD-Project/OpenROAD3.2k—~784Automated safety check: PassBSD-3-Clause
Triagebot Action Bug Triagewithastro/astro63k—~639Automated safety check: PassCustom licence

Similar skills

  • Triage Issue

    softspark/ai-toolkit

    Bug triage: explores codebase for root cause, files GitHub issue with TDD fix plan.

    179 GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check: notes

  • Bug To Patch Generator

    ArabelaTso/Skills-4-SE

    Generate code fixes and patches from bug reports, failing test cases, error messages, and stack traces.

    253 GitHub stars~4.4k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed

  • Issue Fix

    mono/SkiaSharp

    Fix bugs in SkiaSharp C bindings. An agent skill from mono/SkiaSharp.

    5.6k GitHub stars~5.1k tokensUpdated today
    DevelopmentAuto-check passed

  • OpenROAD Bug Fixer

    The-OpenROAD-Project/OpenROAD

    Fixes an OpenROAD bug from a GitHub issue or error code: finds the root cause, implements the fix, adds a regression test and prepares a signed-off commit.

    3.2k GitHub stars~784 tokensUpdated today
    DevelopmentAuto-check passed

  • Triagebot Action Bug Triage

    withastro/astro

    Official

    Takes a bug report for the triagebot-action GitHub Action through reproduction, root-cause diagnosis, an intended-behavior check and a fix attempt.

    63k GitHub stars~639 tokensUpdated today
    DevelopmentAuto-check passed

  • OpenROAD Issue Triage

    The-OpenROAD-Project/OpenROAD

    Reproduces an OpenROAD GitHub bug from an attached tarball and shrinks the failing design with whittle.py so maintainers get a minimal test case.

    3.2k GitHub stars~842 tokensUpdated today
    DevelopmentAuto-check passed

More from Wirasm/prp

All 37 skills in this repo

  • PRP Loop

    Wirasm/prp

    Runs the plan, implement and review pipeline detached in fresh headless sessions, looping review and fix until the pull request is clean.

    2.3k GitHub stars~894 tokensUpdated 5 days ago
    Auto-check passed

  • PRP Loop: Autonomous Pipeline

    Wirasm/prp

    Runs a detached, resumable loop that plans, implements, opens a PR, reviews and fixes a feature across headless CLI sessions until the review is clean.

    2.3k GitHub stars~863 tokensUpdated 5 days ago
    Auto-check passed

  • PRP Workstream Orchestrator

    Wirasm/prp

    Coordinates several PRP workstreams in isolated Git worktrees from one session, verifying proof, holding merge gates and sequencing the merges.

    2.3k GitHub stars~3.5k tokensUpdated 5 days ago
    Auto-check passed

  • PRP Implementation Planner

    Wirasm/prp

    Turns a PRD, issue or description into an implementation-ready plan grounded in codebase evidence, adding root-cause analysis for bugs and publishing issue plans back to the issue.

    2.3k GitHub stars~4.1k tokensUpdated 5 days ago
    Auto-check passed

  • PRP Plan

    Wirasm/prp

    Writes an implementation-ready plan for a feature, bug fix, refactor or chore from a PRD, issue or description, grounded in codebase evidence, and can post it back to the source issue.

    2.3k GitHub stars~4k tokensUpdated 5 days ago
    Auto-check passed

  • PRP Spike

    Wirasm/prp

    Settles a feasibility question with the smallest throwaway build that could disprove it, in an isolated worktree, ending in a verdict backed by evidence instead of a PR.

    2.3k GitHub stars~3.8k tokensUpdated 5 days ago
    Auto-check passed

Works with

Categories

Questions about Prp Debug

What does Prp Debug do?

Diagnoses a bug, error, stack trace, regression, or unexplained behavior and publishes the evidence-backed root cause to GitHub. Prp Debug is an agent skill from Wirasm/prp. Diagnoses a bug, error, stack trace, regression, or unexplained behavior and publishes the evidence-backed root cause to GitHub.

When should I use Prp Debug?

Prp Debug fits situations like: the user says debug this; find the root cause; provides a bug report; asks to investigate a GitHub issue.

How do I install Prp Debug in Claude Code?

Run `npx skills add Wirasm/prp --skill prp-debug -a claude-code`. Or copy the skill folder (.claude/skills/prp-debug in Wirasm/prp) into .claude/skills/prp-debug in your project. Claude Code loads it when a task matches its description.

How do I install Prp Debug in Codex?

Run `npx skills add Wirasm/prp --skill prp-debug -a codex`. Or copy the skill folder (.claude/skills/prp-debug in Wirasm/prp) into .agents/skills/prp-debug in your project. Codex loads it when a task matches its description.

Can I use Prp Debug in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Wirasm/prp --skill prp-debug -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/prp-debug, .gemini/skills/prp-debug, .github/skills/prp-debug and .opencode/skills/prp-debug in your project.

What does Prp Debug need to run?

SKILL.md names no scripts, command-line tools or credentials: Prp Debug is instructions for the agent only.

Does Prp Debug access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Prp Debug safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Prp Debug use?

Prp Debug is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Prp Debug use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Prp Debug?

Skills that share tags, products or a category with Prp Debug: Triage Issue (softspark/ai-toolkit, 179 stars), Bug To Patch Generator (ArabelaTso/Skills-4-SE, 253 stars), Issue Fix (mono/SkiaSharp, 5.6k stars) and OpenROAD Bug Fixer (The-OpenROAD-Project/OpenROAD, 3.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Prp Debug?

Wirasm (a GitHub user) maintains it in Wirasm/prp, which has 2,258 GitHub stars. The repository holds 37 skills in this directory. The repository was last updated on October 2, 2026.

Source: Wirasm/prp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.