sandman-self-review

To run a parallel code review for standards and specification adherence, execute the self-review skill on your branch. It simultaneously checks code changes against documented coding standards and originating specifications to identify deviations.

Specification adherence checking validates that code changes match the originating work item or PRD requirements. This review process ensures your branch aligns with external specification demands while maintaining internal coding standards.

Yes, you need git to check code changes against coding standards. Git is required for diffing and identifying commits, and you may need additional tools for comprehensive standards checking during the parallel review process.

You can validate branch compliance against both internal standards and external PRD requirements. The parallel review process simultaneously checks your code changes against documented coding standards and originating specification requirements.

The best way to identify deviations from coding standards is running a parallel review on your branch. This process simultaneously evaluates code changes against documented standards and specifications to pinpoint any compliance gaps.

When checking specification compliance, limitations include the dependency on git for diffing and identifying commits. Additionally, you may require supplementary external tools to perform comprehensive standards checking on your code changes.