maintainer

Guides human maintainers through approving, deciding, and answering human-required tasks in GitHub workflows.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/volter-ai/open-autonomy-compiler --skill maintainer-volter-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: maintainer
Source: https://github.com/volter-ai/open-autonomy-compiler/tree/main/.claude/skills/maintainer
Command: npx skills add https://github.com/volter-ai/open-autonomy-compiler --skill maintainer-volter-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an autonomous agent organization hits work it is not authorized to complete — a sensitive PR, an out-of-scope decision, or a missing clarification — it needs a defined way to hand that work to a person and wait for an explicit resolution. This Skill is the task spec handed to the human maintainer, explaining what is being asked and how to resolve it so the automated flow resumes. ## Core Features & Use Cases - Human-approval gating: Explains how to authorize a human-required PR via a native GitHub Approve or an exact-SHA /agent approve <full-head-sha> comment, which the human-approval gate verifies per commit. - Typed decision handling: Covers the four engagement types — approve, decide, answer, and inform — with the exact /agent decide and /agent answer commands that record results and clear blocked states. - Use Case: A PR touches workflow files listed in policy.risk.human_required_paths, so the org assigns it to you and parks the merge. You review the diff, then comment /agent approve <current-head-sha>; the gate verifies your authorization and the PR proceeds once ci, security, and agent-review are also green. ## Quick Start Open your GitHub worklist with the query is:open assignee:@me label:human-required, review the assigned item, and resolve it with a native Approve or the appropriate /agent command described in this Skill.

Frequently Asked Questions about maintainer

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

FAQPage Schema
How do I approve a human-required PR in a GitHub agent workflow?▼

Approve the PR natively on GitHub, or comment /agent approve followed by the full current head SHA when GitHub forbids a self-review. The human-approval gate permission-checks the authorization per commit, so you must repeat it after any new push.

How do I find tasks waiting on a human maintainer?▼

Your live worklist is a standard GitHub search: is:open assignee:@me label:human-required, plus label:needs-info for clarification requests. The org assigns items to you and requests your review, and escalation comments re-ping you after the configured SLA.

What triggers human-required scope for a pull request?▼

A PR enters human-required scope when it touches a path declared in policy.risk.human_required_paths — such as workflows, autonomy.yml, the constitution, skills, bun.lock, or boundary gate scripts — or when it carries the human-required label.

Can the automated flow resume without an explicit human action?▼

No. The org never infers completion from timers or notifications. The flow resumes only on an explicit authorized act: a native Approve, an exact-SHA /agent approve comment, or a /agent decide or /agent answer command from an OWNER, MEMBER, or COLLABORATOR.

Does a human approval replace CI and agent review checks?▼

No. Human authorization is an additional gate, not a replacement. A human-required PR still needs ci, security, and the independent agent-review to pass before GitHub native auto-merge can land it.