gk-reviewer

Review code diffs against project specifications and conventions.

1|Updated Jul 4, 2026
One-click install
npx skills add https://github.com/gkganesh12/gk-stack --skill gk-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gk-reviewer
Source: https://github.com/gkganesh12/gk-stack/tree/main/starter/.claude/skills/gk-reviewer
Command: npx skills add https://github.com/gkganesh12/gk-stack --skill gk-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates subjective or speculative code reviews by enforcing a strict, contract-based evaluation of changes against project specifications and established conventions.

Core Features & Use Cases

  • Contract-Based Review: Validates code strictly against provided specs, tickets, or task descriptions.
  • Rule Enforcement: Automatically checks for violations of project-specific conventions and learned rules defined in CLAUDE.md.
  • Use Case: Use this skill when you need a rigorous, unbiased second opinion on a pull request to ensure correctness, security, and adherence to project standards without getting bogged down in style preferences.

Quick Start

Use the gk-reviewer skill to perform a fresh-eyes review of the changes in the current branch against the project requirements.

Frequently Asked Questions about gk-reviewer

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

FAQPage Schema
How do I perform an objective code review against project specifications?

To perform an objective code review, compare your git diffs against project specifications and ticket descriptions to evaluate correctness, contract adherence, and security vulnerabilities while ignoring subjective style preferences.

Can I automate git static analysis to enforce project conventions?

Yes, you can automate git static analysis to check for violations of project-specific conventions and learned rules defined in your configuration files, providing severity-ordered feedback for actionable corrections.

What is requirement-focused code review and when do I need it?

Requirement-focused code review is a contract-based evaluation that validates code changes strictly against provided specs. You need it when ensuring pull request correctness and security without getting bogged down in subjective style preferences.

Do I need project documentation and git diff history to review a pull request?

Yes, you need access to project documentation and git diff history to provide actionable, severity-ordered feedback. These inputs allow the review to enforce strict, contract-based evaluation against established conventions.

What's the best way to check code for security vulnerabilities and rule adherence?

The best way to check code for security vulnerabilities is to evaluate diffs against established conventions and project specifications, automatically detecting rule violations while filtering out subjective style debates.

Why does my code review keep focusing on style instead of correctness?

Code reviews often focus on style due to subjective preferences. To shift focus to correctness and contract adherence, enforce a strict, contract-based evaluation of changes against project specifications and established conventions.