aidlc-requesting-code-review

Orchestrate multi-stage code-review workflows with specialized sub-agents and verdicts.

2|Updated Mar 10, 2026

Search Tags:#automation #workflow #orchestration #code-review #software-engineering #council-review #aidlc

Ready to run

npx skills add https://github.com/bluejayA/aidlc-devflow --skill aidlc-requesting-code-review-bluejaya

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aidlc-requesting-code-review
Source: https://github.com/bluejayA/aidlc-devflow/tree/main/skills/aidlc-requesting-code-review
Command: npx skills add https://github.com/bluejayA/aidlc-devflow --skill aidlc-requesting-code-review-bluejaya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates and coordinates comprehensive code-review workflows across multiple stages before merging.

Core Features & Use Cases

Multi-stage review orchestration: Supports Stage 1 spec compliance, Stage 2 code-quality, Stage 3 security/edge-case analysis, and Stage 4 maintainability, with optional Council-based reviews.
Flexible deployment modes: Standalone manual requests or SDD-driven automatic invocation after task completion.
Structured verdicts and actionable results: Returns a formal verdict and recommended actions, including where to modify code.
Use Case: Before merging a PR, request a full-code-review pass to ensure compliance with specs, security checks, and maintainability guidelines.

Quick Start

Ask aidlc-requesting-code-review to evaluate your PR by providing the changed file paths, an optional spec plan path, and your desired depth.

Frequently Asked Questions about aidlc-requesting-code-review

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

FAQPage Schema

How do I automate multi-stage code reviews before merging a PR?▼

Multi-stage code review automation orchestrates spec compliance, code quality, security, and maintainability checks in sequence. It dispatches specialized sub-agents for each review stage before merging, returning a synthesized verdict with actionable items.

What is a council-based code review workflow?▼

A council-based code review workflow coordinates multiple specialized review agents to evaluate code from different perspectives. It supplements standard stage reviews with broader analysis, enforcing stage sequencing and returning comprehensive structured verdicts.

How do I enforce spec compliance during a code review?▼

Spec compliance during code review is enforced by providing an optional spec plan path. The review process uses Stage 1 to verify code changes against the provided spec, returning actionable items for any non-compliant modifications.

Can I request a standalone code review without an automated pipeline?▼

Yes, standalone manual code review requests are supported. You can ask for a full code-review pass by providing changed file paths, an optional spec plan path, and your desired depth without needing automated pipeline triggers.

Does the code review workflow integrate with SDD-driven task completion?▼

Yes, SDD-driven automatic invocation triggers code review workflows after task completion. This flexible deployment mode sits alongside standalone manual requests to coordinate comprehensive multi-stage reviews before merging.

What limitations exist when requesting code review depth?▼

Code review depth is governed by available stages and optional council-based workflows. Limitations depend on the provided spec plan path and changed file paths, which determine how specialized sub-agents sequence and synthesize actionable verdicts.