om-auto-create-pr-loop

Implements multi-step specs as one commit per step and opens a labeled pull request.

2.6k|159|Updated Mar 8, 2021
One-click install
npx skills add https://github.com/go-musicfox/go-musicfox --skill om-auto-create-pr-loop-go-musicfox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: om-auto-create-pr-loop
Source: https://github.com/go-musicfox/go-musicfox/tree/main/.agents/skills/om-auto-create-pr-loop
Command: npx skills add https://github.com/go-musicfox/go-musicfox --skill om-auto-create-pr-loop-go-musicfox

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Long, multi-step spec implementations are hard to run autonomously: work loses track of progress, verification gets skipped, and interrupted runs cannot be resumed. This Skill turns a free-form brief into a tracked execution plan, lands one lean commit per step in an isolated worktree, batches verification at checkpoints, and opens a labeled draft PR that stays resumable end to end. ## Core Features & Use Cases - Run folder with resumable state: Every run writes PLAN.md (authoritative Tasks table), HANDOFF.md, and NOTIFY.md so a companion skill can resume an interrupted run from the first unfinished step. - Checkpoint and final-gate verification: Every ~5 steps a checkpoint runs targeted validation, integration tests, and UI screenshots, posting evidence to the PR; a final gate runs the full validation suite before the PR flips from draft to ready. - Executor dispatch and review loop: Steps marked dispatch or group run in sequential executor subagents with model tiers, and a single om-auto-review-pr autofix pass lands review fixes as new commits before the summary. - Use Case: Paste a multi-phase feature brief and receive a draft PR that grows commit by commit, with checkpoint evidence comments, full labels, a comprehensive summary, and a ready-for-review flip at completion. ## Quick Start Ask the agent to run om-auto-create-pr-loop with a brief describing the feature or fix you want implemented as a tracked pull request.

Frequently Asked Questions about om-auto-create-pr-loop

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

FAQPage Schema
How do I turn a feature brief into a pull request automatically?

Run om-auto-create-pr-loop with a free-form brief describing the task. It classifies the run, drafts a plan with a Tasks table, implements one commit per step in an isolated worktree, and opens a labeled draft PR that flips to ready when the final gate passes.

How do I resume an interrupted autonomous PR run?

Resume with the companion skill om-auto-continue-pr-loop followed by the PR number. It parses the run folder's PLAN.md Tasks table and HANDOFF.md to find the first unfinished step and continues from there.

When should I use om-auto-create-pr instead of the loop variant?

Use plain om-auto-create-pr for small fixes such as typos, dependency bumps, or single-file changes. The loop variant is for spec-driven, multi-phase work with three or more commits that needs run-folder tracking and checkpoint verification.

Does the skill run tests before marking a PR ready?

Yes. Checkpoints run targeted validation and focused integration tests roughly every five steps, and the final gate runs the full validation command list plus the full integration suite before the draft PR is promoted to ready.

What happens if two agents try to work on the same PR?

A three-signal lock (assignee, in-progress label, claim comment) prevents duplicate work. A conflicting claim stops the run unless the lock is stale or --force is passed with an explicit override comment.