skills.rest
JohannesKonings
JohannesKoningsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

code-review

Compare git diffs against coding standards and project specifications.

9|Updated Dec 1, 2025
Search Tags:#git#quality assurance#static analysis#code review#refactoring#spec validation
One-click install
npx skills add https://github.com/JohannesKonings/tanstack-aws --skill code-review-johanneskonings
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/JohannesKonings/tanstack-aws/tree/main/.agents/skills/code-review
Command: npx skills add https://github.com/JohannesKonings/tanstack-aws --skill code-review-johanneskonings

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of inconsistent code quality and scope creep by performing a rigorous, two-axis review of code changes against both technical standards and project specifications.

Core Features & Use Cases

  • Standards Enforcement: Automatically checks code against documented repository standards and a baseline of industry-standard code smells.
  • Spec Validation: Ensures that the implementation faithfully adheres to the originating issue or PRD, identifying missing requirements or scope creep.
  • Use Case: Use this during a pull request to ensure your new feature implementation follows the team's coding conventions while simultaneously verifying that all requirements from the associated Jira ticket or GitHub issue are fully met.

Quick Start

Ask the agent to perform a code review on the current branch by comparing it against the main branch.

Frequently Asked Questions about code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate code reviews against project specifications and coding standards?▼

Automate code reviews by comparing git diffs against documented coding standards and originating project specifications. This dual-axis approach validates functional requirements from issue trackers while analyzing code quality using Fowler code smells.

How do I check a pull request for scope creep and missing requirements?▼

Check pull requests for scope creep by validating implementation against originating issue or PRD requirements. Spec validation identifies missing functional requirements and flags scope creep by comparing git diffs to project specifications.

What is the best way to detect technical debt and code smells in a git diff?▼

Detect technical debt by analyzing git diffs using a predefined set of Fowler code smells. This standards enforcement checks code changes against documented repository standards to provide side-by-side reports on technical debt.

Can I validate functional requirements from a Jira ticket or GitHub issue during a code review?▼

Validate functional requirements from Jira tickets or GitHub issues by comparing code changes against originating project specifications. Spec validation ensures implementation faithfully adheres to the PRD and identifies missing requirements.

Does this code review approach work with documented repository standards and issue trackers?▼

This code review approach works with documented repository standards and issue trackers by orchestrating parallel sub-agents. These sub-agents provide side-by-side reports on technical debt and feature completeness against project specifications.

When should I use a dual-axis code review for static analysis and spec validation?▼

Use a dual-axis code review during pull requests to ensure feature implementations follow team coding conventions while verifying requirements are met. This solves inconsistent code quality and scope creep by reviewing technical standards and specifications simultaneously.

Related Skills

Explore More Software Engineering Skills→
FrantssFrantss

code-review

Compare git diffs against repository standards and project specifications.

Community
Advanced
alfredoperezalfredoperez
80

code-review

Review code changes against coding standards and specification requirements in parallel.

Community
Advanced
tonombtonomb

code-review

Compare HEAD against a fixed point to review code standards and spec alignment.

Community
Advanced
hachejhachej
45

code-review

Compare git diffs against repository standards and functional specifications.

Community
Advanced