Individual skill

vibe-review

Review a proposed change against requirements, regressions, verification evidence, and relevant security risks.

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

Read pinned source

Source commit d26fb0d8a9cdac94cf99f004087620487e4da33d

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Network or broad shell
Last checked: Nov 2, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 3,225
Repository last updated: Oct 4, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

ai-agents Repository topic
ai-workflow Repository topic
beginner-friendly Repository topic
mvp-development Repository topic
technical-design Repository topic
vibe-coding Repository topic
llm-tools Repository topic
workflow-automation Repository topic
claude-code Repository topic
chatgpt Repository topic
security Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 862 bytes

Read excerpt


# 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.