parallel-review-implementation

Generate structured JSON review findings for changed packages from Git diffs.

4|1|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/jankneumann/agentic-coding-tools --skill parallel-review-implementation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: parallel-review-implementation
Source: https://github.com/jankneumann/agentic-coding-tools/tree/main/.agents/skills/parallel-review-implementation
Command: npx skills add https://github.com/jankneumann/agentic-coding-tools --skill parallel-review-implementation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides an automated, vendor-diverse review process that inspects per-package or whole-branch diffs and produces machine-readable, actionable findings so integration gates can make safe decisions without ad-hoc manual triage.

Core Features & Use Cases

  • Per-package and whole-branch modes: Uses work-packages.yaml when available and falls back to whole-branch review when not.
  • Contract compliance and code-quality checks: Verifies OpenAPI/DB/event contracts, tests, error handling, security, performance, and observability for changed files.
  • Validation and orchestration integration: Produces JSON findings validated against the review-findings schema and writes artifacts for orchestrator-driven escalation and remediation flows.
  • Adversarial review option: Supports an adversarial persona to challenge design decisions for increased rigor in high-risk reviews.

Quick Start

Run parallel-review-implementation with the change id and package id to produce a validated review findings JSON file.

Frequently Asked Questions about parallel-review-implementation

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

FAQPage Schema
How do I generate structured code review findings from a git diff?

To generate structured code review findings from a git diff, apply this Skill to per-package or whole-branch changes. It produces machine-readable JSON validated against the review-findings schema for automated integration gates.

How does contract compliance validation work for changed packages?

Contract compliance validation inspects changed files within a git diff to verify OpenAPI, database, and event contracts. It runs code-quality checks covering tests, error handling, security, performance, and observability before outputting results.

Can I use per-package implementation reviews in an orchestrated CI workflow?

Yes, you can use per-package implementation reviews in orchestrated CI workflows. The Skill reads work-packages.yaml and work-queue results, then writes validated review-findings.json artifacts to support orchestrator-driven escalation and remediation.

What is the best way to review high-risk code changes with increased rigor?

The best way to review high-risk code changes with increased rigor is using the adversarial review option. This persona challenges design decisions during the implementation review to ensure thorough analysis of per-package diffs.

Do I need work-packages.yaml to run a whole-branch implementation review?

No, you do not need work-packages.yaml to run a whole-branch implementation review. The Skill uses work-packages.yaml when available for per-package modes but automatically falls back to whole-branch review when it is absent.

Why are my code review findings failing schema validation?

Code review findings fail schema validation if the output JSON does not match openspec/schemas/review-findings.schema.json. Ensure your contract artifacts and work-queue results are correctly formatted before running the review.