review-fixer

Apply verified fixes within OWNED_FILES and run regression tests.

11|1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/ylxmf2005/AgentCorp --skill review-fixer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-fixer
Source: https://github.com/ylxmf2005/AgentCorp/tree/main/agentcorp/review-fixer
Command: npx skills add https://github.com/ylxmf2005/AgentCorp --skill review-fixer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill ensures that groups of verified fixes are landed safely inside a controlled set of files (OWNED_FILES), with regression checks and per-item fix records to prevent drift.

Core Features & Use Cases

  • Lands a single group of verified fixes inside a defined owned-files boundary.
  • Performs drift checks and per-item regression validation to safeguard code integrity.
  • Maintains focused changes within OWNED_FILES and records fix histories for traceability.
  • Useful in scenarios where review-research outcomes must be faithfully applied and audited before merging.

Quick Start

Review the assigned FIX_ITEMS and apply them to the code within OWNED_FILES, then run the regression tests.

Frequently Asked Questions about review-fixer

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

FAQPage Schema
How do I apply verified code-review fixes while preventing changes outside owned files?

You land verified fixes by processing assigned fix items strictly within a defined OWNED_FILES boundary. This controlled scope ensures changes apply faithfully, prevents drift, and maintains landing discipline across the codebase.

What is the best way to validate per-item regression testing during fix landing?

Per-item regression validation checks each assigned fix item within a controlled scope during the landing process. This drift check safeguards code integrity and ensures every change passes regression tests before merging into owned files.

Can I use this approach to manage fix landing for group work across specific assigned items?

Yes, this approach handles fix landing for group work by processing a single group of assigned FIX_ITEMS at a time. It requires the group's FIX_ITEMS and OWNED_FILES from the research handoff to maintain focused changes and traceability.

Do I need research handoff data to start applying fixes to owned files?

Yes, you need the group's FIX_ITEMS and OWNED_FILES from the research handoff. These inputs define the assigned changes and the file boundary required to enforce landing discipline and maintain a controlled regression scope.

Why does my fix landing process require drift checks inside owned files?

Drift checks are required to prevent unintended changes from entering the codebase during fix landing. They safeguard code integrity by ensuring applied fixes remain faithful to the verified items within the controlled OWNED_FILES boundary.