Dev10x:review-fix

Convert review findings JSON into per-finding fixup commits with lint validation.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Brave-Labs/dev10x --skill dev10x-review-fix
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Dev10x:review-fix
Source: https://github.com/Brave-Labs/dev10x/tree/main/skills/review-fix
Command: npx skills add https://github.com/Brave-Labs/dev10x --skill dev10x-review-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consume structured findings from Dev10x:review and create one standalone fixup! commit per finding via Dev10x:git-fixup. This enables a fast, auditable fix cycle in code reviews.

Core Features & Use Cases

  • Load the findings JSON produced by Dev10x:review and filter by severity (ERROR/WARNING) for actionable items.
  • Apply automated or guided fixes per finding, then validate via lint/format checks (ruff, black).
  • Stage changes and create per-finding fixup commits referencing the original subject to preserve history.

Quick Start

Provide the findings JSON file path to generate per-finding fixup commits automatically.

Frequently Asked Questions about Dev10x:review-fix

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

FAQPage Schema
How do I automate git fixup commits from code review findings?▼

You automate git fixup commits by loading a structured findings JSON file, applying fixes, validating with ruff and black, and staging deterministic per-finding commits referencing the original review subject.

What is the best way to turn ruff and black lint warnings into individual git commits?▼

The best way to turn lint warnings into individual commits is to process structured review findings, apply fixes per error or warning, run ruff and black validation checks, and create standalone fixup commits in a deterministic order.

How do I create one fixup commit per lint error automatically?▼

You create one fixup commit per lint error by iterating over a structured findings JSON file, filtering by severity, applying fixes, validating with ruff and black, and committing each change individually with the original subject.

Does this automated fixup commit workflow work without a findings JSON file?▼

No, this automated fixup commit workflow enforces required inputs and guards against missing findings files, missing paths, and lint or format failures by requiring a structured findings JSON to process.

Why do my automated fixup commits fail during the lint and format validation step?▼

Automated fixup commits fail during validation when ruff and black checks detect remaining formatting or linting issues after applying fixes, triggering built-in guards that block committing unvalidated changes.

Can I filter code review findings by severity before generating fixup commits?▼

Yes, you can filter code review findings by severity, specifically targeting ERROR and WARNING levels, to ensure only actionable items are processed into standalone fixup commits.