claude-piv-skeleton: Command for Claude Code

.claude/commands/validation/code-review-fix.md

code-review-fix is a command for Claude Code from plipowczan/claude-piv-skeleton. It costs 6 tokens per session (1,526 once invoked), scanned A, original, MIT.

A command that reads a code-review report and implements the problems and recommendations it lists. A code review is a check of proposed code changes for defects, security risks, and maintainability issues.

In plain words
What is it for?
Use it after receiving a review report for a feature or change. It helps locate each reported issue, understand its priority, and apply the suggested correction.
Why use it?
It turns review feedback into concrete code changes and orders the work by seriousness. Critical problems such as security flaws or data-loss risks are handled before lower-priority style improvements.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths.

This is plipowczan/claude-piv-skeleton's own configuration. It tells Claude Code how to work on claude-piv-skeleton itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude-piv-skeleton configures →

Part of the piv-speckit plugin — 6 skills, 16 commands shipped together

Reuse

Borrowing it

Nothing to install: this file belongs to plipowczan/claude-piv-skeleton. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/plipowczan/claude-piv-skeleton/main/.claude/commands/validation/code-review-fix.md
Clone the repo
git clone --depth 1 https://github.com/plipowczan/claude-piv-skeleton

Made for: Claude Code.

Or install piv-speckit, the plugin that ships this one along with the rest of its 6 skills, 16 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for code-review-fix

README.md
[![agentmods](https://agentmods.dev/badge/commands/plipowczan/claude-piv-skeleton/code-review-fix.svg)](https://agentmods.dev/commands/plipowczan/claude-piv-skeleton/code-review-fix)
Your own site
<a href="https://agentmods.dev/commands/plipowczan/claude-piv-skeleton/code-review-fix"><img src="https://agentmods.dev/badge/commands/plipowczan/claude-piv-skeleton/code-review-fix.svg" alt="Measured on agentmods" height="20"></a>
Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,526 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00006 $0.01526
Opus 5 $0.00003 $0.00763
Sonnet 5 $0.00001 $0.00305
Haiku 4.5 $0.00001 $0.00153

Measured 7d ago against content hash a69500ccb636, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

code-review-fix scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/validation/code-review-fix.md · 271 lines

How it starts

The opening of the file, as written. The whole thing — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Code Review Fix: Implement Review Recommendations

Code Review Report

Read code review report: $ARGUMENTS

Example: .claude/agents/code-reviews/example-feature-validation-review.md

Process

1. Read and Understand Review

Read the code review report completely:

  • Identify all issues found
  • Understand severity levels (critical, high, medium, low)
  • Review suggested fixes
  • Note code examples provided

2. Prioritize Fixes

Fix in this order:

Priority 1: Critical Issues

  • Security vulnerabilities (SQL injection, XSS, exposed secrets)
  • Data loss risks
  • Race conditions
  • Must fix before commit

Priority 2: High Priority Issues

  • Performance problems (N+1 queries, memory leaks)
  • Logic errors
  • Code quality issues that affect functionality
  • Should fix before commit

Priority 3: Medium Priority Issues

  • Code quality improvements
  • Minor performance optimizations
  • Can fix in follow-up if needed

Priority 4: Low Priority Issues

  • Style issues (use linting tools)
  • Nice-to-have improvements
  • Can defer

3. Fix Each Issue

For each issue in the review report:

Step 1: Locate the code

  • Find the file and line number
  • Read surrounding context
  • Understand the issue

Step 2: Apply the fix

  • Follow the suggestion from the review
  • Use the code example provided
  • Follow Example patterns (see reference docs)

Step 3: Verify the fix

  • Run related tests
  • Check for new issues introduced
  • Ensure the fix doesn't break other functionality

Step 4: Document the fix

  • Add comment if logic is complex
  • Update related documentation if needed

4. Example Standards Compliance

When fixing issues, ensure compliance with:

Spring Data JDBC (NOT JPA/Hibernate):

// ✅ GOOD: Simple entity for JDBC
public class Entity {
    private Long id;
    private Long userId;
}

// ❌ BAD: JPA annotations
@Entity
public class Entity {
    @ManyToOne
    private User user;
}

Constructor Injection:

// ✅ GOOD: Constructor injection
@RequiredArgsConstructor
public class Service {
    private final Repository repository;
}

// ❌ BAD: Field injection
@Autowired
private Repository repository;

Read the full file on GitHub · 271 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 7d ago First seen · 271 lines · 6 tokens per session scan A a69500ccb636

Subscribe to this mod's changes

code-review-fix is a command published in the GitHub repository plipowczan/claude-piv-skeleton (4 stars, last pushed 7mo ago), licensed MIT. It adds 6 tokens to every session and 1,526 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.