Run any Skill in Manus with one click

auto-review

Stars74

Forks6

UpdatedMarch 31, 2026 at 14:59

Review code changes and provide structured feedback. Use when: reviewing PRs, analyzing code diffs for bugs/security/style, or processing review.request relay events.

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

bit-vcs

bit-vcs/bit

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	auto-review
description	Review code changes and provide structured feedback. Use when: reviewing PRs, analyzing code diffs for bugs/security/style, or processing review.request relay events.

auto-review

Review code changes and provide structured feedback.

Trigger

User requests a code review
bit pr list shows PRs awaiting review
Relay event: review.request (optional, requires relay)

Steps

Get PR details: bit pr get <id> or git diff <base>...<head>
Analyze changes: Check for:
- Bugs and logic errors
- Security vulnerabilities (OWASP top 10)
- Code style and consistency
- Test coverage
- Performance implications
Write review: Provide constructive, specific feedback

Submit verdict:

# Local (bit pr)
bit pr review <pr-id> --approve --commit <hex> --body "LGTM"
# Via relay (optional)
bit relay review submit <repo> --pr <id> --verdict approve

Review format

## Summary
Brief description of what the PR does.

## Findings
- [severity] file:line — description

## Verdict
approve/request-changes with reasoning

Important

Be constructive, not just critical
Approve if changes are correct even if style differs from preference
Flag security issues as blocking
For MoonBit code, check for common issues: unused variables, missing error handling, type mismatches

More from this repository

same repository

bit-issue

bit-vcs/bit

Manage tasks with bit issue — Git-native issue tracking without external services. Use when: creating tasks, tracking work items, organizing sub-issues, searching issues, or managing project workflow with bit.

2026-07-1774

start-work

bit-vcs/bit

Manage implementation sessions with bit issue coordination. Use when: starting non-trivial code changes, resuming previous work, entering plan mode, creating branches, or doing parallel work. Triggers on keywords: bit issue, session, parallel work, resume, continue.

2026-07-1774

triage-issue

bit-vcs/bit

Analyze and triage issues — categorize, assess complexity, suggest approach. Use when: reviewing new issues, prioritizing backlog, or processing hub.issue relay events.

2026-07-1774

fix-ci

bit-vcs/bit

Investigate and fix CI failures. Use when: debugging failed GitHub Actions runs, fixing build/test failures, or processing ci.status relay events.

2026-05-1574

relay-respond

bit-vcs/bit

Push results back to a bit relay room after completing a task. Use when: reporting CI status, submitting PR reviews, commenting on issues, or publishing agent responses via relay.

2026-03-3174

relay-sync

bit-vcs/bit

Synchronize bit issues and PRs across repositories via a relay server. Use when: coordinating with remote sessions, sharing issues between machines, syncing hub data across clones, or the user mentions relay, sync, remote coordination, or distributed issues.

2026-03-2574

name	auto-review
description	Review code changes and provide structured feedback. Use when: reviewing PRs, analyzing code diffs for bugs/security/style, or processing review.request relay events.

auto-review

Review code changes and provide structured feedback.

Trigger

User requests a code review
bit pr list shows PRs awaiting review
Relay event: review.request (optional, requires relay)

Steps

Get PR details: bit pr get <id> or git diff <base>...<head>
Analyze changes: Check for:
- Bugs and logic errors
- Security vulnerabilities (OWASP top 10)
- Code style and consistency
- Test coverage
- Performance implications
Write review: Provide constructive, specific feedback

Submit verdict:

# Local (bit pr)
bit pr review <pr-id> --approve --commit <hex> --body "LGTM"
# Via relay (optional)
bit relay review submit <repo> --pr <id> --verdict approve

Review format

## Summary
Brief description of what the PR does.

## Findings
- [severity] file:line — description

## Verdict
approve/request-changes with reasoning

Important

Be constructive, not just critical
Approve if changes are correct even if style differs from preference
Flag security issues as blocking
For MoonBit code, check for common issues: unused variables, missing error handling, type mismatches