audit

Automate post-build reviews against plan, spec, and project doctrine.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Angel1104/praxis-core --skill audit-angel1104
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/Angel1104/praxis-core/tree/main/skills/audit
Command: npx skills add https://github.com/Angel1104/praxis-core --skill audit-angel1104

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Post-build review gate. Validates the completed implementation before closure and ensures alignment with plan, spec, and project doctrine.

Core Features & Use Cases

  • Three-perspective post-build review (Structural Integrity, Security Exposure, Operational Impact) with automated PASS/ BLOCKED verdict.
  • Autonomous BLOCKER resolution where possible, with evidence-backed findings.
  • Provides a formal review artifact and updates CR state accordingly.

Quick Start

Provide a CR-ID to run the end-to-end post-build review workflow.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I automate post-build code review against project specifications?

Post-build review validates completed implementations against the plan, spec, and project doctrine. It reads CR artifacts, build summaries, and test results to ensure the review is grounded in evidence and traceable before closure.

What is autonomous post-build verification for software architecture?

Autonomous post-build verification is a formal review gate that applies three mandatory perspectives: Structural Integrity, Security Exposure, and Operational Impact. It outputs a PASS or BLOCKED verdict to ensure alignment with architectural specifications.

How do I resolve blockers found during automated code review?

Blocker resolution during automated code review is handled autonomously where possible. The system outputs evidence-backed findings for BLOCKED verdicts and attempts to resolve the identified structural, security, or operational issues automatically.

Does post-build audit work with existing CR artifacts and test results?

Post-build audit works directly with existing CR artifacts, build summaries, and test results. It reads these inputs to ground the formal review in evidence, ensuring traceability and updating the CR state with the final PASS or BLOCKED verdict.

What's the best way to enforce a security exposure check before closing a build?

Enforcing a security exposure check before closure is handled by applying mandatory review perspectives during post-build verification. The workflow evaluates Security Exposure alongside Structural Integrity and Operational Impact to output a formal PASS or BLOCKED verdict.

When do I need a formal post-build review gate in my workflow?

A formal post-build review gate is needed when you must validate a completed implementation before closure and ensure alignment with project doctrine. It provides a formal review artifact and updates the CR state to prevent unverified builds from passing.