skill CX Codex

vibe-review — Claude Code skill: what it does, how to install

Q: How do I install vibe-review in Claude Code?

Run `npx skills add KhazP/vibe-coding-prompt-template --skill vibe-review -a claude-code`, then check `~/.claude/skills/vibe-review/SKILL.md`.

Q: Which tools does vibe-review use?

The skill is allowed to use `Read`, `Glob`, `Grep`, and `Bash`. If the agent cannot inspect files or run `Bash`, some review conclusions cannot be verified.

vibe-review checks proposed changes against requirements, regressions, verification evidence, and security concerns before they move forward.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓

npx skills add KhazP/vibe-coding-prompt-template --skill vibe-review -a claude-code

Open on GitHub

What vibe-review does

vibe-review examines the real diff together with applicable project instructions, acceptance criteria, and check results. It follows changed behavior into its callers and tests, then looks for concrete regressions, weak error handling, and assumptions that do not hold. Authorization and data-exposure risks are considered when the change makes them relevant.

Findings include a file and line, the trigger, the impact, and a suggested correction. The skill separates observed defects from missing proof and does not claim checks it did not run. Its permitted tools are Read, Glob, Grep, and Bash, so a runtime that cannot read the project or execute Bash will leave parts of the review unverified.

The review does not authorize unrelated edits or publication. When it finds no issues, it still reports remaining verification gaps.

What it helps with

compare a diff with acceptance criteria
trace changed behavior through callers and tests
spot missing error handling in modified code
check relevant authorization and data-exposure risks
separate proven defects from missing evidence

Example prompts for the agent

Review the current diff against the task requirements and acceptance criteria.
Trace every changed behavior into its callers and tests, then report each finding with its file, line, trigger, impact, and correction.
Check the change for authorization or data-exposure risks, and distinguish observed defects from checks that were not run.

How to install vibe-review

1Skills CLI (Vercel)

npx skills add KhazP/vibe-coding-prompt-template --skill vibe-review -a claude-code

2Manually: put the files in place

~/.claude/skills/vibe-review/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/vibe-review/

1Skills CLI (Vercel)

npx skills add KhazP/vibe-coding-prompt-template --skill vibe-review -a codex

2Manually: put the files in place

.agents/skills/vibe-review/SKILL.md

For all projects use ~/.agents/skills/

1Skills CLI (Vercel)

npx skills add KhazP/vibe-coding-prompt-template --skill vibe-review -a cursor

2Manually: put the files in place

.cursor/skills/vibe-review/SKILL.md

Cursor also reads .agents/skills/ and .claude/skills/

1GitHub CLI

gh skill install KhazP/vibe-coding-prompt-template vibe-review

2Manually: put the files in place

.github/skills/vibe-review/SKILL.md

1Skills CLI (Vercel)

npx skills add KhazP/vibe-coding-prompt-template --skill vibe-review -a gemini-cli

2Platform CLI

gemini skills install https://github.com/KhazP/vibe-coding-prompt-template --path workflow/skills/vibe-review

Manually: put the files in place

.devin/skills/vibe-review/SKILL.md

The legacy .windsurf/skills/ path still works

Skills CLI (Vercel)

npx skills add KhazP/vibe-coding-prompt-template --skill vibe-review -a opencode

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about vibe-review

How do I install vibe-review in Claude Code?

Run npx skills add KhazP/vibe-coding-prompt-template --skill vibe-review -a claude-code, then check ~/.claude/skills/vibe-review/SKILL.md.

What does vibe-review do?

It reviews a proposed change against requirements, changed behavior, tests, and relevant security risks. Its findings point to files and lines and distinguish defects from missing verification.

Which tools does vibe-review use?

The skill is allowed to use Read, Glob, Grep, and Bash. If the agent cannot inspect files or run Bash, some review conclusions cannot be verified.

Source text

SKILL.md · MIT

---
name: vibe-review
description: Review a proposed change against requirements, regressions, verification evidence, and relevant security risks.
allowed-tools: Read, Glob, Grep, Bash
---

# Vibe Review

Read the actual diff, applicable instructions, acceptance criteria, and check results. Trace changed behavior into its callers and tests. Look for concrete regressions, missing error handling, incorrect assumptions, and relevant authorization or data exposure issues.

Report actionable findings with file/line, trigger, impact, and suggested correction. Distinguish demonstrated defects from missing evidence. Prioritize correctness and scope over cosmetic preferences. Do not claim independent checks unless you ran them. If there are no findings, say so and disclose remaining verification gaps. Review does not authorize unrelated edits or publication.

improve-codebase-architecture Matt Pocock This skill scans a codebase for architectural friction, then builds a visual HTML report with refactoring candidates. Use it before a deeper architecture review. 1,163,035installs tdd Matt Pocock Guides the red-green TDD loop: ensures tests are written first, keep them at public interfaces, and avoid coupling to implementation details. 1,141,062installs triage Matt Pocock This skill moves issues and external PRs through triage states, verification, and agent briefs. It fits maintainers managing an issue queue. 990,453installs codebase-design Matt Pocock This skill helps design modules with small interfaces and hidden complexity. Use it when refactoring code, choosing a seam, or making tests easier to write. 850,344installs code-review Matt Pocock Reviews changes from a chosen reference point against repository standards and the originating spec. Use it for a branch, PR, or work in progress. 789,521installs implement Matt Pocock Implements work from a specification or tickets, following a test-driven flow and ending with review and a commit. Use it when a coding task needs a defined delivery routine. 774,700installs

From the same set8

vibe-workflow This skill picks a workflow for a new app, an existing project change, or a bug. Use it when the next step depends on the project's current state. CX Codex +1 ★ 3,191repo stars vibe-verify This skill exercises a running product against acceptance criteria and reports evidence. A passing build on its own proves nothing about behavior. CX Codex +1 ★ 3,191repo stars vibe-research The skill runs research on an app idea or an open technical question before you commit to a design. CX Codex +1 ★ 3,191repo stars vibe-handoff Creates a compact project handoff for another session or coding tool. It captures current work without copying chat transcripts or secrets. CX Codex +1 ★ 3,191repo stars vibe-debug A skill that walks an agent through a reproducible failure in an existing project: crashes, broken behavior, failing checks. Not for greenfield planning. CX Codex +1 ★ 3,191repo stars vibe-build This skill takes a new-project slice from the brief to a working user journey and relevant checks. Use it when a passing build alone is not enough. CX Codex +1 ★ 3,191repo stars vibe-agents Turns agreed product and technical decisions into AGENTS.md and tool configuration. Useful once requirements are settled but the agent files are not written yet. CX Codex +1 ★ 3,191repo stars