forge:approve

Approve pending FORGE gates and update run status to completed.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/Chulf58/FORGE --skill forge-approve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge:approve
Source: https://github.com/Chulf58/FORGE/tree/main/skills/approve
Command: npx skills add https://github.com/Chulf58/FORGE --skill forge-approve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the manual gate approval step in FORGE pipelines, ensuring timely progression and auditable records.

Core Features & Use Cases

  • Locate the pending gate for a run using gate-pending.json or the run state, and identify Gate 1 or Gate 2.
  • Update gate status to "approved" and transition the associated run to "completed" with the correct currentStep and gateState.
  • Provide clear terminal feedback guiding the user to the next action (implement or apply) after approval.

Quick Start

Approve Gate 1 to begin the implementation phase.

Frequently Asked Questions about forge:approve

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

FAQPage Schema
How do I approve a pending gate in a FORGE pipeline to advance the run?

To approve a pending FORGE gate, the tool locates the correct run using gate-pending.json, updates the gate status to approved, transitions the run to completed, and notifies you to implement or apply next.

What happens to run state when a FORGE gate approval is triggered?

Triggering a FORGE gate approval updates the gate status to approved and transitions the run state to completed with the correct currentStep and gateState values for audit trail tracking.

How do I automate manual pipeline gate approvals for feature cycles?

Automating manual pipeline gate approvals requires resolving the gate file location for Gate 1 or Gate 2, emitting approval messaging, and updating the run status to completed automatically.

Does the FORGE gate approval process work for both Gate 1 and Gate 2?

Yes, the FORGE gate approval process is applicable when gating at either Gate 1 or Gate 2 during a feature cycle, resolving the correct gate file location to update the status.

Why do I need to update the gate status to advance my pipeline run state?

Updating the gate status to approved is required to transition the associated run state to completed, ensuring timely pipeline progression and maintaining an auditable record of the gate decision.