find-bugs

Solid

Read-only bug audit of the current branch vs a base ref. Dispatches subagents per stack (Go, JS/TS, etc.), consolidates findings, produces a prioritized report. Does not fix. Usage: /find-bugs [base-ref]

AI & Automation 40 stars 1 forks Updated 2 days ago Apache-2.0

Install

View on GitHub

Quality Score: 83/100

Stars 20%
54
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Skill: /find-bugs # Bug Audit — Read-Only Audit the current branch for bugs without touching code. Produces a prioritized report; user decides what to fix. --- ## Steps ### Step 1 — Determine scope ```bash BASE="${1:-main}" # If on a feature branch: diff vs base if git rev-parse --verify "$BASE" >/dev/null 2>&1; then DIFF=$(git diff "$BASE"...HEAD) else if git rev-parse --verify --quiet HEAD~10 >/dev/null; then BASE=HEAD~10 else BASE=$(git rev-list --max-parents=0 HEAD | tail -1) fi DIFF=$(git diff "$BASE"...HEAD) fi # Fallback: on main with no base arg → recent commits if [[ -z "$DIFF" ]]; then DIFF=$(git log --since='2 weeks ago' -p --no-merges) fi echo "Auditing $(git rev-parse --abbrev-ref HEAD) vs $BASE" echo "Diff size: $(echo "$DIFF" | wc -l) lines" ``` If diff > 2000 lines: warn and ask if user wants to narrow scope (specific files or commits) before proceeding. ### Step 2 — Read project context ```bash head -100 CLAUDE.md 2>/dev/null cat .claude/context-essentials.md 2>/dev/null # Detect stack cat go.mod 2>/dev/null | head -3 cat package.json 2>/dev/null | jq -r '(.dependencies // {}) + (.devDependencies // {}) | keys | join(", ")' 2>/dev/null # Changed files by type git diff "$BASE"...HEAD --name-only | sort ``` ### Step 3 — Dispatch stack-aware subagents Dispatch **in parallel** based on detected stack. Each subagent gets: - The full diff - Project context (CLAUDE.md / context-essentials.md excerpt) - Stack-specific checklist (b...

Details

Author
valpere
Repository
valpere/session-indexer
Created
2 months ago
Last Updated
2 days ago
Language
Go
License
Apache-2.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

bug-check

Systematic bug hunt focused on patterns that survive code review and test audit — description-vs-implementation mismatches, SQL correctness, type coercion bugs, boundary/off-by-one errors, behavioral asymmetry, and input validation gaps. Derived from analysis of 40+ bugs found by Qodo and CodeRabbit that the ship-check pipeline (pr-review, code-quality, test-audit) missed. Use when asked to "bug check", "check for bugs", "deep correctness check", "look for subtle bugs", or as part of the ship-check pipeline. NOT for: code style (use code-quality), test design (use test-audit), security review (use security-review), or high-level correctness review (use pr-review).

0 Updated today
aliasunder
AI & Automation Listed

scan

Proactively hunt unobserved bugs in resting code: a read-only two-stage scan, recall-biased per-lens hunter subagents, then a separate fresh-context default-refute gate, over a target path/feature/diff or a rotated lane, emitting only verified 5-field findings. Use when: 'find a bug', 'bug hunt', 'scan for bugs', 'hunt for bugs in <X>'. Skip when: reviewing a diff (`review:code-review`); security auditing (`review:security-review`); root-causing an observed failure (`debugging:debug`); doc/config/code/arch claim drift, all dimensions (`codebase-health:audit`); structural tidying (`code-tidying:tidy`); comment markers (`work-items:scan-todos`); coverage gaps (`testing:audit`, `mutation-testing:audit`). Disambiguation: 'scan repo for issues' is the upstream known-issue registry (`claude-ops:known-issues`); 'file a bug' you already observed is `bugs:write`. Bare invocation neither edits nor files; `--track` files verified findings as raw intake (subject to the team's `filing_posture`).

16 Updated today
melodic-software
AI & Automation Solid

generate-find-bugs

Generates a project-specific /find-bugs skill with stack-specific security and correctness checklists. Run once per project. Usage: /generate-find-bugs

40 Updated 2 days ago
valpere