do-execute-review-fix

Execute a single review-fix task file and update its status.

28|1|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/fabio-barboza/development-orchestrator --skill do-execute-review-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: do-execute-review-fix
Source: https://github.com/fabio-barboza/development-orchestrator/tree/main/skills/do-execute-review-fix
Command: npx skills add https://github.com/fabio-barboza/development-orchestrator --skill do-execute-review-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill executes a single review-fix task file by applying the fix, running the tests, and updating the status. It is intended when do-execute-review produced a fix task and the user wants to resolve a specific issue. Do not use for bulk corrections — invoke once per file. Do not use for QA, QA bugfixes, or implementing new features.

Core Features & Use Cases

  • Executes the fix for a single review finding.
  • Runs the project's test suite and updates the fix task status.
  • Maintains traceability by recording changes and statuses for each finding.

Quick Start

Passe o caminho do arquivo de fix específico, por exemplo: do-execute-review-fix ./prds/prd-your-feature/review-fixes/fix-R01-critico-senha.md

Frequently Asked Questions about do-execute-review-fix

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

FAQPage Schema
How do I execute a single review-fix task file to resolve a code finding?

To execute a review-fix task, pass the specific fix file path to the command. The tool applies the fix, runs the project's test suite to validate the change, and updates the fix task status for traceability.

Can I use this tool for bulk QA bugfixes across multiple files?

No, this tool is not intended for bulk QA corrections or implementing new features. You must invoke it once per individual fix file to ensure deterministic execution and targeted resolution of a single review finding.

What test configuration do I need to run review-fixes autonomously?

Executing an autonomous review-fix requires the project's existing test configuration. The tool relies on these tests to validate the applied code changes and assumes deterministic execution of the fix task file.

How does the review-fix process maintain traceability for code findings?

The review-fix process maintains traceability by automatically recording applied changes and updating the status for each finding. This ensures every resolved issue from the review is tracked through its specific fix task file.

When should I use a review-fix task instead of general code quality automation?

Use a review-fix task when a prior code review produces a specific finding that requires a targeted correction. Do not use it for general QA bugfixes, bulk corrections, or implementing new software features.

What is the best way to resolve a critical finding from a code review?

The best way to resolve a critical review finding is to invoke the review-fix command with the exact path to the generated fix file, allowing the tool to apply the correction and run tests autonomously.