Review pull requests against CLAUDE.md, prd.json, or design docs.
npx skills add https://github.com/skenklok/ai-dev-utility --skill pr-review-skenklok
Please help me install this Agent Skill. Skill: pr-review Source: https://github.com/skenklok/ai-dev-utility/tree/main/.agent/skills/pr-review Command: npx skills add https://github.com/skenklok/ai-dev-utility --skill pr-review-skenklok
PR reviews can be time-consuming and error-prone when verifying alignment with specifications; this skill streamlines the process and delivers precise, actionable feedback.
Provide the PR branch name and the specification to review, and I will generate a GitHub-ready review with actionable fixes.
High-intent search queries and answers about installing and using this skill.
Automating code review against specifications involves validating PR branches against design documents like CLAUDE.md or prd.json to generate actionable feedback. The process checks spec compliance, code complexity, and test adequacy to produce GitHub-ready reports.
Yes, you can validate PR compliance with CLAUDE.md and prd.json files by reviewing branch changes against these provided design documents. The review checks alignment, applies security checks, and outputs concrete findings with recommended fixes.
The best way to generate GitHub-ready PR review reports is to run an automated spec-aligned review that evaluates code changes against provided specifications. This produces concrete findings and actionable fixes formatted for direct collaboration on GitHub.
Spec compliance review includes security checks and test adequacy validation as part of a multi-faceted evaluation. It assesses code complexity and compliance alongside specification alignment to ensure comprehensive PR coverage.
To start a spec-aligned PR review, you need to provide the PR branch name and the specification document, such as a design doc, CLAUDE.md, or prd.json. The review then evaluates the feature work and generates guidance for fixes.
Automated PR review is limited to verifying alignment with the specifications you provide, meaning it cannot evaluate undocumented requirements. It relies on the accuracy of your design docs to generate concrete findings and recommended test validations.
KamiJeongValidate Git branch names against sequential or timestamp feature patterns.
p-o-ke-naeGuide GitHub Flow branching, commits, testing, pull requests, and squash merges.
nicolehaugenAutomate addressing GitHub pull request feedback with user confirmation.
rsmdtValidate implementations against documented specifications with structured compliance reporting.
