review-council

Coordinate multi-perspective code review across security, architecture, performance, and maintainability.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/matt-metivier/zk-hub --skill review-council-matt-metivier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-council
Source: https://github.com/matt-metivier/zk-hub/tree/main/skills/review-council
Command: npx skills add https://github.com/matt-metivier/zk-hub --skill review-council-matt-metivier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unified entry point for all council-based review workflows. Evaluates inputs from security, architecture, performance, and maintainability viewpoints, then synthesizes a go/no-go recommendation.

Core Features & Use Cases

  • Load and orchestrate security, architecture, performance, maintainability perspectives in parallel
  • Synthesize findings into a go/no-go verdict with bias mitigation and reproducible outputs
  • Enforce repo-skill checklist injection and validation steps to ensure domain conventions are followed

Quick Start

Submit a PR diff to the council to start a multi-perspective review.

Frequently Asked Questions about review-council

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

FAQPage Schema
How do I automate multi-perspective PR reviews for security and architecture risks?

Multi-perspective PR reviews are automated by coordinating parallel analysis across security, architecture, performance, and maintainability viewpoints, synthesizing findings into a validated go/no-go verdict with bias mitigation.

What is bias mitigation in code review and how does it improve go/no-go decisions?

Bias mitigation in code review balances inputs from multiple analysis perspectives to reduce individual blind spots, ensuring the synthesized go/no-go recommendation accurately reflects security and maintainability risks.

How do I enforce repository conventions during automated pull request analysis?

Repository conventions are enforced during pull request analysis by injecting and validating repo-skill checklists, ensuring domain-specific rules are followed before generating the final review synthesis.

Can I use multi-perspective analysis for CI pipeline diagnosis and auto-merge gating?

Yes, multi-perspective analysis applies to CI diagnosis and auto-merge gating by loading machine skills and checklist data to evaluate code changes, surface risks, and produce reproducible gating verdicts.

How do I synthesize research findings from multiple technical perspectives?

Research synthesis is generated by loading diverse technical perspectives in parallel, applying bias mitigation to evaluate the combined inputs, and outputting a unified, validated verdict.