auto-review

Route code review requests to the full Autopus auto workflow.

106|74|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/Insajin/autopus-adk --skill auto-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-review
Source: https://github.com/Insajin/autopus-adk/tree/main/.autopus/plugins/auto/skills/auto-review
Command: npx skills add https://github.com/Insajin/autopus-adk --skill auto-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a thin alias surface that routes review requests to the full Autopus auto workflow, enabling end-to-end code review processing without duplicating routing logic.

Core Features & Use Cases

  • Thin alias shim: preserves user intent and flags while delegating execution to the detailed auto workflow.
  • Context Load & SPEC Path Resolution: handoff managed by the canonical router before the detailed workflow runs.
  • Use Case: When you issue a review command, this skill ensures the request is forwarded to the auto workflow for comprehensive evaluation.

Quick Start

Invoke the alias surface with a review request to load the full auto workflow.

Frequently Asked Questions about auto-review

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

FAQPage Schema
How do I route code review requests to an automated workflow?

Routing code review requests involves invoking a thin alias shim that forwards your command and context to a comprehensive auto workflow for end-to-end processing.

What is the best way to automate TRUST 5 code reviews?

Automating TRUST 5 code reviews is handled by routing the request through an alias surface that delegates execution to a detailed auto workflow while preserving user flags and intent.

Can I preserve command flags like --auto and --multi when automating code reviews?

Yes, you can preserve command flags like --auto and --multi when automating code reviews because the alias shim passes all flags exactly as issued to the detailed workflow.

How does context loading and SPEC path resolution work in an automated review workflow?

Context loading and SPEC path resolution work by handing off the review request to a canonical router, which manages context retrieval before the detailed auto workflow executes.

Do I need a separate routing logic setup for end-to-end code review processing?

You do not need a separate routing logic setup for end-to-end code review processing, as the alias shim delegates directly to the existing auto workflow without duplicating routing logic.