Compare git diffs against repository standards and functional specifications.
npx skills add https://github.com/hachej/boring-ui --skill code-review-hachej
Please help me install this Agent Skill. Skill: code-review Source: https://github.com/hachej/boring-ui/tree/main/.agents/skill-library/mattpocock/code-review Command: npx skills add https://github.com/hachej/boring-ui --skill code-review-hachej
This skill addresses the inconsistency and cognitive load of manual code reviews by providing a structured, dual-perspective analysis that separates technical standards from functional requirements.
Ask the agent to perform a code review on the current branch by comparing it against the main branch.
High-intent search queries and answers about installing and using this skill.
Automated code review for pull requests is performed by comparing git diffs against repository standards and functional specifications. The system orchestrates parallel sub-agent execution to analyze code quality and validate implementation against linked issue trackers.
Yes, you can validate git diffs against a Jira ticket or GitHub issue by verifying the implementation aligns with the originating issue, PRD, or feature request. This spec validation provides independent reports on requirement fulfillment.
Static analysis handles Fowler code smells during refactoring by evaluating code against a predefined set of recognized smells. This standards analysis identifies technical debt and ensures the implementation follows documented repository conventions.
The best way to check software quality in a complex pull request is using a dual-axis analysis that separates technical standards from functional requirements. This structured approach evaluates coding conventions while simultaneously confirming the specific problem is solved.
Yes, this code review approach works without external dependencies. It performs a dual-perspective analysis directly on the current branch by comparing it against the main branch to provide independent reports on technical debt and requirement fulfillment.
You should not use automated code review for your branch if you need a subjective assessment of code style rather than a structured comparison against documented repository standards, Fowler code smells, and functional specifications.
mvillmowCreate a GitHub pull request linked to a specified issue.
travisjneumanAnalyze codebases for technical debt using Python static analysis scripts.
Kushal9889Sets up Husky git hooks to automate code quality checks and testing before commits.
willdadyCompare git diffs against coding standards and project specifications.
