review

Review code, documents, or architecture with evidence-based findings and risk assessment.

1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/aibilitycz/superpowered-toolkit --skill review-aibilitycz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/aibilitycz/superpowered-toolkit/tree/main/plugins/super-intelligence/skills/review
Command: npx skills add https://github.com/aibilitycz/superpowered-toolkit --skill review-aibilitycz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a careful, evidence-based, single-pass evaluation of code, documents, or architecture to uncover issues without skimming for hours.

Core Features & Use Cases

  • Deep-dive analysis of diffs, PRs, files, plans, brainstorms, or specs with evidence-backed findings.
  • Auto-detection of review target and routing to appropriate evaluation patterns.
  • Clear verdicts and risk-based recommendations to guide next steps.
  • User-guided follow-ups to discuss findings or proceed with fixes.

Quick Start

Invoke the reviewer on a target (branch, PR, file, plan, brainstorm, or spec) and obtain a structured, evidence-based verdict in one deep pass.

Frequently Asked Questions about review

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

FAQPage Schema
How do I perform an evidence-based code review on a pull request without skimming for hours?

Perform an evidence-based code review by invoking an automated reviewer on your pull request to generate a single deep assessment. It auto-detects the PR diff, loads relevant project context, and presents structured findings with risk assessment.

Can I review architecture plans and brainstorm specs in addition to branch diffs?

Yes, you can review architecture plans and brainstorm specs. The reviewer auto-detects the target type—whether a branch diff, PR, file path, plan, brainstorm, or spec—and routes it to the appropriate evaluation pattern.

What is the best way to get a structured risk assessment for a code diff?

The best way to get a structured risk assessment for a code diff is using a focused single-pass reviewer. It evaluates the diff, gathers project context, and outputs clear verdicts with risk-based recommendations to guide next steps.

Does this code review approach provide actionable next steps after evaluating a file?

Yes, this code review approach provides actionable next steps after evaluating a file. It delivers evidence-backed findings and clear verdicts, allowing you to proceed with guided follow-ups to discuss the results or implement fixes.

When should I use a single-pass deep review instead of skimming code manually?

Use a single-pass deep review instead of skimming manually when you need to uncover complex issues in code, documents, or architecture. It provides a careful evaluation with evidence-backed findings, replacing hours of manual inspection.