best-practices-reviewer

To enforce best-practices compliance, you need a process that verifies validation steps, checks for testing, and prompts clarifying questions when evaluation criteria are missing. This ensures plans precede major changes and guides corrective actions.

Maintaining context hygiene requires requesting concrete targets, recommending sub-agents to scope investigations without polluting the main context, and suggesting context resets when repeated fixes are detected across long-running sessions.

To ensure a plan precedes large or cross-file code changes, implement a plan-before-implement discipline that mandates exploration, planning, and cautious implementation before any major modifications are applied.

Iteration guardrails are needed to detect repeated fixes during development. When repeated fixes occur, the guardrails suggest a context reset to prevent context pollution and restore effective implementation.

Yes, you can use sub-agents to scope investigations without polluting the main context. Sub-agent guidance ensures exploratory actions remain isolated, preserving context hygiene across the implementation process.

You should prompt for clarifying questions during a code review when evaluation criteria are missing. This surfaces concrete improvement questions and guides the user toward corrective actions before changes are finalized.