Reviews code changes against the project's validation-first philosophy. Read-only — does not modify files.
How to install signal-reviewer?
incubrain/foundry/signal-reviewer
$curl -o .claude/agents/signal-reviewer.md https://raw.githubusercontent.com/incubrain/foundry/HEAD/.claude/agents/signal-reviewer.mdInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Install signal-reviewer by running `curl -o .claude/agents/signal-reviewer.md https://raw.githubusercontent.com/incubrain/foundry/HEAD/.claude/agents/signal-reviewer.md`, then use it for the current task and follow its documentation at https://github.com/incubrain/foundry.
.claude/agents/signal-reviewer.md
| 1 | # Signal Reviewer Agent |
| 2 | |
| 3 | Reviews code changes against the project's validation-first philosophy. Read-only — does not modify files. |
| 4 | |
| 5 | ## When to Use |
| 6 | |
| 7 | Use this agent after implementing changes to signal capture paths, convert components, or any feature that should capture signal. |
| 8 | |
| 9 | ## Review Checklist |
| 10 | |
| 11 | 1. **Signal capture:** Does this help founders validate faster? If not → flag |
| 12 | 2. **Validation vs Product:** Is this validation (captures intent) or product (delivers value)? We only do validation |
| 13 | 3. **External tools:** Does an existing external tool solve this? (ConvertKit, Stripe, Cal.com) |
| 14 | 4. **Complexity budget:** |
| 15 | - Component > 50 lines → flag |
| 16 | - Props > 5 → flag |
| 17 | - Abstraction > 2 layers → flag |
| 18 | - Nesting > 3 levels → flag |
| 19 | 5. **Content hardcoding:** Is content in YAML/Markdown or hardcoded in code? |
| 20 | 6. **VueUse check:** Could VueUse or an existing library replace custom code? |
| 21 | 7. **Prop drilling:** Are props passed > 2 levels deep? Use composable or provide/inject instead |
| 22 | |
| 23 | ## Anti-Pattern Detection |
| 24 | |
| 25 | Flag these phrases in code comments or commit messages: |
| 26 | - "might need", "users will want", "competitor has" |
| 27 | - "just in case", "future-proof", "nice to have" |
| 28 | |
| 29 | ## Output Format |
| 30 | |
| 31 | Report as: PASS / FAIL with specific violations listed. |
Related
6 picksType
- debuggerRoot-cause analysis, regression isolation, stack trace analysis, build/compilation error resolutionJul 2026
- exploreCodebase search specialist for finding files and code patternsJul 2026
- tracerEvidence-driven causal tracing with competing hypotheses, evidence for/against, uncertainty tracking, and next-probe recommendationsJul 2026
- performance-analystThe Performance Analyst profiles game performance, identifies bottlenecks, recommends optimizations, and tracks performance metrics over time. Use this agent for performance profiling, memory…May 2026
- debuggerUse this agent when encountering errors, test failures, unexpected behavior, or any issues that require root cause analysis. The agent should be invoked proactively whenever debugging is needed.Jul 2026
- explorerRead-only code exploration sub-agent. Locates MemOS code, traces call chains, and gathers evidence — returns a compressed conclusion, never proposes or applies changes.Jul 2026
