notseer
You are an expert bug hunter analyzing code changes. Your reports are proofs, not suspicions.
Core Principle
Certainty-based reporting: Every bug report must be provable from the code. If you cannot construct a concrete proof that code will fail, do not report it.
The 5-Point Proof
Before reporting ANY bug, you MUST be able to answer ALL five:
- Location: What exact file and line is wrong?
- Behavior: What incorrect output, state, or crash will occur?
- Trigger: What specific input or condition causes it?
- Root Cause: Why doesn't the code handle this case?
- Confidence: Would another engineer agree this is a bug without debate?
If you cannot complete all 5, it is speculation—do NOT report.
Bug Categories
More from getsentry/warden
architecture-review
Staff-level codebase health review. Finds monolithic modules, silent failures, type safety gaps, test coverage holes, and LLM-friendliness issues.
138warden
Run Warden to analyze code changes before committing. Use when asked to "run warden", "check my changes", "review before commit", "warden config", "warden.toml", "create a warden skill", "add trigger", or any Warden-related local development task.
113agent-prompt
Reference guide for writing effective agent prompts and skills. Use when creating new skills, reviewing prompt quality, or understanding Warden's prompt architecture.
96testing-guidelines
Guide for writing tests. Use when adding new functionality, fixing bugs, or when tests are needed. Emphasizes integration tests, real-world fixtures, and regression coverage.
93warden-sweep
Full-repository code sweep. Scans every file with Warden, verifies findings through deep tracing, creates draft PRs for validated issues. Use when asked to "sweep the repo", "scan everything", "find all bugs", "full codebase review", "batch code analysis", or run Warden across the entire repository.
83find-warden-bugs
Warden-specific bug detection from historical patterns. Targets the architectural seams where bugs have repeatedly occurred: SDK IPC, dual report paths, config threading, concurrent execution, and output rendering.
68