Real-time code feedback for pi — LSP, linters, formatters, structural analysis
Agent Claude Code
Implement a fix for a pi-lens issue as a branch plus PR. Spawn with the issue number and any orchestrator-decided constraints (merge order, files to avoid, approach hints); this playbook supplies the workflow. Use sonnet for well-specified contained fixes, opus (via model override) for cross-cutting or semantically…
Agent Claude Code
Log-forensics and root-causing for pi-lens runtime behavior — inconclusive rates, stale findings, silent degradations, crash attribution, dogfood-session anomalies. Use when the question is "what actually happened and why", not "apply this fix". Spawn with the symptom (quotes, timestamps, session context) and the…
Agent Claude Code
Adversarial pre-merge review of a pi-lens PR. Use for every PR before merge, including small and self-authored ones. Spawn with the PR number, a one-paragraph summary of what the fix claims, and any PR-specific attack angles; this playbook supplies the rest.