Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

review-fix

Étoiles3

Forks1

Mis à jour2 juin 2026 à 04:50

Process `REVIEW:` inline comments left in code after implementation review. Fix each comment locally and remove it. Use after execute-plan when a human has added `REVIEW:` annotations to the codebase.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

iimuz

iimuz/dotfiles

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	review-fix
description	Process `REVIEW:` inline comments left in code after implementation review. Fix each comment locally and remove it. Use after execute-plan when a human has added `REVIEW:` annotations to the codebase.
user-invocable	true
disable-model-invocation	false

Review Fix

Overview

Process REVIEW: comments that a human has added to source code after a code review. Apply each local fix, then delete the resolved comment. Do not touch the planning file and do not handle design-level changes here.

Process

Identify the planning file from the user's prompt (default: docs/planning.md).
Read the planning file in full if it exists.
Search the entire codebase for REVIEW: comments.
For each REVIEW: comment, decide:
- Can this be resolved with a local code change that does not conflict with the plan? → Fix it and delete the comment.
- Does it require a design change, schema change, API change, or plan update? → Do not implement it; report it and recommend running write-plan instead.
After fixing a comment, verify the comment has been removed from the file.
Run lint and tests when available.
Confirm no REVIEW: comments remain. Report any that were intentionally deferred.

What review-fix does NOT handle

Database schema changes
API design changes
Data model ownership changes
Specification changes
Scope changes
Architectural changes
Anything requiring plan.md to be updated
Todo list restructuring
Re-opening completed tasks

When a REVIEW: comment falls into one of these categories, do not implement it. Report it clearly and instruct the user to run write-plan first.

Constraints

Never delete a REVIEW: comment without implementing the fix it requests.
Do not add REVIEW: comments or leave them in production code.
Do not add unnecessary comments or JSDoc.
Do not use any or unknown without a specific, justified reason.
If a REVIEW: comment conflicts with plan.md, follow plan.md and report the conflict.
Run typecheck before finishing. Run lint and tests when available.
Do not modify the planning file.

Plus depuis ce dépôt

même dépôt

gh-ops

iimuz/dotfiles

Use for GitHub operations: creating issues, posting issue comments, creating draft PRs, and adding PR review comments.

2026-07-163

scamper

iimuz/dotfiles

Facilitate structured divergent idea generation using the SCAMPER technique (Bob Eberle). An orchestrator elicits a concrete target, applies seven transformation lenses (Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, Reverse) in parallel via focused subagents, then converges into evaluated, prioritized ideas. Use when the user asks for a SCAMPER analysis, systematic ideation, or improvement ideas for an existing product, service, process, or idea.

2026-07-043

six-hats

iimuz/dotfiles

Facilitate structured multi-perspective analysis using Edward de Bono's Six Thinking Hats. A Blue Hat orchestrator applies one hat at a time in sequence over a single shared record, using five focused hat subagents. Use when the user asks for a Six Hats or 6 hat analysis, a multi-perspective breakdown of a decision, idea, or problem, or systematic structured thinking on a topic.

2026-07-043

markmap

iimuz/dotfiles

Author markmap-format Markdown. Use when writing a mindmap (マインドマップ / markmap) in Markdown.

2026-07-043

sample-greeting

iimuz/dotfiles

Sample skill for verifying plugin wiring. Trigger when the user asks to run the sample greeting or test the sample plugin.

2026-07-033

gh-pr-resolve

iimuz/dotfiles

Use when resolving or addressing PR review comments.

2026-07-023

Review Fix

Overview

Process

Identify the planning file from the user's prompt (default: docs/planning.md).

Read the planning file in full if it exists.

Search the entire codebase for REVIEW: comments.

For each REVIEW: comment, decide:

Can this be resolved with a local code change that does not conflict with the plan? → Fix it and delete the comment.
Does it require a design change, schema change, API change, or plan update? → Do not implement it; report it and recommend running write-plan instead.

After fixing a comment, verify the comment has been removed from the file.

Run lint and tests when available.

Confirm no REVIEW: comments remain. Report any that were intentionally deferred.

What review-fix does NOT handle

Database schema changes

API design changes

Data model ownership changes

Specification changes

Scope changes

Architectural changes

Anything requiring plan.md to be updated

Todo list restructuring

Re-opening completed tasks

When a REVIEW: comment falls into one of these categories, do not implement it. Report it clearly and instruct the user to run write-plan first.

Constraints

Never delete a REVIEW: comment without implementing the fix it requests.

Do not add REVIEW: comments or leave them in production code.

Do not add unnecessary comments or JSDoc.

Do not use any or unknown without a specific, justified reason.

If a REVIEW: comment conflicts with plan.md, follow plan.md and report the conflict.

Run typecheck before finishing. Run lint and tests when available.

Do not modify the planning file.