polish-head

Review the latest Git commit for DRY violations and testability gaps.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/nickstrad/veil-ai --skill polish-head
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: polish-head
Source: https://github.com/nickstrad/veil-ai/tree/main/.claude/skills/polish-head
Command: npx skills add https://github.com/nickstrad/veil-ai --skill polish-head

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of accumulating technical debt in recent commits by catching overlooked code quality issues like duplicated logic, untestable business logic, and inconsistent coding patterns before they are merged into the codebase.

Core Features & Use Cases

  • Latest Commit Scoped Review: Limits analysis exclusively to files changed in the most recent commit to deliver focused, actionable feedback without noise from unrelated code.
  • Multi-Category Quality Checks: Evaluates changes for DRY violations, testability gaps, low-value test coverage, unnecessary complexity, and alignment with project-specific conventions including repository pattern, Zod validation, and co-located tests.
  • Use Case: After pushing a commit that adds a new user authentication feature, use this Skill to identify duplicated validation logic, extract business rules from UI components into testable services, and ensure new code matches existing type and export patterns.

Quick Start

Invoke the polish-head skill to review the code changes in your latest commit for quality and consistency issues.

Frequently Asked Questions about polish-head

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

FAQPage Schema
How do I review my latest git commit for code quality and pattern consistency?

To review your latest git commit for code quality, you can scope the analysis exclusively to files modified in the most recent commit to identify DRY violations, testability gaps, and pattern inconsistencies without noise from unrelated code.

How do I check for DRY violations and testability gaps before merging new code?

Checking for DRY violations and testability gaps involves evaluating recent changes for duplicated logic, untestable business logic, and low-value tests, ensuring new code matches project-specific conventions like repository patterns and Zod boundary validation.

Can I automatically fix code review issues found in my latest commit?

You cannot automatically fix code review issues without intervention; the tool delivers prioritized, actionable feedback for each identified issue and requires explicit user confirmation before applying any code changes to preserve developer control.

Does automated commit review work with project-specific conventions like Zod validation and co-located tests?

Automated commit review does work with project-specific conventions by applying your established patterns including repository pattern with optional database dependency injection, Zod boundary validation, and co-located __tests__ directories during the analysis.

What is the best way to catch technical debt in recent commits before merging?

The best way to catch technical debt in recent commits is performing a focused code review of the latest changes to identify unnecessary complexity and low-value tests before they are merged into the codebase.

Why does commit review only analyze files modified in the most recent commit?

Commit review analyzes only files modified in the most recent commit to deliver focused, actionable feedback without noise from unrelated code, eliminating the risk of accumulating technical debt by catching overlooked issues early.