autoclosure

Automates PR closeout through task compliance checks, feedback resolution, proof replay, and GitHub delivery.

16.5k|997|Updated Dec 2, 2019
One-click install
npx skills add https://github.com/udecode/plate --skill autoclosure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autoclosure
Source: https://github.com/udecode/plate/tree/main/.agents/skills/autoclosure
Command: npx skills add https://github.com/udecode/plate --skill autoclosure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finishing an already-started pull request involves many easy-to-skip gates: verifying task-plan evidence, triaging live review feedback, rerunning proofs after every push, and posting verified receipts. This Skill enforces that entire closeout process so no PR is merged or closed without verifiable evidence.

Core Features & Use Cases

  • Task Compliance Gate: Verifies every PR carries an exact task-plan body line, that the plan exists at the PR head, and that it identifies the exact PR; noncompliant PRs receive a remediation comment and are closed with read-back receipts.
  • Live PR Feedback Gate: Fetches unfiltered top-level comments, review bodies, and all review threads via GitHub API and GraphQL, assigns P0-P3 priorities with rationale, and blocks delivery until every P1-or-higher finding is fixed, proven, and resolved.
  • Closure Matrix and Loop: Tracks per-lane proof status (source behavior, build, docs, registry, changeset, checks, delivery) and replays all P1 proofs after the final material push before posting a terminal receipt tied to the exact head OID.
  • Use Case: A reviewer left inline threads and top-level comments on your Plate PR. Invoke this Skill to triage each item by priority, fix and prove the blocking ones, rerun checks, and deliver the PR only after a verified zero-P1 read-back.

Quick Start

Ask the agent to run autoclosure on the current pull request to verify task evidence, resolve all review feedback, and complete GitHub delivery.

Frequently Asked Questions about autoclosure

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

FAQPage Schema
How do I finish and ship an open pull request with unresolved review feedback?

Run the autoclosure workflow on the PR. It fetches all top-level comments, review bodies, and inline threads, assigns each a P0-P3 priority, fixes and proves every P1-or-higher item, and blocks delivery until a fresh read-back shows zero unresolved blocking findings.

What happens when a pull request has no task plan evidence?

The compliance gate checks the PR body for an exact task-plan line, confirms the plan file exists at the fetched PR head, and verifies it names the exact PR. If any check fails, the workflow posts a remediation comment, verifies it, closes the PR, and stops.

Does autoclosure work with GitHub pull request review threads?

Yes. It fetches inline review threads through GitHub GraphQL cursor pagination without filtering resolved or outdated states, plus unfiltered top-level comments and review bodies through the REST API, so no feedback item is silently skipped.

When should I use autoclosure instead of starting a new task?

Use it when implementation already exists and only verification, review, checks, or delivery remain. If substantial implementation is still needed, start a dedicated task first, because autoclosure never invents new product scope or replaces per-PR task ownership.

Why does delivery stay blocked after all review threads are resolved?

Resolved threads do not prove fixes survived later edits. The workflow replays every recorded P1-or-higher proof after the final material branch push and requires a terminal receipt whose OID matches the live head, fetched ref, and local commit.