Runs difit to launch a browser-based diff review UI and reports the result. Use when the user wants to review diffs with difit, visually review code changes in a browser, or says "difit でレビュー".
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Runs difit to launch a browser-based diff review UI and reports the result. Use when the user wants to review diffs with difit, visually review code changes in a browser, or says "difit でレビュー".
Save the returned task_id (used later to stop the server in Step 6).
Important:
Always use run-difit.sh wrapper (not npx difit directly). It provides a pseudo-tty to prevent difit from entering STDIN mode.
Do NOT pipe diff to stdin. Always pass arguments directly.
Always include the --clean flag.
Always include the --keep-alive flag. This keeps the difit server running even after the browser tab is closed, so comments can be retrieved via HTTP in Step 5 regardless of browser/process state. (Without it, closing the browser shuts the server down and comments become unretrievable.)
<output_file> is the first positional argument — the script redirects difit output there (no pipe). The file is used to detect server startup and the auto-assigned port.
Because --keep-alive is set, the background task will not complete on its own; it must be stopped via TaskStop in Step 6.
Step 4: Ask User for Review Completion
After launching difit in Step 3, immediately confirm completion with the user. You MUST use the AskUserQuestion tool for this — never ask via a plain text message and wait for a manual reply. Do NOT poll for completion first.
「完了」 → Proceed to Step 4.5. Approval status is determined by fetching comments via HTTP in Step 5, not from this selection. The user does not need to close the browser — --keep-alive keeps the server reachable.
「中止」 → Skip Steps 4.5 and 5. Go to Step 6 (stop the server), then report result APPROVED (no feedback) in Step 7.
Step 4.5: Verify difit Startup
After the user responds, Read the contents of <output_file> and verify difit started successfully:
Startup check: If <output_file> does NOT contain difit server started on → the launch failed. Retry once (go back to Step 3). If the retry also lacks this marker, report an error and stop.
Premature exit check: If <output_file> contains Warning: difit exited in → the session ended too quickly. Retry once (go back to Step 3). If the retry also exits prematurely, report an error and stop.
Step 5: Fetch Comments via HTTP
Retrieve the review comments directly from the running difit server:
fetch-comments.sh reads the auto-assigned port from <output_file> and queries /api/comments-output. This is reliable regardless of how the process is later terminated — the client syncs comments to the server on every change, and --keep-alive keeps the endpoint reachable.
Determine the result from the command output:
fetch-comments.sh output
Final result
Contains 📝 Comments
CHANGES_REQUESTED
Empty / no marker
APPROVED
When the result is CHANGES_REQUESTED, the entire output (the 📝 Comments from review session: block) is the feedback content.
Fallback: If fetch-comments.sh fails (e.g. the server is unreachable because difit crashed), Read<output_file> and check for a 📝 Comments block written there by difit's shutdown flush. Treat its presence as CHANGES_REQUESTED, absence as APPROVED.
Step 6: Stop the difit Server
Because --keep-alive keeps the server running indefinitely, stop the background task now that comments have been retrieved:
TaskStop(task_id=...)
Step 7: Report Result
When feedback exists:
Output:
There is user feedback.
<feedback content from fetch-comments.sh output>
Include the full 📝 Comments from review session: block as-is.
When no feedback:
Output only:
No user feedback. It is APPROVED.
Error Handling
If difit fails to start or is not installed, report the error.
If <output_file> does not contain difit server started on (empty, blank, or unexpected response), retry once (as described in Step 4.5). If the retry also fails, stop the task (TaskStop) and report:
Error: difit failed to start after retry. Please run difit manually.
If <output_file> contains Warning: difit exited in (premature exit without user review), retry once. If the retry also exits prematurely, stop the task (TaskStop) and report:
Error: difit exited too quickly for user review after retry. Please run difit manually.
Always TaskStop the background task before reporting a terminal error, since --keep-alive prevents it from exiting on its own.
