Borrowing it
Nothing to install: this file belongs to plipowczan/claude-piv-skeleton. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/plipowczan/claude-piv-skeleton/main/.claude/commands/bug_fix/rca.mdgit clone --depth 1 https://github.com/plipowczan/claude-piv-skeletonWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/plipowczan/claude-piv-skeleton/rca)<a href="https://agentmods.dev/commands/plipowczan/claude-piv-skeleton/rca"><img src="https://agentmods.dev/badge/commands/plipowczan/claude-piv-skeleton/rca/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/plipowczan/claude-piv-skeleton/rca"><img src="https://agentmods.dev/badge/commands/plipowczan/claude-piv-skeleton/rca.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00011 | $0.01844 |
| Opus 5 | $0.00005 | $0.00922 |
| Sonnet 5 | $0.00002 | $0.00369 |
| Haiku 4.5 | $0.00001 | $0.00184 |
Grade A, and why
rca scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 321 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Root Cause Analysis (RCA)
Bug Source
Determine the source and analyze accordingly:
Option 1: GitHub Issue
$ARGUMENTS
Example: https://github.com/your-org/repo/issues/123 or just 123
Option 2: Direct Bug Description
direct:Bug description here
Example: direct:Properties with special characters in address cause geocoding to fail
Purpose
Create a comprehensive Root Cause Analysis document for a bug or issue.
Goal: Understand the problem deeply before implementing a fix.
RCA Process
1. Understand the Issue
If analyzing a GitHub Issue:
- Issue title and number
- Issue description
- Steps to reproduce
- Expected behavior
- Actual behavior
- Screenshots/logs if provided
- Labels, milestones, assignee
- Use
gh issue view <number>to get full issue details
If analyzing a direct bug description:
- Parse the bug description from user input
- Ask clarifying questions if needed:
- What is the expected behavior?
- What is the actual behavior?
- How can this be reproduced?
- What is the impact (critical/high/medium/low)?
- Which users or use cases are affected?
- Gather additional context:
- When did this start happening?
- Was it working before?
- Any recent changes that might have caused it?
Clarify Ambiguities:
- If description is unclear, ask questions
- Get reproduction steps if missing
- Understand the impact (critical/high/medium/low)
- Identify affected users or use cases
2. Reproduce the Issue
Can you reproduce it?
- Yes - Successfully reproduced
- No - Cannot reproduce
- Partially - Can reproduce some scenarios
Reproduction Steps:
- Step 1: [Description]
- Step 2: [Description]
- Step 3: [Description]
- Step 4: [Issue occurs]
Environment:
- Mode: LOCAL / PRODUCTION (as applicable)
- Browser (if applicable):
- Data: [Specific data that triggers issue]
3. Analyze the Code
Find Related Code:
# Search for relevant files
grep -r "keyword" backend/src/main/java/
grep -r "keyword" frontend/src/
# Find related controllers
find backend/src/main/java -name "*Controller.java"
# Find related services
find backend/src/main/java -name "*Service.java"
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 321 lines · 11 tokens per session scan A 6f59cf06978b
rca is a command published in the GitHub repository plipowczan/claude-piv-skeleton (4 stars, last pushed 7mo ago), licensed MIT. It adds 11 tokens to every session and 1,844 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.