What is the 'Technical Honesty' principle in this skill?

Technical honesty means prioritizing the technical correctness of the code and the requirements of the project over social comfort or 'polite' agreement with a reviewer.

How does the YAGNI check function during a review?

When a 'proper' implementation is suggested, the skill prompts a grep search of the codebase to see if the feature is actually used before adding complexity.

When should I use the Chronista Code Review skill?

Use it whenever you are preparing to submit a PR, after complex bug fixes, or when receiving feedback that requires technical validation before implementation.

Why does the skill discourage saying 'thank you' or 'great point'?

It eliminates performative agreement to ensure developers focus on verifying and implementing technical changes rather than engaging in emotional performance.

Can I use this skill to argue against a reviewer's feedback?

Yes, the skill provides a framework for rebuttals based on technical grounds, such as existing architectural decisions, context gaps, or regression risks.

Chronista Code Review

Name: Chronista Code Review
Author: chronista-club

bychronista-club

0•

Collaboration Tools

Enforces a disciplined, technical-first approach to code reviews by prioritizing technical honesty and rigorous validation over social performance.

The Chronista Code Review skill transforms how developers interact during the review process by establishing a high-discipline framework. It provides structured workflows for both requesting and receiving feedback, emphasizing technical accuracy over 'performative agreement.' By prohibiting empty social niceties and mandating pre-implementation validation, this skill ensures that every code change is technically justified, follows YAGNI principles, and aligns with the existing architecture. It is particularly useful for teams seeking to reduce technical debt and maintain a high bar for code quality through honest, evidence-based communication.

Key Features

01Technical response patterns that prohibit performative agreement

02Standardized review request workflow with git SHA identification

03Mandatory YAGNI (You Aren't Gonna Need It) verification logic

04Evidence-based rebuttal frameworks for technical disagreements

050 GitHub stars

06Structured feedback processing for multi-item reviews

Use Cases

01Processing multi-point feedback systematically to prevent partial implementation errors

02Requesting high-stakes reviews for major feature merges or complex bug fixes

03Validating external feedback against existing architectural constraints and usage

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add chronista-club/claude-plugin-chronista-style code-review

For use in Claude.ai and ChatGPT

Download Skill