find-bugs
SolidRead-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]
Install
Quality Score: 83/100
Skill Content
Details
- Author
- valpere
- Repository
- valpere/session-indexer
- Created
- 2 months ago
- Last Updated
- today
- Language
- Go
- License
- Apache-2.0
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
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).
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
bug-hunter
Audit an existing codebase for verified functional, logic, runtime, concurrency, data-integrity, contract, and security bugs without fixing them. Use only when the user explicitly invokes $bug-hunter for adversarial bug finding in a repository, path, staged change, or branch diff. Not for ordinary code review, style issues, missing tests, speculative hardening, implementation, auto-fix, or remediation work.