om-open-pr

Commits, pushes, and opens labeled pull requests for autonomous agent pipelines.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Autonomous coding pipelines often finish their work but leave the final shipping step — committing, pushing, opening the pull request, applying labels, and releasing issue locks — inconsistent or manual. This Skill standardizes that final step so every automated run ends with a properly opened, labeled, and traceable pull request. ## Core Features & Use Cases - Commit, push, and open or reuse PRs: Detects existing PRs for the branch or issue and reuses them instead of creating duplicates, opening ready-for-review PRs against the configured base branch. - Full SDLC label normalization: Applies review, category, QA, priority, and risk labels through guarded tracker operations, with a single consolidated label-rationale comment. - Lock handoff and issue handback: Transfers the in-progress lock to the PR for chained runs, hands issues back to their authors, and always releases locks even on failure. - Use Case: After an automated bug-fix run edits files and passes validation, invoke this Skill to commit the changes, open a PR titled fix(auth): resolve token refresh race (#42), apply the label set, and emit the PR: reference line for the next pipeline step. ## Quick Start Ask the agent to run the om-open-pr skill with the issue number and category to commit the current branch, open a labeled pull request, and release the issue lock.

Frequently Asked Questions about om-open-pr

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

FAQPage Schema
How do I automatically open a pull request after an automated code fix?

Run this Skill after the fixing step completes: it commits staged changes, pushes the branch, and opens a ready-for-review PR against the configured base branch. It fills the body from the previous step's summary and applies the full label set.

How does the skill avoid creating duplicate pull requests?

Before opening anything, it searches for existing PRs by head branch and, in issue-driven runs, by issue reference. If one exists, it reuses that PR by pushing updates and refreshing its body and labels instead of opening a second one.

What labels does the skill apply to a new pull request?

It applies the review pipeline label, a category label such as bug or feature, exactly one priority label, exactly one risk label, and either needs-qa or skip-qa. All mutations go through guarded tracker operations, and one consolidated rationale comment explains the set.

Does the skill release issue locks if the PR opening fails?

Yes. The issue lock release is treated as a finally-block: even when there are no changes, the push fails, or PR creation fails, the in-progress label is removed and the issue is handed back to its author.

When should a pull request be opened as a draft instead of ready?

Draft is reserved for explicitly incomplete work, such as spec-only design PRs or interrupted runs, using the --draft flag. Completed autonomous runs always open ready-for-review PRs by default.