review-code

Coordinate multi-perspective code reviews with SAST checks and council votes.

12|4|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/andrewvaughan/agent-council --skill review-code-andrewvaughan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-code
Source: https://github.com/andrewvaughan/agent-council/tree/main/canonical/skills/review-code
Command: npx skills add https://github.com/andrewvaughan/agent-council --skill review-code-andrewvaughan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates comprehensive, multi-perspective code reviews across security, quality, documentation, and domain review to surface issues before changes reach a pull request.

Core Features & Use Cases

  • Activates the Review Council to evaluate code changes from security, quality, documentation, and domain perspectives.
  • Runs automated security scanning (SAST) and provides structured findings for review.
  • Generates council-ready recommendations and formal votes to accelerate safe merges and improve code quality.

Quick Start

Review the current changes on your feature branch with this skill to receive a council-backed assessment.

Frequently Asked Questions about review-code

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

FAQPage Schema
How do I automate multi-perspective code reviews before creating a pull request?

Pre-pull request code review automation analyzes branch diffs across security, quality, documentation, and domain perspectives. It executes SAST checks and delivers council-ready reports with formal votes to accelerate safe merges before changes are submitted.

What is a Review Council for code changes and how does it work?

A code review council coordinates multiple evaluation perspectives—security, quality, documentation, and domain—to assess code changes. It automates diff analysis, performs SAST checks, and delivers formal votes with structured findings for merge decisions.

Can I run SAST checks and diff analysis on feature branches without opening a PR?

SAST checks and diff analysis can be executed on feature branches during pre-PR review cycles. The skill applies to ongoing review cycles where code changes exist, running security scans and surfacing issues before pull request submission.

Does this code review approach work with ongoing review cycles or only new pull requests?

This code review approach applies to both pre-PR feature branch checks and ongoing review cycles where code changes exist. It activates the Review Council whenever diffs are available, making it suitable for continuous evaluation beyond new pull requests.

What's the best way to get structured findings and votes for code review decisions?

Structured findings and formal votes are generated by coordinating a multi-perspective council review across security, quality, documentation, and domain dimensions. The system automates diff analysis and SAST checks to deliver council-ready recommendations for merge decisions.

When should I not use automated council-style code review?

Automated council-style code review should not be used when no code diffs exist for analysis, since the system requires branch changes to evaluate. For trivial modifications lacking security or documentation implications, the multi-perspective assessment overhead may be unnecessary.