Run any Skill in Manus with one click

review

Stars8

Forks2

UpdatedApril 22, 2026 at 09:14

Review the diff between the current branch and its merge base against main (or master). Flag bugs, regressions, missing tests, and style deviations. Use when the user asks to review the current branch or a pending change.

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

QualityUnit

QualityUnit/harnext

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	review
description	Review the diff between the current branch and its merge base against main (or master). Flag bugs, regressions, missing tests, and style deviations. Use when the user asks to review the current branch or a pending change.

review

Review the pending changes on the current branch.

Steps

bash: git rev-parse --abbrev-ref HEAD; detect base branch (prefer main, fall back to master).
bash: git merge-base HEAD <base>, then git diff <merge-base>...HEAD --stat and git diff <merge-base>...HEAD.
read each changed file at HEAD — diff alone misses surrounding context.
Per file, call out: correctness bugs, missing error handling, missing/weak tests, violated project conventions (cross-reference siblings).
Summarize as Must fix / Should fix / Nits with file:line citations.

Guardrails

Review is read-only. Never edit files.
If the diff is empty or main isn't a shared ancestor, stop and report that instead of guessing.

More from this repository

same repository

report-harnext-issue

QualityUnit/harnext

File a GitHub issue against the harnext repo (QualityUnit/harnext) from within harnext, enriched with non-sensitive environment context. Uses a fallback chain (authenticated gh → GitHub REST API with a token → zero-auth prefilled issue URL) so reporting works even without gh installed or authenticated. Reserved for the /report-harnext-issue command.

2026-06-198

browser-verify

QualityUnit/harnext

Drive a real Chromium-based browser (Chrome/Edge/Brave) to reproduce a reported UI bug (triage mode) or verify an implementation (tester mode). Produces a video, a Playwright trace, and text artifacts (console/network/page errors, accessibility snapshots) that the agent can read to decide pass/fail. Use when the user asks to verify a UI change, reproduce a UI bug, or produce browser evidence for a PR/issue.

2026-04-248

init

QualityUnit/harnext

Detect the repo's tech stack (including monorepo sub-apps) and scaffold a project-local `setup` skill at `<cwd>/.harnext/skills/setup/` that lets future harnext sessions install dependencies, run each runnable app in the background, and attach to their logs. Use when bootstrapping a new repo.

2026-04-228

name	review
description	Review the diff between the current branch and its merge base against main (or master). Flag bugs, regressions, missing tests, and style deviations. Use when the user asks to review the current branch or a pending change.

review

Review the pending changes on the current branch.

Steps

bash: git rev-parse --abbrev-ref HEAD; detect base branch (prefer main, fall back to master).
bash: git merge-base HEAD <base>, then git diff <merge-base>...HEAD --stat and git diff <merge-base>...HEAD.
read each changed file at HEAD — diff alone misses surrounding context.
Per file, call out: correctness bugs, missing error handling, missing/weak tests, violated project conventions (cross-reference siblings).
Summarize as Must fix / Should fix / Nits with file:line citations.

Guardrails

Review is read-only. Never edit files.
If the diff is empty or main isn't a shared ancestor, stop and report that instead of guessing.