bug-analysis
Analyzes software bugs including root cause identification, severity assessment, impact analysis, reproduction steps validation, and fix recommendations. Performs bug triage, categorization, duplicate detection, and regression analysis. Use when investigating bugs, analyzing crash reports, triaging issues, debugging problems, reviewing error logs, or when users mention "analyze bug", "investigate issue", "debug problem", "bug report", "crash analysis", "root cause analysis", or "fix recommendation".
npx skills add majiayu000/claude-skill-registry --skill bug-analysis-dauquangthanh-hanoi-rainbow --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Bug Analysis ## Overview This skill provides systematic bug analysis to identify root causes, assess impact, classify severity, and generate actionable fix recommendations. It helps triage bugs efficiently and provides structured analysis for development teams. ## Core Analysis Workflow ## Step 1: Initial Triage & Information Gathering **Collect Essential Information:** - Bug description and symptoms - Reproduction steps (verify they work) - Expected vs actual behavior - Environment details (OS, browser, version, config) - Error messages, stack traces, logs - Screenshots or videos - User impact and frequency **Quick Assessment:** - Severity: Critical/High/Medium/Low - Type: Functional/Performance/Security/UI/Data/Integration/Configuration/Regression - Priority: Based on severity + business impact - Potential duplicates: Search existing issues ### Step 2: Bug Categorization **Severity Classification** (see [severity-guidelines.md](references/severity-guidelines.md) for detailed criteria): **Critical (P0)** - Response: Immediate (<1 hour) - System outage, data loss, security breach, no workaround **High (P1)** - Response: Same day - Major feature broken, significant user impact (>2
- Overview
- Core Analysis Workflow
- Step 1: Initial Triage & Information Gathering
- Step 2: Bug Categorization
- Step 3: Root Cause Analysis
- Step 4: Impact Assessment
- Step 5: Fix Recommendation
- Output Format
- Special Analysis Scenarios
- Security Vulnerabilities
- Performance Issues
- Crash Analysis
- Investigation Tools & Commands
- Best Practices
Service status systemctl status service_name Resource usage top -bn1 | head -20 # CPU ps aux --sort=-%mem | head -10 # Memory du -sh /* | sort -rh | head -10 # Disk Recent changes git log --since="1 day ago" --oneline Error analysis tail -100 /var/log/app.log | grep -i error
What does the bug-analysis skill do?
Analyzes software bugs including root cause identification, severity assessment, impact analysis, reproduction steps validation, and fix recommendations. Performs bug triage, categorization, duplicate detection, and regression analysis. Use when investigating bugs, analyzing crash reports, triaging issues, debugging problems, reviewing error logs, or when users mention "analyze bug", "investigate issue", "debug problem", "bug report", "crash analysis", "root cause analysis", or "fix recommendation".
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill bug-analysis-dauquangthanh-hanoi-rainbow --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.