orchestration-postbuild

Automate post-build code denoising and parallel frontend, backend, documentation, and security audits.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/sebastianspicker/phased-agent-orchestration --skill orchestration-postbuild
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orchestration-postbuild
Source: https://github.com/sebastianspicker/phased-agent-orchestration/tree/main/.cursor/skills/orchestration-postbuild
Command: npx skills add https://github.com/sebastianspicker/phased-agent-orchestration --skill orchestration-postbuild

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates critical post-build quality checks, including code cleanup and comprehensive security and documentation audits, ensuring the software meets high standards before release.

Core Features & Use Cases

  • Code Denoising: Removes dead imports, unused variables, and debug leftovers while preserving behavior and rerunning tests.
  • Multi-faceted Audits: Conducts frontend, backend, documentation, and security reviews.
  • Security Remediation Loop: Identifies security vulnerabilities, enforces fixes, and verifies remediation.
  • Use Case: After a new feature is built and tested, this Skill can automatically clean up any introduced cruft, scan for security flaws like hardcoded secrets or XSS vulnerabilities, and ensure documentation is up-to-date, providing a consolidated gate result.

Quick Start

Run the orchestration-postbuild skill to perform denoising and security audits on the latest changes.

Frequently Asked Questions about orchestration-postbuild

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

FAQPage Schema
How do I automate post-build code cleanup and remove dead imports?▼

Post-build code cleanup is automated through code denoising, which removes dead imports, unused variables, and debug leftovers while preserving behavior and rerunning tests to ensure functionality remains intact.

What is a post-build security audit and how does it handle vulnerabilities?▼

A post-build security audit scans for flaws like hardcoded secrets or XSS vulnerabilities. It enforces a remediation loop that identifies vulnerabilities, requires fixes, and verifies the remediation before passing the gate.

What do I need to run parallel frontend, backend, and documentation audits?▼

To run parallel audits, you need specific input artifacts including changed implementation files and a plan.json file. The process utilizes fast worker models to execute the frontend, backend, documentation, and security reviews.

Can I enforce strict quality gates that block releases for critical violations?▼

Yes, strict gate conditions are enforced by requiring no critical violations, fixed security issues, and updated public API documentation. The process provides a consolidated gate result to determine if the software meets release standards.

When should I run a post-build quality assurance check in my development workflow?▼

Run quality assurance checks after a new feature is built and tested. This ensures any introduced cruft is cleaned up, security flaws are remediated, and documentation is verified before proceeding to release.