skills.rest
laozhong86
laozhong86COMMUNITY
Explore all skills by this author →
GitHub

gxpm-review-army

Orchestrate two-stage code review with spec-compliance gating and parallel quality reviewers.

1|Updated Apr 24, 2026
Search Tags:#code-review#auditability#spec-compliance#parallel-review#two-stage#gxpm#review-army
One-click install
npx skills add https://github.com/laozhong86/gxpm --skill gxpm-review-army
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gxpm-review-army
Source: https://github.com/laozhong86/gxpm/tree/main/skills/gxpm-review-army
Command: npx skills add https://github.com/laozhong86/gxpm --skill gxpm-review-army

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates a disciplined, two-stage review process to ensure spec compliance before launching broad code-quality scrutiny, reducing wasted effort on faulty changes.

Core Features & Use Cases

  • Stage 1: Spec Compliance Gate validates that a change satisfies acceptance contracts and behavioral specs before any downstream review.
  • Stage 2: Parallel Review Fan-out runs Code Quality, Security, Test, and Accessibility reviewers concurrently after Stage 1 passes, accelerating verification.
  • Unified Findings Payload aggregates all reviewer findings into a single flat array for auditable, replayable governance.
  • Gate-driven Progress uses blocking findings to prevent stage transitions until issues are resolved, with deterministic retry loops.

Quick Start

Initiate the two-stage army workflow on an issue by triggering self-review with Army mode to run Stage 1 gating and, if cleared, Stage 2 parallel reviews.

Frequently Asked Questions about gxpm-review-army

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

FAQPage Schema
How does a two-stage code review process improve spec compliance?▼

A two-stage code review process improves spec compliance by running a dedicated acceptance gate that validates behavioral specs before any quality review begins, reducing wasted effort on faulty changes.

How do I run parallel code reviews for security and test coverage?▼

You run parallel code reviews by triggering self-review with Army mode, which clears Stage 1 gating and fans out up to six concurrent reviewers covering Code Quality, Security, Test, and Accessibility.

Can I block code stage transitions when review findings are unresolved?▼

Yes, gate-driven progress blocks stage transitions when unresolved findings exist, using deterministic retry loops to prevent code progression until issues are resolved.

What is the best way to audit cross-domain code review findings?▼

The best way to audit cross-domain code review findings is to aggregate all reviewer outputs into a single unified flat findings payload, ensuring replayable governance.

When should I not use a spec-compliance gate for code review?▼

You should not use a spec-compliance gate for changes that do not require comprehensive cross-domain verification, as the blocking findings will prevent stage transitions unnecessarily.

Related Skills

Explore More Software Engineering Skills→
nyldnnyldn
4.0k

skill-staged-review

Enforce two-stage review for spec compliance and code quality before merge.

Community
Advanced
ben-alkovben-alkov
5

swarm-fan-out

Orchestrate parallel specialist agents to analyze code and synthesize unified reports.

Community
Advanced
wshobsonwshobson
38.6k

go-concurrency-patterns

Provide idiomatic Go examples for advanced concurrency patterns.

Community
Advanced
FaysilAlshareefFaysilAlshareef
4

code-review-workflow

Automates standardized code review guidance and enforcement on pull requests.

Community
Advanced