Change Verification Gate
fengshao1227/ccg-workflow
Analyzes a code diff for documentation sync, test coverage and impact scope, warning when docs or tests lag behind a design-level change or a large edit.
Run /code-review on the current diff and post the findings as inline comments in VibeDiff, tagged as agent:reviewer.
Install Vibediff Review
$ npx skills add meain/dotfiles --skill vibediff-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install meain/dotfiles vibediff-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/meain/dotfiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/agents/.agents/skills/vibediff-review .claude/skills/vibediff-review && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "vibediff-review" agent skill from https://github.com/meain/dotfiles/tree/master/agents/.agents/skills/vibediff-review into .claude/skills/vibediff-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibediff-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/meain/dotfiles/tree/master/agents/.agents/skills/vibediff-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add meain/dotfiles --skill vibediff-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install meain/dotfiles vibediff-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/meain/dotfiles.git skills-src && mkdir -p .agents/skills && cp -r skills-src/agents/.agents/skills/vibediff-review .agents/skills/vibediff-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vibediff-review" agent skill from https://github.com/meain/dotfiles/tree/master/agents/.agents/skills/vibediff-review into .agents/skills/vibediff-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibediff-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add meain/dotfiles --skill vibediff-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install meain/dotfiles vibediff-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/meain/dotfiles.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/agents/.agents/skills/vibediff-review .cursor/skills/vibediff-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "vibediff-review" agent skill from https://github.com/meain/dotfiles/tree/master/agents/.agents/skills/vibediff-review into .cursor/skills/vibediff-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibediff-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/meain/dotfiles.git --path agents/.agents/skills/vibediff-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add meain/dotfiles --skill vibediff-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install meain/dotfiles vibediff-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/meain/dotfiles.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/agents/.agents/skills/vibediff-review .gemini/skills/vibediff-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "vibediff-review" agent skill from https://github.com/meain/dotfiles/tree/master/agents/.agents/skills/vibediff-review into .gemini/skills/vibediff-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibediff-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install meain/dotfiles vibediff-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add meain/dotfiles --skill vibediff-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/meain/dotfiles.git skills-src && mkdir -p .github/skills && cp -r skills-src/agents/.agents/skills/vibediff-review .github/skills/vibediff-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "vibediff-review" agent skill from https://github.com/meain/dotfiles/tree/master/agents/.agents/skills/vibediff-review into .github/skills/vibediff-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibediff-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add meain/dotfiles --skill vibediff-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install meain/dotfiles vibediff-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/meain/dotfiles.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/agents/.agents/skills/vibediff-review .opencode/skills/vibediff-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "vibediff-review" agent skill from https://github.com/meain/dotfiles/tree/master/agents/.agents/skills/vibediff-review into .opencode/skills/vibediff-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibediff-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
vibediff-review- GitHub stars
- 285
- Token cost
- ~888 tokens
- SKILL.md length
- 376 words
- Files
- 1
- Skills in repo
- 35
- Repo updated
- First seen
- Licence
- MIT
At a glance
Run /code-review on the current diff and post the findings as inline comments in VibeDiff, tagged as agent:reviewer.
- Works in 5 steps: Run the code review → Verify VibeDiff instance and find the… → Resolve the revision → …
- The user says /vibediff-review
- SKILL.md covers When to use, Workflow and Notes
- Calls curl
What it does
Vibediff Review is an agent skill from meain/dotfiles. Run /code-review on the current diff and post the findings as inline comments in VibeDiff, tagged as agent:reviewer. Use when the user says /vibediff-review, "review and post to vibediff", "code review this into vibediff", or asks for a code review to show up as VibeDiff comments instead of a chat summary.
Its SKILL.md is about 890 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Code review and Technical documentation. The repository describes itself as: If there is a shell, there is a way! The licence is MIT.
When your agent uses it
- The user says /vibediff-review
- Review and post to vibediff
- Code review this into vibediff
- Asks for a code review to show up as VibeDiff comments instead of a chat summary
Example prompts
- “review and post to vibediff”
- “code review this into vibediff”
- “/vibediff-review”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 3e336e2. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
curl
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use curl, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Vibediff Review loads about 888 tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 376 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from meain/dotfiles at commit 3e336e2, republished under its MIT licence (© meain). 376 words, ~888 tokens.
Download SKILL.mdSave it as
.claude/skills/vibediff-review/SKILL.md (or your agent's skills folder).- name
- vibediff-review
- description
- Run /code-review on the current diff and post the findings as inline comments in VibeDiff, tagged as agent:reviewer. Use when the user says /vibediff-review, "review and post to vibediff", "code review this into vibediff", or asks for a code review to show up as VibeDiff comments instead of a chat summary.
VibeDiff Review Workflow
Run the code-review skill against the current diff, then post each surviving finding as an inline VibeDiff comment authored as agent:reviewer.
When to use
- User says "/vibediff-review", "review and post to vibediff", "code review this into vibediff"
- User wants review findings to land as VibeDiff threads instead of (or in addition to) a chat summary
Workflow
1. Run the code review
Invoke the code-review skill on the current diff (pass through any effort level or args the user gave, e.g. /vibediff-review high). Do not pass --comment (that posts to GitHub PRs) or --fix — this skill owns posting the output, to VibeDiff.
This produces a set of verified findings (file, line, summary, failure_scenario, category, verdict).
If there are no findings, tell the user and stop — don't post anything to VibeDiff.
2. Verify VibeDiff instance and find the project
DIR="/path/to/repo"
curl -s http://localhost:8888/api/directories | grep -q "$DIR" || \
curl -s -X POST http://localhost:8888/api/directories \
-H 'Content-Type: application/json' \
-d "{\"directory\":\"$DIR\"}"
curl -s "http://localhost:8888/api/directory?directory=$DIR"3. Resolve the revision
Leave revision empty to attach comments to the working-copy diff (the common case right after a review). If the user asked to review a specific commit, resolve it to a jj change ID first — VibeDiff uses jj change IDs, not git hashes:
REV=$(jj log --no-graph -r '<revision>' --template 'change_id' -R $DIR)4. Post each finding as a comment
For every finding, post one comment at its file/line. Combine summary and failure_scenario into the content so the reader gets both the defect and a concrete failure case. Always set "author": "agent" and "authorName": "reviewer" — the UI renders this as agent:reviewer, distinguishing it from other agent comment types (e.g. agent:explain).
curl -s -X POST http://localhost:8888/api/review/comment \
-H 'Content-Type: application/json' \
-d "{
\"directory\": \"$DIR\",
\"revision\": \"$REV\",
\"file\": \"services/example-svc/internal/store/example.go\",
\"line\": 88,
\"author\": \"agent\",
\"authorName\": \"reviewer\",
\"content\": \"<summary>\\n\\n<failure_scenario>\"
}"If revision is empty (working-copy review), omit it from the payload rather than sending an empty string.
Show full SKILL.md (116 more words)Show less
5. Report back
Tell the user how many findings were posted and to which file/line pairs. Don't repeat the full finding text in chat — that's what the VibeDiff comments are for — a one-line-per-finding recap is enough.
Notes
directoryis required for root comments;authormust be"user"or"agent"— always"agent"here.authorNameis capped at 50 chars —"reviewer"fits and is the fixed tag for this skill; don't vary it per invocation.- Reuse the same
revisionvalue across all comments from one review run so they group into a single pass in the VibeDiff UI. - If
code-reviewreports zero findings, do not create a placeholder "no issues found" comment — just tell the user in chat.
© meain, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in agents/.agents/skills/vibediff-review of meain/dotfiles.
Open the folder on GitHubat commit 3e336e2
Compare with similar skills
Vibediff Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Vibediff Review this skillmeain/dotfiles | 285 | — | ~888 | Automated safety check: Pass | MIT | |
| Change Verification Gatefengshao1227/ccg-workflow | 5.9k | — | ~511 | Automated safety check: Notes | MIT | |
| Post Draft Reviewagent-substrate/substrate | 4.8k | — | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Docs GuardamElnagdy/guard-skills | 1.3k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Codex Proxy RS Development Guidezyycn/codex-proxy-rs | 788 | — | ~618 | Automated safety check: Pass | Apache-2.0 | |
| Inline PR Commentshyperlane-xyz/hyperlane-explorer | 102 | — | ~1.1k | Automated safety check: Pass | Custom licence |
Similar skills
Post Draft Review
agent-substrate/substrate
Posts pull request review findings as GitHub draft (pending) inline comments for a human to edit and submit, instead of publishing them straight to the PR author.
Docs Guard
amElnagdy/guard-skills
Checks generated or edited documentation against the source code, flagging invented symbols, outdated samples and unverifiable claims before publishing.
Codex Proxy RS Development Guide
zyycn/codex-proxy-rs
Routes development, troubleshooting, review and documentation tasks on the Codex Proxy RS repository to the right section of its docs, instead of loading the whole architecture or contributing guide.
Inline PR Comments
hyperlane-xyz/hyperlane-explorer
Post a single consolidated PR review with summary and inline comments.
PR Inline Comments
sesori-ai/sesori_apps_monorepo
Fetch inline (code) review comments on a GitHub pull request, grouped into threads, with optional filtering by datetime.
More from meain/dotfiles
All 35 skills in this repoRecall
meain/dotfiles
Search past Claude Code and Codex sessions. An agent skill from meain/dotfiles.
Grill With Docs
meain/dotfiles
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise.
Backlog
meain/dotfiles
Daily backlog management — full planning review OR add a single entry from a URL.
Concern Review
meain/dotfiles
Generate an interactive local HTML review page for a large PR or diff, grouping the changed files by logical concern (not just by file) so a reviewer can go through one theme at a time instead of a…
My Weekly Report
meain/dotfiles
Generate a concise weekly status update in team format. An agent skill from meain/dotfiles.
Web Search
meain/dotfiles
Search the web using lynx and DuckDuckGo. An agent skill from meain/dotfiles.
Related
Categories
Questions about Vibediff Review
What does Vibediff Review do?
Run /code-review on the current diff and post the findings as inline comments in VibeDiff, tagged as agent:reviewer. Vibediff Review is an agent skill from meain/dotfiles. Run /code-review on the current diff and post the findings as inline comments in VibeDiff, tagged as agent:reviewer.
When should I use Vibediff Review?
Vibediff Review fits situations like: the user says /vibediff-review; review and post to vibediff; code review this into vibediff; asks for a code review to show up as VibeDiff comments instead of a chat summary.
How do I install Vibediff Review in Claude Code?
Run `npx skills add meain/dotfiles --skill vibediff-review -a claude-code`. Or copy the skill folder (agents/.agents/skills/vibediff-review in meain/dotfiles) into .claude/skills/vibediff-review in your project. Claude Code loads it when a task matches its description.
How do I install Vibediff Review in Codex?
Run `npx skills add meain/dotfiles --skill vibediff-review -a codex`. Or copy the skill folder (agents/.agents/skills/vibediff-review in meain/dotfiles) into .agents/skills/vibediff-review in your project. Codex loads it when a task matches its description.
Can I use Vibediff Review in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add meain/dotfiles --skill vibediff-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vibediff-review, .gemini/skills/vibediff-review, .github/skills/vibediff-review and .opencode/skills/vibediff-review in your project.
What does Vibediff Review need to run?
Going by SKILL.md and its folder, Vibediff Review needs the command-line tools its instructions call (curl).
Does Vibediff Review access the network?
SKILL.md contains no URLs. Its commands use curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Vibediff Review safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Vibediff Review use?
Vibediff Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Vibediff Review use?
About 888 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Vibediff Review?
Skills that share tags, products or a category with Vibediff Review: Change Verification Gate (fengshao1227/ccg-workflow, 5.9k stars), Post Draft Review (agent-substrate/substrate, 4.8k stars), Docs Guard (amElnagdy/guard-skills, 1.3k stars) and Codex Proxy RS Development Guide (zyycn/codex-proxy-rs, 788 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vibediff Review?
meain (a GitHub user) maintains it in meain/dotfiles, which has 285 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 8, 2026.
Source: meain/dotfiles on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.