Dev10x-git-fixup

Create scoped fixup commits linked to PR review comments or standalone improvements.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Brave-Labs/dev10x --skill dev10x-git-fixup-brave-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Dev10x-git-fixup
Source: https://github.com/Brave-Labs/dev10x/tree/main/codex-skills/dev10x-git-fixup
Command: npx skills add https://github.com/Brave-Labs/dev10x --skill dev10x-git-fixup-brave-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill creates properly scoped fixup commits that address specific review comments or are standalone improvements, ensuring one fixup per comment and clear traceability.

Core Features & Use Cases

  • Review fixups: generate a fixup per review comment linked to a PR discussion.
  • Standalone fixups: allow self-initiated improvements with a standalone marker.
  • Integrates with Dev10x:gh-pr-fixup: coordinates with the higher-level workflow and pre-commit validations to enforce one-fixup-per-comment.

Quick Start

Stage your changes and run the fixup command to attach a specific review comment or create a standalone fixup.

Frequently Asked Questions about Dev10x-git-fixup

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

FAQPage Schema
How do I create fixup commits for PR review comments in a Git workflow?

Fixup commits for PR review comments are created by staging changes and running a fixup command that links the commit to a specific review thread. This enforces one fixup per comment, ensuring clear traceability and properly scoped improvements.

Can I create a standalone fixup commit that is not tied to a PR review thread?

Standalone fixup commits can be created for self-initiated improvements by using a standalone marker. This indicates the fixup is independent of any specific PR discussion thread while still maintaining clear commit messaging within the workflow.

Does this fixup workflow enforce one commit per PR comment?

This fixup workflow enforces one fixup per PR review comment through integrated pre-commit validations and guardrails. These mechanisms ensure that commits remain properly scoped and clearly traceable to their corresponding discussion threads.

What is the best way to organize Git fixup commits before a pre-commit validation?

Organizing Git fixup commits before pre-commit validation involves linking each commit to a specific review thread or applying a standalone marker. This approach meets workflow requirements by ensuring clear messaging and preventing improperly scoped fixes.

When should I not use a standalone marker for a fixup commit?

A standalone marker should not be used when your changes directly address a specific PR review comment. In that case, you must link the fixup commit to the corresponding discussion thread to maintain proper traceability and workflow compliance.

Why do my Git fixup commits fail pre-commit checks during PR reviews?

Git fixup commits fail pre-commit checks when they violate the one-fixup-per-comment guardrail or lack clear traceability. The workflow validates that each commit is properly scoped to a specific review thread or marked as a standalone fix.