Review code changes between a fixed point and HEAD for standards and spec compliance.
npx skills add https://github.com/docs-plus/docs.plus --skill review-docs-plus
Please help me install this Agent Skill. Skill: review Source: https://github.com/docs-plus/docs.plus/tree/main/.agents/skills/review Command: npx skills add https://github.com/docs-plus/docs.plus --skill review-docs-plus
This Skill eliminates the tedious, error-prone manual work of checking code changes for both adherence to your repo's documented coding standards and alignment with the original issue or PRD requirements, ensuring no critical gaps slip through during code review.
Use the review skill to check all changes in your current feature branch against the main branch for standards and spec compliance.
High-intent search queries and answers about installing and using this skill.
Automated code review for standards compliance and spec alignment works by running parallel checks against your repo's documented coding standards and originating issue or PRD content. This dual-axis approach generates separate findings for convention gaps and requirement mismatches without context cross-contamination.
Checking a feature branch's git diff for PRD alignment requires comparing code changes between a fixed point and the current HEAD. The system automatically detects the originating spec from commit message references, user-provided paths, or docs/specs directories to flag missing requirements.
Auditing a pull request for coding standard violations is best handled by a dedicated standards compliance check axis. It evaluates your git diff against documented standards files and reports convention gaps independently from feature spec mismatches.
Yes, you can review post-merge code changes for spec gaps by performing a change audit between a fixed point and HEAD. It automatically locates the originating spec and generates non-merged findings for standards adherence and spec alignment.
Yes, performing a change audit requires access to the repository's git history, documented standards files, and originating issue or PRD content. These inputs are necessary to generate separate findings for standards adherence and spec alignment.
Using separate sub-agents for standards compliance and spec alignment checks prevents context cross-contamination. This ensures findings for each axis remain independent and clear, so you can address convention gaps and requirement mismatches separately.
tonombCompare HEAD against a fixed point to review code standards and spec alignment.
andrewthetechieReview repository diffs against standards and spec sources.
christian289Enforce branch naming, commit message formatting, and automated pull request creation.
safzanpiraniReview code against coding standards and requirements using parallel sub-agents.
