candid-review

Review git diffs against Technical.md standards and generate actionable fixes.

20|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/ron-myers/candid --skill candid-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: candid-review
Source: https://github.com/ron-myers/candid/tree/main/skills/candid-review
Command: npx skills add https://github.com/ron-myers/candid --skill candid-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams perform rigorous, context-aware code reviews by applying project-wide standards (Technical.md) and delivering actionable fixes, with streamlined tracking via todos and optional auto-commit of changes.

Core Features & Use Cases

  • Load and enforce project-specific standards from Technical.md to surface violations with clear context.
  • Detect changes in git diffs (staged or unstaged) and categorize issues by severity for targeted fixes.
  • Generate actionable fixes and convert them into todos, with optional automatic commits after applying fixes.
  • Provide an optional interactive prompt to choose tone (Harsh or Constructive) and review scope.

Quick Start

Run the candid-review skill to start reviewing your current changes. To adjust tone, use --harsh or --constructive. To auto-commit applied fixes, include --auto-commit.

Frequently Asked Questions about candid-review

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

FAQPage Schema
How do I automate code reviews to enforce project-specific standards in Git?

Automated code reviews enforce project rules by loading a Technical.md file, detecting Git diffs, and categorizing violations. The process surfaces issues with clear context and generates actionable fixes based on your configured rules.

Can I automatically commit code review fixes applied to my staged or unstaged diffs?

Yes, you can automatically commit applied fixes by including the --auto-commit flag. This streamlines the workflow by committing changes directly after the review process generates and applies the actionable fixes to your diffs.

How do I configure the tone of automated code review feedback?

Configure code review feedback tone by using the --harsh or --constructive flags. This adjusts the presentation of categorized issues and actionable fixes to match your team's preferred communication style.

What is the best way to track code review violations found in Git diffs?

Track code review violations by converting generated fixes into todos. This provides streamlined tracking of actionable items directly within your workflow after evaluating staged or unstaged file changes.

Do I need a Technical.md file to perform context-aware code reviews?

A Technical.md file is required to enforce project-wide standards and surface violations with clear context. Without it, the review process lacks the specific rules needed to categorize and generate actionable fixes.