Orchestrates autonomous agent fleets by triaging GitHub issues, PRs, and running workers.
npx skills add https://github.com/volter-ai/open-autonomy-compiler --skill pm-volter-ai
Please help me install this Agent Skill. Skill: pm Source: https://github.com/volter-ai/open-autonomy-compiler/tree/main/.claude/skills/pm Command: npx skills add https://github.com/volter-ai/open-autonomy-compiler --skill pm-volter-ai
oa-rework marker comments, and cancels stuck or runaway runs through the Runner. - Dangling PR reaping and human escalation: Closes stale PRs whose issues are already closed, assigns and @mentions maintainers or requesters on blocked items, and re-pings them on a configurable SLA. - Use Case: On a scheduled sweep, the orchestrator finds an issue whose PR has green checks but a merge conflict, relaunches develop to rebuild it on fresh main, and escalates a 26-hour-old human-required item to the maintainer. ## Quick Start Ask the agent to sweep the repository board: review every open issue, PR, and running worker, then take the appropriate orchestration action on each.High-intent search queries and answers about installing and using this skill.
Use an orchestrator sweep that reads every open issue's full history, every open PR's checks and merge state, and every in-flight worker via the Runner, then takes exactly one action per item such as launching develop, commenting status, or escalating to a human.
Check the Runner's in-flight list for a develop session whose ref matches the issue number, including proposing states, and verify no PR exists on the agent/issue-<n> branch in any state before launching a new run.
A PR with mergeStateStatus DIRTY will never auto-merge even with all checks green. The orchestrator relaunches develop to rebuild the change onto fresh main, or closes the issue if the work is obsolete, while respecting the rework cap.
The orchestrator counts its own oa-rework marker comments on the issue against max_develop_attempts from autonomy.yml, defaulting to 2. At or above the cap it stops relaunching, labels the issue human-required, and escalates to a maintainer.
No. The permission split gives it no contents:write access, so it cannot merge or edit code. It can only comment, label, assign, launch or cancel runs, and close dangling PRs whose issues are already closed.
Blocked items get assigned to the maintainer or issue author with one @mention. If no human replies within policy.human.sla_minutes, default 24 hours, a single escalation re-ping is posted per SLA window, never every sweep.
QuintenpsExtract scoped GitHub tokens for isolated personal and enterprise authentication contexts.
Fu-JieMerge release PRs into main and close linked issues automatically.
AurelioloOrchestrate multi-agent pull request reviews with code analysis and issue verification.
eric-sabeManage GitHub Issues and ProjectV2 boards via gh CLI and GraphQL.