approve

Name: approve
Availability: InStock
Author: Mifune

Read critic findings and emit an APPROVED or DENIED verdict.

28|3|Updated Mar 27, 2026

Search Tags:#automation #workflow #decision #approve #critique #gate

Ready to run

npx skills add https://github.com/mifunedev/openharness --skill approve-mifunedev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: approve
Source: https://github.com/mifunedev/openharness/tree/main/.claude/skills/approve
Command: npx skills add https://github.com/mifunedev/openharness --skill approve-mifunedev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The approve gate prevents premature commits by reading critic findings and emitting a single APPROVED or DENIED verdict before any GitHub-side state exists, ensuring decisions are made on local artifacts.

Core Features & Use Cases

Gate the spec before commitment by evaluating critique findings and enforcing a clear go/no-go decision.
Emit a single STATUS line and route the workflow to the next node only after an APPROVED verdict.
Support an optional human override in non-auto mode for borderline findings.

Quick Start

Run the approve gate on a critiqued spec to determine APPROVED or DENIED before any GitHub state is created.

Frequently Asked Questions about approve

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

FAQPage Schema

How do I gate a spec before committing to prevent premature commits?▼

To gate a spec before committing, this Skill reads critique findings and emits a single APPROVED or DENIED verdict, preventing premature commits before any GitHub-side state exists.

What is an automated approval gate in a local workflow?▼

An automated approval gate evaluates critique findings on local artifacts, enforcing a clear go/no-go decision before any GitHub-side state is created, routing the workflow only after an APPROVED verdict.

How do I enforce an auto-gate decision without human override?▼

You can enforce auto-gate behavior by using the --auto flag, which bypasses the optional interactive human override and strictly enforces the automated go/no-go decision based on critic findings.

Can I manually override a denied workflow verdict for borderline findings?▼

Yes, in non-auto mode, you can use an optional interactive human override to manually approve borderline findings, allowing flexibility when the automated decision logic is uncertain.

When do I need an automated decision gate in my workflow?▼

You need an automated decision gate when a plan or PRD has been critiqued and requires a formal go/no-go decision before any GitHub-side state is created, ensuring decisions are made on local artifacts.