code-review

Compare git revision ranges and generate standards and specification reports.

Updated May 3, 2026
One-click install
npx skills add https://github.com/druejaramillo/skills --skill code-review-druejaramillo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/druejaramillo/skills/tree/main/project/code-review
Command: npx skills add https://github.com/druejaramillo/skills --skill code-review-druejaramillo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of inconsistent or superficial code reviews by enforcing a structured, evidence-based methodology that ensures proposed changes meet specific requirements and engineering standards.

Core Features & Use Cases

  • Standards Assessment: Evaluates code against repository conventions, architecture decisions, and quality benchmarks.
  • Requirement Traceability: Maps proposed changes directly to stated acceptance criteria or issues to ensure the implementation matches the intent.
  • Use Case: Use this when you need an independent, thorough audit of a pull request to identify potential bugs, architectural flaws, or deviations from project requirements before merging.

Quick Start

Use the code-review skill to analyze the changes between the main branch and the feature-login branch against the current requirements.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I perform an evidence-based code review on a git pull request?

Evidence-based code review requires comparing a three-dot git revision range between base and head revisions to rigorously assess proposed changes against engineering standards and functional specifications.

What is requirement traceability in a code review?

Requirement traceability in code review maps proposed git diff changes directly to stated acceptance criteria or issues, ensuring the implementation matches the original intent before merging.

How do I analyze a git diff against engineering standards before merging?

Analyzing a git diff against engineering standards requires a clear base and head revision range plus explicit requirement documentation to generate separate standards and specification reports.

Do I need explicit requirement documentation to run a code review?

Yes, explicit requirement documentation is required to run this code review process, as it maps proposed changes to acceptance criteria and generates a specification compliance report.

Can I use a code review skill to assess branch changes against repository conventions?

Yes, you can assess branch changes against repository conventions by providing a three-dot git revision range to evaluate architecture decisions and quality benchmarks.

What are the limitations of automated pull request code analysis?

Automated pull request code analysis is limited to read-only assessment and cannot execute code, requiring a clear git revision range and explicit documentation to function properly.