skills.rest
mfittko
mfittkoCOMMUNITY
Explore all skills by this author →
GitHub

final-approval

Route dev loop execution to the canonical final approval and merge gate procedure.

14|1|Updated May 13, 2026
Search Tags:#github#pull-request#human-approval#dev-loop#workflow-routing#merge-gate#final-approval
One-click install
npx skills add https://github.com/mfittko/dev-loops --skill final-approval
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: final-approval
Source: https://github.com/mfittko/dev-loops/tree/main/.claude/skills/final-approval
Command: npx skills add https://github.com/mfittko/dev-loops --skill final-approval

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates confusion about where to find the official final approval and merge gate procedure for AI-driven dev loops, ensuring users always access the correct, up-to-date merge rules and required checkpoint steps.

Core Features & Use Cases

  • Canonical Procedure Redirect: Acts as a narrowed read-set pointer for the routed final_approval strategy, automatically routing users to the official Copilot PR Follow-up Skill for full merge gate instructions.
  • Merge Gate Compliance: Ensures all final approval steps follow standardized requirements, including CI verification, review thread resolution, and merge authorization checks.
  • Use Case: When a dev loop reaches the final approval phase, this Skill automatically loads the correct procedure so you don't have to search for or maintain duplicate merge gate documentation.

Quick Start

Use the final-approval skill when your dev loop reaches the final approval phase to automatically load the correct merge gate procedure and follow the human approval checkpoint steps.

Frequently Asked Questions about final-approval

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

FAQPage Schema
How do I enforce a human approval checkpoint before a pull request merge in an AI dev loop?▼

A human approval checkpoint before pull request merge is enforced by routing the dev loop to the canonical final approval procedure. This verifies CI status and resolves unresolved review threads before authorizing the merge.

What is a merge gate procedure in AI-driven software development?▼

A merge gate procedure is a formal checkpoint requiring human approval before a pull request merges. It standardizes CI verification and review thread resolution to eliminate confusion about official merge rules.

How do I route workflow execution to the correct final approval steps for a GitHub pull request?▼

Workflow execution routes to the correct final approval steps by using a narrowed read-set pointer that redirects to the Copilot PR Follow-up Skill, loading the official merge gate procedure automatically.

Does this final approval routing require maintaining separate merge gate documentation?▼

No, final approval routing eliminates the need for separate merge gate documentation by acting as a redirect pointer to the canonical Copilot PR Follow-up Skill, ensuring you always access up-to-date instructions.

What checks are required at the final approval phase before merging a pull request?▼

The final approval phase requires CI status verification, unresolved review thread resolution, and merge authorization checks to complete the standardized merge gate compliance for the dev loop.

Related Skills

Explore More Software Engineering Skills→
OrestesKOrestesK
2

iterate-pr

Diagnose GitHub pull request failures, apply validated fixes, and monitor checks.

Community
Advanced
coco-researchcoco-research
264

gsd-ship

Push a verified branch and create a merge-ready pull request.

Community
Advanced
mfittkomfittko
14

copilot-pr-followup

Automate GitHub PR follow-up tasks from Copilot review through gate checks.

Community
Advanced
mfittkomfittko
14

dev-loop

Automate GitHub issue-to-merged PR workflows through seven deterministic phases.

Community
Advanced