con un clic
con un clic
Execute the difit release workflow when the user says "リリース" or asks to cut a release. Update CHANGELOG Unreleased from commits since latest tag, ask for explicit OK confirmation in Japanese, then release by moving the confirmed Unreleased section verbatim as the exact source of truth.
Ask the user for a code review through difit after code changes in this repository, using `pnpm run dev`.
A skill for reviewing a specific diff and showing the findings as comments inside difit (the diff viewer). Use it to review branch diffs, commit diffs, or GitHub PRs, then preload findings or code explanations into difit with `--comment` before launching it for the user.
Ask the user for a code review through difit after code changes in this repository, using `pnpm run dev`.
A skill for reviewing a specific diff and showing the findings as comments inside difit (the diff viewer). Use it to review branch diffs, commit diffs, or GitHub PRs, then preload findings or code explanations into difit with `--comment` before launching it for the user.
A skill for reviewing a specific diff and showing the findings as comments inside difit (the diff viewer). Use it to review branch diffs, commit diffs, or GitHub PRs, then preload findings or code explanations into difit with `--comment` before launching it for the user.
| name | difit |
| description | Ask the user for a code review through difit after code changes. |
This skill requests a code review from the user using difit.
Before running commands, choose <difit-command> using the following rule:
command -v difit succeeds, use difit.npx difit.npx difit would require network access in a sandboxed environment without network permission, request escalated permissions and user approval before running it.If the user leaves review comments, they are printed to stdout when the chosen difit command exits. When review comments are returned, continue work and address them. If the server is shut down without comments, treat it as "no review comments were provided." Restarting it is unnecessary. Manual verification of whether the page launched correctly is also unnecessary.
<difit-command> .<difit-command><difit-command> staged<difit-command> workingBasic Usage:
<difit-command> <target> # View single commit diff. ex: difit 6f4a9b7
<difit-command> <target> [compare-with] # Compare two commits/branches. ex: difit feature main
If there is something you want to tell the user when difit opens, attach it as startup comments with --comment.
This is useful for review findings, explanations, and any context the user should see directly on the diff.
<difit-command> <target> [compare-with] \
--comment '{"type":"thread","filePath":"src/foobar.ts","position":{"side":"old","line":102},"body":"line 1\nline 2"}' \
--comment '{"type":"thread","filePath":"src/example.ts","position":{"side":"new","line":{"start":36,"end":39}},"body":"Range comment for L36-L39"}'
type: "thread" for each comment.position.side: "new" for lines that exist on the target side of the diff.position.side: "old" for lines that exist only on the deleted side.--comment bodies or any command-line arguments.For uncommitted changes, if files not yet added to git should also appear in the diff, add --include-untracked.
<difit-command> . --include-untracked
Can only be used inside a Git-managed directory.