code-review

Structure code review feedback with technical validation and YAGNI principles.

Updated Dec 20, 2025
One-click install
npx skills add https://github.com/chronista-club/claude-plugin-chronista-style --skill code-review-chronista-club
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/chronista-club/claude-plugin-chronista-style/tree/main/code-review
Command: npx skills add https://github.com/chronista-club/claude-plugin-chronista-style --skill code-review-chronista-club

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenges of ineffective code reviews by establishing clear principles and actionable steps for both requesting and receiving feedback, ensuring technical integrity and preventing performative agreement.

Core Features & Use Cases

  • Requesting Reviews: Provides a structured process for initiating code reviews, specifying what information to share and how to respond to feedback.
  • Receiving Reviews: Outlines a disciplined approach to handling feedback, emphasizing technical validation over emotional responses and prohibiting performative agreement.
  • Handling Ambiguity: Guides users on how to address unclear feedback by seeking clarification before implementation.
  • External Reviewer Interaction: Offers strategies for responding to feedback from external reviewers, including technical validation and context checks.
  • YAGNI Enforcement: Integrates the "You Ain't Gonna Need It" principle to prevent unnecessary feature creep during reviews.

Quick Start

Use the code-review skill to request a review for your latest changes 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 handle ambiguous feedback during a code review?

To handle ambiguous code review feedback, seek clarification before implementing any changes. The process requires validating the feedback against the codebase and addressing unclear comments with direct communication to ensure technical accuracy.

What is the best way to respond to code review comments?

The best way to respond to code review comments is by providing technical justifications rather than performative agreement. You must validate feedback against your codebase, prioritize revisions based on impact, and maintain technical integrity.

How do I prevent feature creep when requesting code reviews?

To prevent feature creep during code reviews, enforce the YAGNI principle to ensure code relevance. This approach limits unnecessary additions by focusing strictly on required technical accuracy and maintaining existing codebase integrity.

How do I validate external reviewer feedback on my codebase?

To validate external reviewer feedback, perform context checks and verify technical accuracy against your codebase. Respond using technical justifications and prioritize revisions based on the actual impact and clarity of the suggested changes.

What information do I need to share when initiating a code review?

When initiating a code review, you need to share structured information about your latest changes, typically against the main branch. A disciplined review process requires defining clear protocols for requesting and responding to feedback.