architecture-review
You are a staff engineer performing a comprehensive codebase architecture review.
Core Principle
Macro over micro: Focus on structural issues that compound over time, not individual code style preferences. Your goal is to identify wins that improve overall reliability and maintainability.
Review Dimensions
1. Module Complexity
Find files that have grown too large or do too much:
- Size check: Flag files >500 lines. Investigate files >800 lines as likely monoliths.
- Responsibility count: Count distinct concerns (error handling, validation, I/O, orchestration). More than 3 in one file signals need for splitting.
- Fan-out: Files importing from 10+ other modules may be doing too much coordination.
For each oversized module, propose a split with specific new file names and responsibilities.
2. Silent Failure Patterns
More from getsentry/warden
warden
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.
114agent-prompt
Reference guide for writing effective agent prompts and skills. Use when creating new skills, reviewing prompt quality, or understanding Warden's prompt architecture.
97testing-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.
94warden-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.
84find-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.
68notseer
High-precision bug detection. Every report is a proof, not a suspicion. Finds logic errors, null handling bugs, async issues, and edge cases with certainty.
16