Table of Contents

Apply Review Fixes

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

name, description, allowed-tools, disable-model-invocation

name	description	allowed-tools	disable-model-invocation
apply-review	Read review-result.md and automatically apply the suggested fixes to the codebase. Use after code-review when asked to apply fixes, implement review suggestions, or auto-fix review findings.	Read, Write, Edit, MultiEdit, Bash(git diff:), Bash(git status:), Bash(git branch:*)	false

Apply Review Fixes

Your task

Read the file review-result.md from the project root using the Read tool.
- If the file does not exist, stop and tell the user to run /code-review first.
Read the current git status and branch using git tools to understand the repository state.
Parse all issues from review-result.md and apply actionable fixes.

Priority order

Apply issues in this order:

⛔ Blocking — always apply
⛔ Security — always apply
⚠️ Non Blocking with a 🤖 Suggested Code block — apply if unambiguous
ℹ️ Information with a 🤖 Suggested Code block — apply only if safe and clear

Skip issues with labels: Praise, Thought, Note — these are observations, not action items.

For each actionable issue

Use the Read tool to open the referenced file at the specified path
Understand the problem from the comment description
Apply the fix using the Edit tool:
- If 🤖 Suggested Code is present → use it as the basis for the fix
- If no code is suggested → reason about the correct fix from the description
Verify the change makes sense in the surrounding code context
If a fix seems risky, breaks existing logic, or is ambiguous → skip it and log it

Rules

Only modify files referenced in the review
Match the surrounding code style, indentation, and naming conventions
Apply fixes one at a time, sequentially
If a referenced file path does not exist → skip and log under "Manual Action Required"
Do not run tests or builds — only apply code changes

After applying all fixes

Append the following section to review-result.md using the Edit tool (do not overwrite the existing content):

---

## Applied Fixes Log

**Applied at:** [current date and time]

### Applied
- `[file:line]` — [brief description of what was fixed]

### Skipped
- `[file:line]` — [reason: risky / unclear / informational only / no suggested code]

### Manual Action Required
- `[file:line]` — [description of issue that needs a human decision or cannot be auto-applied]

Finally, show a brief summary in the chat of what was applied and what needs manual attention.

Apply Review Fixes

Your task

Priority order

For each actionable issue

Rules

After applying all fixes

🤖 Kodo AI Reviewer

📚 Gitea

👩‍💻 Developer

🧑‍🔧 Tech Lead

📚 Bitbucket

👩‍💻 Developer

🧑‍🔧 Tech Lead

📚 Local Kodo