parallel-audit

Execute parallel-agent audits to surface side effects and regressions from code changes.

4|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/greenheadHQ/nixos-config --skill parallel-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: parallel-audit
Source: https://github.com/greenheadHQ/nixos-config/tree/main/modules/shared/programs/claude/files/skills/parallel-audit
Command: npx skills add https://github.com/greenheadHQ/nixos-config --skill parallel-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Exhaustive side-effect/regression audit via parallel agents to quickly surface issues introduced by changes across the project, reducing risk and manual review burden.

Core Features & Use Cases

  • Parallel, agent-based execution with a configurable agent count to scale coverage.
  • Independent agent contexts ensure isolation and reproducible findings across macOS and NixOS platforms.
  • Systematic perspectives guide change validation, including performance, API compatibility, and edge cases; outputs include concrete file:line references.

Quick Start

Run the audit with 10 agents on the current changes to start the parallel exploration.

Frequently Asked Questions about parallel-audit

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

FAQPage Schema
How do I audit code changes for side effects and regressions across different platforms?

You can audit code changes using parallel-agent execution to surface side effects and regressions. This approach validates platform-specific behavior across macOS and NixOS, outputting concrete file and line references for performance, API compatibility, and edge case issues.

What is the best way to scale regression coverage when validating macOS and NixOS compatibility?

Scaling regression coverage is best achieved by configuring a high parallel agent count, such as 10 agents. This allows independent contexts to simultaneously explore platform-specific behavior, API compatibility, and performance implications across macOS and NixOS.

How do parallel agents isolate findings during a side effect audit?

Parallel agents isolate findings by maintaining independent contexts during execution. This ensures reproducible auditing results, preventing cross-contamination of perspectives while systematically evaluating performance, API compatibility, and edge cases across platform-specific changes.

Does parallel-audit work with NixOS and macOS for validating platform-specific behavior?

Yes, parallel-audit works with NixOS and macOS by validating platform-specific behavior during change reviews. It explicitly targets platform implications, API compatibility, and performance regressions using independent agent contexts to ensure accurate findings.

How do I start a parallel code review to surface performance and API compatibility issues?

You can start a parallel code review by running the audit with a configurable agent count, such as 10 agents, on current changes. This initiates parallel exploration to systematically surface performance, API compatibility, and edge case issues.