code-review

You can review staged changes, explicitly named file paths, or auto-discovered source and test files. The skill runs parallel security, quality, and architecture checks simultaneously to surface actionable findings before merge.

Automating code quality checks for TypeScript files uses parallel subagents to analyze security, quality, and architecture simultaneously, deduplicates findings against open beads tasks, and serializes task creation for each issue found.

Yes, targeted file review supports staged changes, explicitly named paths, and auto-discovered TypeScript files in common source and test folders, allowing you to scope the parallel security, quality, and architecture analysis to relevant changes only.

Parallel code review applies to both source and test TypeScript files. It auto-discovers files in common source and test folders, running security, quality, and architecture checks across all discovered files before merge.

The code review process deduplicates findings against open beads tasks before creating new ones. Each unique issue is serialized into an individual beads task, ensuring teams can track follow-ups without duplicate work.

Automated parallel analysis is designed for file-level reviews during development, including staged changes and named paths. It is not suited for repository-wide historical audits or non-TypeScript codebases outside its security, quality, and architecture scope.