skills.rest
The-Vibe-Company
The-Vibe-CompanyOFFICIAL
Explore all skills by this author →
WebsiteGitHub

review-code-dev

Review local code changes with isolated reviewers and produce verified P0-P3 findings.

2.4k|292|Updated Feb 7, 2026
Search Tags:#static analysis#subagents#Git#security review#pre-commit#Code review#Pull request
One-click install
npx skills add https://github.com/The-Vibe-Company/companion --skill review-code-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-code-dev
Source: https://github.com/The-Vibe-Company/companion/tree/main/.agents/skills/review-code-dev
Command: npx skills add https://github.com/The-Vibe-Company/companion --skill review-code-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Code review is often skipped, rushed, or mixed into the same conversation that wrote the code, which lets real bugs slip through and floods the chat with unverified suggestions. This Skill runs an independent, strictly read-only review of your local changes and returns only evidence-backed, severity-ranked findings.

Core Features & Use Cases

  • Isolated read-only review: One isolated primary reviewer inspects the diff, with at most 2-3 focused specialist reviewers (security, frontend, performance, migrations, API contracts, red-team) launched only for independent high-risk questions.
  • Verified P0-P3 findings: Every candidate finding is verified against the actual code, deduplicated by fingerprint, and published only with file/line, failure path, impact, and a false-positive check.
  • Safe artifacts and PR watch: Review artifacts are written to a Git-ignored run directory that can never be committed, secrets are redacted from collected context, and an atomic ledger supports recurring PR monitoring without duplicate reviews.
  • Use Case: Before opening a pull request, ask for a review of your branch against main; the Skill collects the diff, checks auth and migration risks, and returns a short list of confirmed issues that should block merge.

Quick Start

Ask the assistant to review your uncommitted changes or your current branch against main and report only the actionable issues.

Frequently Asked Questions about review-code-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review uncommitted changes before committing?▼

Ask for a review of your uncommitted changes and the Skill collects git status, staged and unstaged diffs, and untracked file previews into a context file. An isolated reviewer inspects every changed file and returns only confirmed P0-P3 findings with file and line references.

How to review a branch against main before opening a PR?▼

Request a base-mode review naming your base branch, and the Skill diffs your branch against that ref, audits intent and scope, and checks high-risk areas like auth, migrations, and API contracts. Findings are verified against the actual code before being reported.

Does this code review modify my files or Git state?▼

No, the review is strictly read-only: it never edits source, stages, commits, checks out, or runs tests and builds. Artifacts are written only to a plans/review-code-dev run directory that is added to the local Git exclude file and verified as ignored before any file is written.

Can the review use subagents for security or frontend checks?▼

Yes, the primary reviewer can launch up to two focused reviewers for standard effort or three for deep effort, covering lenses like security, frontend, performance, data migrations, and API contracts. Every helper candidate is verified and deduplicated by the primary reviewer before publication.

What are the limitations of automated read-only code review?▼

The review does not run tests, linters, or builds during the review phase, so runtime behavior is inferred from code reading rather than execution. Findings below confidence 7 are withheld, and truncated diffs or unavailable external consumers are marked as partial coverage.

Related Skills

Explore More Software Engineering Skills→
mhertmhert

code-review

Analyze git diffs to generate severity-classified code review reports.

Community
Advanced
bernajaberbernajaber

review

Review git diffs for UX, visual, accessibility, security, and constitution violations.

Community
Intermediate
synaptiaisynaptiai
6

runtime-verification

Launch development servers and run smoke, end-to-end, and browser tests.

Official
Advanced
ccomkhjccomkhj
8

pair-coding

Coordinate Claude Code and Codex pair-programming with proposer/reviewer sign-offs.

Community
Advanced