audit

Compose existing checks into a single read-only AUDIT verdict for unit promotability.

28|3|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/mifunedev/openharness --skill audit-mifunedev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/mifunedev/openharness/tree/main/.claude/skills/audit
Command: npx skills add https://github.com/mifunedev/openharness --skill audit-mifunedev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This gate consolidates multiple per-unit checks into a single, read-only verdict for the executable loop, enabling consistent, fast decisions on whether an implementation is promotable.

Core Features & Use Cases

  • Composes existing checks (task-graph conformance, regression floor, CI/promotable state) into a unified AUDIT-PASS/AUDIT-FAIL decision.
  • Works with or without an open pull request by evaluating PR status or CI state for the current branch.
  • Emits a final routing token to drive downstream workflow (retro on success, implement on failure) for automated handoff.

Quick Start

Invoke the audit node for the target implementation to produce a single AUDIT-PASS or AUDIT-FAIL verdict and emit the final routing token.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I automate per-unit audit verdicts for pull requests?

Per-unit audit verdicts are automated by composing task-graph conformance, regression floor, and CI state checks into a single read-only AUDIT-PASS or AUDIT-FAIL decision for the target implementation slug.

What is a read-only verdict gate in CI workflows?

A read-only verdict gate consolidates multiple pull request checks into one unified promotability decision without modifying repository state, emitting a routing token for downstream workflow automation.

Can I evaluate branch promotability without an open pull request?

Branch promotability can be evaluated without an open pull request by falling back to assess the current CI state for the specified branch instead of PR status.

How does the audit gate handle routing tokens after evaluating implementation checks?

The audit gate emits a final routing token after evaluating implementation checks, directing downstream workflows to trigger a retro on success or route back to implementation on failure.

What checks are required to pass a per-unit audit gate?

Passing a per-unit audit gate requires satisfying task-graph conformance, meeting the regression floor, achieving a promotable CI state, and optionally completing UI verification.

Does the audit gate modify repository state when deciding PR mergeability?

The audit gate does not modify repository state; it operates as a read-only evaluation that decides PR mergeability and unit promotability based on composed checks.