code-review-reflect

Apply ACCEPTED code review feedback and validate via iterative build and test runs.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/Jsplix/ACODIAN-ORIGIN --skill code-review-reflect-jsplix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-reflect
Source: https://github.com/Jsplix/ACODIAN-ORIGIN/tree/main/.codex/skills/code-review-reflect
Command: npx skills add https://github.com/Jsplix/ACODIAN-ORIGIN --skill code-review-reflect-jsplix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually processing code review comments, deciding which changes to apply, modifying source code, and running quality assurance checks is time-consuming and error-prone, especially in development pipelines where code changes must be isolated to avoid conflicts with other concurrent work.

Core Features & Use Cases

  • Strict User Decision Adherence: Only modifies source code for review comments explicitly marked as ACCEPT by the user, skipping REJECTED or unmarked items to respect final approval authority.
  • Isolated Code Modification: Runs changes in a separate subagent context to prevent mixing with other concurrent work, returning only a summary of modifications to the leader session.
  • Iterative QA Validation: Automatically runs build and test commands repeatedly until all checks pass, reporting failures with minimal log excerpts instead of full logs.
  • Use Case: Development teams using automated code review pipelines can use this skill to automatically apply approved feedback, validate changes, and update review artifacts without manual intervention.

Quick Start

Use the code-review-reflect skill to apply all accepted feedback from your branch's review-comments.md file and run QA to validate the resulting code changes.

Frequently Asked Questions about code-review-reflect

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

FAQPage Schema
How do I automate applying accepted code review feedback to source code?

To automate applying accepted code review feedback, you can mark review comments with explicit ACCEPT decisions. The skill processes these pre-marked items, modifies the source code accordingly, and skips any rejected or unmarked feedback automatically.

How does isolated code modification prevent conflicts in development pipelines?

Isolated code modification prevents conflicts by running source code changes in a separate subagent context. This separation ensures that applying review feedback does not mix with other concurrent work, returning only a modification summary to the leader session.

Can I validate source code changes with iterative build and test commands after applying review fixes?

Yes, you can validate source code changes with iterative build and test commands. The skill automatically runs QA checks repeatedly until all tests pass, reporting any failures with minimal log excerpts instead of exposing full execution logs.

What happens to rejected or unmarked code review comments during feedback application?

Rejected or unmarked code review comments are skipped during feedback application to respect final user approval authority. The skill enforces strict adherence to user decisions by only modifying source code for items explicitly marked as ACCEPT.

How do I update review artifacts with QA execution results after applying code changes?

To update review artifacts with QA execution results, the skill automatically records the outcomes of the iterative build and test validations. It modifies the source code based on accepted feedback and then updates the artifacts with the final execution results.

Do I need to manually mark code review comments before automating source code modification?

Yes, you need to manually mark code review comments with explicit ACCEPT or REJECT decisions before automating source code modification. The skill requires these pre-marked decisions to ensure strict adherence to user-approved changes and prevent unwanted modifications.