bug-report

Category: Testing & Security | Uploader: KilimcininKorOglu | Downloads: 0 | Version: v1.0（Latest）

This skill MUST be invoked when the user says "bug report", "bug raporu", "hata raporu", "bug analizi", "find bugs", "hataları bul" or any variation requesting systematic bug analysis. SHOULD also invoke when user mentions "security audit", "code review for bugs", "güvenlik taraması", or asks to scan the codebase for issues. Analyzes the entire repository to identify and document all bugs systematically. Creates a BUG-REPORT.md with severity-ranked findings, root cause analysis, and recommendations.

Changelog: Source: GitHub https://github.com/KilimcininKorOglu/cli-tweaks

Directory Structure

Current level: claude/skills/bug-report/

📄 SKILL.md 3.6 KB

SKILL.md

---
name: bug-report
description: >
  This skill MUST be invoked when the user says "bug report", "bug raporu",
  "hata raporu", "bug analizi", "find bugs", "hataları bul" or any variation
  requesting systematic bug analysis. SHOULD also invoke when user mentions
  "security audit", "code review for bugs", "güvenlik taraması", or asks to
  scan the codebase for issues. Analyzes the entire repository to identify
  and document all bugs systematically. Creates a BUG-REPORT.md with
  severity-ranked findings, root cause analysis, and recommendations.
argument-hint: "[--severity critical|high|medium|low|all]"
---

# Bug Analysis & Report

Analyze the entire repository to identify and document all bugs systematically.

## Usage

```bash
/bug-report                    # Full analysis, all severities
/bug-report --severity high    # Filter by severity
```

## Process

### Step 1: Repository Assessment

Map the project structure:
- Identify technology stack and dependencies
- Find main entry points and critical paths
- Check for existing tests and linting configurations
- Look for existing `BUG-REPORT.md` to continue ID sequence
- Scan for `TODO`, `FIXME`, `HACK`, `XXX`, `BUG` comments

### Step 2: Bug Discovery

Scan for these categories:

| Severity | Examples                                                                  |
|----------|---------------------------------------------------------------------------|
| CRITICAL | SQL injection, XSS, CSRF, auth bypass, data corruption, crashes, leaks   |
| HIGH     | Logic errors, race conditions, missing validation, wrong API contracts    |
| MEDIUM   | Swallowed exceptions, edge cases, integration problems                    |
| LOW      | Deprecated APIs, dead code, N+1 queries, technical debt                   |

### Step 3: Document Each Bug

```
BUG-[ID]: [Brief description]
Severity: CRITICAL | HIGH | MEDIUM | LOW
Status: NEW | CONFIRMED | IN_PROGRESS | FIXED | WONT_FIX
File: [path/to/file.ext:line_number]
Component: [affected module/feature]

Problem: [What's wrong - current behavior]
Expected: [What should happen]
Root Cause: [Why it happens - if determinable]
Impact: [User/system/business impact]
```

### Step 4: ID Management

Bug IDs must never reset. Always increment from the highest existing ID.
Check `BUG-REPORT.md`, `bugs.md`, `bug.md` for existing IDs.
If no existing bugs, start from BUG-001.

### Step 5: Generate Report

Save to `BUG-REPORT.md` in repository root:

```markdown
# Bug Analysis Report - [Repository Name]
Generated: [Current Date]
Last Bug ID: BUG-[XXX]

## Summary
| Severity     | Count |
|--------------|-------|
| Critical     | X     |
| High         | X     |
| Medium       | X     |
| Low          | X     |
| **Total**    | **X** |

## Critical Bugs (Immediate Attention Required)
[List critical bugs first]

## All Bugs
| ID      | Severity | Status | File              | Description |
|---------|----------|--------|-------------------|-------------|
| BUG-001 | CRITICAL | NEW    | path/file.ext:42  | Description |

## Recommendations
[Suggested fixes and preventive measures]
```

## Priority Order

1. Security vulnerabilities (always first)
2. Data corruption risks
3. System crashes
4. Functional bugs by user impact
5. Code quality issues

## Notes

- Be thorough but avoid false positives
- For complex bugs, explain potential solutions without implementing
- Respect existing code patterns when suggesting fixes
- Group related bugs together
- If `bugs.md` or `bug.md` exists, merge into new report and delete old file
- IMPORTANT: Always write the report in English only, regardless of conversation language

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

bug-report

Directory Structure

SKILL.md

Report

Notice