janjaszczak/cursor

troubleshooting-rca

Perform root-cause analysis for bugs/errors/regressions using logs, repro steps, and hypothesis testing. Use when the user reports “nie działa”, stack traces, failing tests, or regressions.

First seen Feb 21, 2026

Installation

$ npx skills add janjaszczak/cursor --skill troubleshooting-rca

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from janjaszczak/cursor · top by installs.

npx skills add janjaszczak/cursor

Browse all from janjaszczak/cursor

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

CompatibilityRequires access to logs/tests and ability to run minimal diagnostics.
Allowed toolsBash(*) Read FileSearch(*)
More metadata
intent
Avoid RCA ritual when building greenfield features.

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,189 B
  • docs SUMMARY.md 221 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 8 installs

SKILL.md

troubleshooting-rca

Activation gate (anti-noise)

Activate when:

  • There is an error message, failing test, crash, regression, unexpected behavior, or logs.

Skip when:

  • User requests implementation from scratch and no failure exists yet.

Procedure

  1. Restate symptom + expected behavior.
  2. Collect minimal repro:

- Command, input, environment, last known good commit.

  1. Hypotheses (max 3) ranked by likelihood.
  2. Test each hypothesis with the smallest possible check.
  3. Before Fix: Root cause must be clearly stated; one minimal verification step must be given. Then: Fix + verify with test/run.
  4. Add a prevention note (test, guard, logging).

Output

  • Symptom → Most likely cause → Fix → Verification command(s).