auditor-gate

Read handoff and verdict JSON to emit audit.json with a gate status.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/OilProducts/agent-skills --skill auditor-gate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auditor-gate
Source: https://github.com/OilProducts/agent-skills/tree/main/auditor-gate
Command: npx skills add https://github.com/OilProducts/agent-skills --skill auditor-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the final governance and release-gate checks for code changes, ensuring compliance and quality before deployment without altering the source code.

Core Features & Use Cases

  • Automated Auditing: Applies final governance and release-gate checks to a judged change set.
  • Artifact Generation: Reads handoff.json, verdict.json, and optional evaluation evidence to emit a machine-readable audit.json with a gate status (pass, fail, or needs-human).
  • Use Case: After a code change has been judged for functional correctness, this Skill acts as an independent auditor to verify policy compliance, traceability, and overall landability, producing a clear pass/fail/needs-human decision.

Quick Start

Use the auditor-gate skill to apply final governance checks to the current change set using the provided handoff and verdict artifacts.

Frequently Asked Questions about auditor-gate

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

FAQPage Schema
How do I automate release gate checks for a judged code change set?

You can automate release gate checks by reading handoff.json and verdict.json to evaluate compliance, emitting an audit.json file with a final pass, fail, or needs-human gate status without modifying source files.

What is an automated audit gate in a CI/CD governance pipeline?

An automated audit gate is a final compliance checkpoint that reads evaluation evidence and verdicts to decide code landability, outputting a machine-readable gate status to enforce governance before deployment.

How do I enforce compliance and governance without altering source code?

You enforce compliance by running an independent auditor process that reads existing judgment artifacts like verdict.json, evaluates policy adherence, and outputs an audit.json gate decision while leaving source files untouched.

When do I need a separate auditor to decide code landability after a judge verdict?

You need a separate auditor when implementation has a functional judge verdict but still requires an independent governance check to verify policy compliance, traceability, and overall release readiness before landing.

Can I use an automated release gate for needs-human compliance decisions?

Yes, the automated release gate evaluates judged change sets and can output a needs-human status in audit.json when policy compliance or landability criteria cannot be fully resolved automatically.

What format does an automated release gate output for deployment governance?

An automated release gate outputs a machine-readable audit.json file containing the final gate status, providing a clear pass, fail, or needs-human decision for downstream deployment automation.