00PrabalK00/bug-reproduction-root-cause-hunter
skills/bug-reproduction-root-cause-hunter/SKILL.md
Reproduce reported bugs, isolate failure conditions, inspect recent changes, test root-cause hypotheses, and propose the smallest safe fix plan. Use for vague "it broke" reports, flaky regressions, failing tests, or production issue investigations.
testing
Updated Mar 23, 2026
$ install --global
skillsauthnpx skillsauth add 00PrabalK00/claude-skills bug-reproduction-root-cause-hunterInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
4 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
4
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 23, 2026, 11:40 PM67.8s2 files scanned
SKILL.md
- name:
- bug-reproduction-root-cause-hunter
- description:
- Reproduce reported bugs, isolate failure conditions, inspect recent changes, test root-cause hypotheses, and propose the smallest safe fix plan. Use for vague "it broke" reports, flaky regressions, failing tests, or production issue investigations.
Bug Reproduction Root Cause Hunter
Overview
Turn loose bug reports into a repeatable debugging workflow with evidence at each step.
Core Workflow
- Normalize the report. Capture expected behavior, actual behavior, exact errors, inputs, and environment details.
- Reproduce the failure. Use existing tests, app commands, logs, or a minimal repro path before theorizing.
- Narrow the surface. Identify the smallest set of files, conditions, flags, data states, or requests needed to trigger the bug.
- Test hypotheses. Inspect recent diffs, surrounding code, and related tests to validate likely causes.
- Propose the fix path. Recommend the smallest safe change, the regression test to add, and any rollout concerns.
Deliver
- Provide exact repro steps when reproduction succeeds.
- State the most likely root cause with concrete evidence.
- If reproduction fails, document what was tried, what remains plausible, and the next best experiment.
- Keep the fix plan separate from the diagnosis.
Guardrails
- Do not claim certainty without evidence.
- Prefer recent changes and environment differences as early suspects, not automatic conclusions.
- Preserve any raw error output needed to debug further.
Related Skills
00PrabalK00/vendor-evaluation-scorecard
tools
VerifiedTrustedCommunity
Compare vendors or tools using weighted criteria, tradeoffs, risks, and recommendation logic. Use when selecting platforms or partners.
SKILL.mdUpdated Mar 23, 2026
00PrabalK00/user-interview-synthesizer
data-ai
VerifiedTrustedCommunity
Extract needs, pain points, quotes, and behavioral patterns from user interviews. Use when synthesizing qualitative research.
SKILL.mdUpdated Mar 23, 2026
00PrabalK00/user-feedback-clusterer
databases
VerifiedTrustedCommunity
Group user feedback into themes, bugs, requests, sentiment, and confusion points. Use when analyzing feedback corpora.
SKILL.mdUpdated Mar 23, 2026
00PrabalK00/test-writer-coverage-closer
testing
VerifiedTrustedCommunity
Find missing coverage, design useful unit or integration tests, add fixtures or mocks, and explain remaining edge cases. Use when a feature lacks tests, a bug needs regression coverage, or coverage gaps block confidence.
SKILL.mdUpdated Mar 23, 2026