staff-review

A staff-level code review analyzes local branches, repos, or files for deep structural quality. It differs by cross-referencing plans in docs/plans/ or chronicles in docs/chronicles/ to verify findings with full context before presenting audit-ready results.

Automate deep code reviews on a local branch by dispatching the staff-reviewer subagent. The process identifies review scope from user input, reads associated plans or chronicles, and coordinates with auxiliary skills to verify findings.

Yes, scope-aware code review can target specific files, directories, or entire repositories. The process determines what to review from user input and applies associated plans or chronicles to ensure contextually relevant analysis.

Existing plans or chronicles are utilized when available but are not strictly required. The staff review process can analyze branches, files, or changes directly, coordinating with auxiliary skills or online resources to verify findings independently.

Document code review findings for future audits by generating audit-ready output. This structured format returns findings with rationale, suggested fixes, and traceable context derived from the reviewed plans, chronicles, or branch changes.

The staff-reviewer subagent coordinates with auxiliary skills by leveraging them to verify findings during scope-based analysis. It reads user input, locates relevant context, and uses these tools alongside online resources before presenting results.