Run any Skill in Manus with one click

code-review

Stars3

Forks1

UpdatedJune 25, 2026 at 10:15

Review completed changes for blockers, regressions, security, and scope drift. Use with /code-review before merge or final handoff.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

damian87x

damian87x/oh-my-copilot

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	code-review
description	Review completed changes for blockers, regressions, security, and scope drift. Use with /code-review before merge or final handoff.

Code Review

Use /code-review before merge or final handoff.

When to use

Changes are complete and ready for review
You need a second opinion before shipping
You want to catch regressions, security issues, or scope drift

Steps

Read the diff — git diff for unstaged, git diff --staged for staged, or git diff main...HEAD for branch diff
Check for blockers — bugs, logic errors, missing error handling, broken contracts
Check for security — secrets in code, injection risks, auth gaps, unsafe defaults, and data exposure / least privilege: does the change return, log, or expose more than it needs (PII, password hashes, SELECT *, tokens, internal fields)?
Check for regressions — does the change break existing tests or documented behaviour?
Check for scope drift — does the change do more or less than requested?
Run tests if they exist and haven't been run

Rules

Don't stop at the first issue. Once you find a blocker, keep scanning the whole change — a serious bug (e.g. a data leak) often hides behind the obvious one. Review every line.
Only flag issues that genuinely matter — no style nits, no formatting opinions
If the code works, tests pass, and scope is right, say so clearly
Flag anything you'd reject in a PR review

Output

Verdict — PASS / NEEDS_CHANGES / BLOCKER
Blocking — issues that must be fixed before merge
Non-blocking — suggestions or observations
Evidence reviewed — what was checked (diff, tests, build)

More from this repository

same repository

skill-bench

damian87x/oh-my-copilot

Use when a user wants to compare an arbitrary skill or path across models, quality, cost, latency, or routing.

2026-07-173

history-analyze

damian87x/oh-my-copilot

Analyze actual local Copilot skill activations without reading conversation content.

2026-07-163

wayfinder

damian87x/oh-my-copilot

Plan work too big for one agent session as a shared map of decision tickets on GitHub Issues or Jira, then resolve them one at a time until the route is clear. Use with /wayfinder when the user says "plan something too big for one session", "chart a map", "wayfind", "work the map", or "decision tickets". Always confirm tracker (GitHub vs Jira) and destination before writing. Adapted from mattpocock/skills wayfinder (MIT).

2026-07-163

handoff

damian87x/oh-my-copilot

Create or resume a task handoff so a fresh agent can continue unfinished work. Persist via omp handoff CLI (never write handoff files yourself). Use when the user says /handoff, wants to pause mid-task, or resume prior work.

2026-07-153

ralph

damian87x/oh-my-copilot

Single-owner execute-fix-verify loop for one clear task. Use with /ralph when one agent should keep going until evidence or blocker.

2026-07-053

ultraqa

damian87x/oh-my-copilot

Adversarial QA pass that tests behavior, failures, and regressions. Use with /ultraqa after implementation when shallow checks are not enough.

2026-07-053

name	code-review
description	Review completed changes for blockers, regressions, security, and scope drift. Use with /code-review before merge or final handoff.

Code Review

Use /code-review before merge or final handoff.

When to use

Changes are complete and ready for review
You need a second opinion before shipping
You want to catch regressions, security issues, or scope drift

Steps

Read the diff — git diff for unstaged, git diff --staged for staged, or git diff main...HEAD for branch diff
Check for blockers — bugs, logic errors, missing error handling, broken contracts
Check for security — secrets in code, injection risks, auth gaps, unsafe defaults, and data exposure / least privilege: does the change return, log, or expose more than it needs (PII, password hashes, SELECT *, tokens, internal fields)?
Check for regressions — does the change break existing tests or documented behaviour?
Check for scope drift — does the change do more or less than requested?
Run tests if they exist and haven't been run

Rules

Don't stop at the first issue. Once you find a blocker, keep scanning the whole change — a serious bug (e.g. a data leak) often hides behind the obvious one. Review every line.
Only flag issues that genuinely matter — no style nits, no formatting opinions
If the code works, tests pass, and scope is right, say so clearly
Flag anything you'd reject in a PR review

Output

Verdict — PASS / NEEDS_CHANGES / BLOCKER
Blocking — issues that must be fixed before merge
Non-blocking — suggestions or observations
Evidence reviewed — what was checked (diff, tests, build)