om-open-pr

Commits, pushes, and opens or reuses a labeled pull request for autonomous pipeline runs.

1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/tkogut/agents-os-core --skill om-open-pr-tkogut
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: om-open-pr
Source: https://github.com/tkogut/agents-os-core/tree/main/global_skills/om-open-pr
Command: npx skills add https://github.com/tkogut/agents-os-core --skill om-open-pr-tkogut

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Autonomous agent pipelines finish code changes but leave the final shipping step — committing, pushing, opening the PR, applying labels, and releasing issue locks — inconsistent or manual. This Skill standardizes that final step so every automated run ends with a ready-for-review PR and a clean tracker state. ## Core Features & Use Cases - Duplicate-safe PR opening: Detects and reuses an existing PR for the branch or issue instead of opening a second one, refreshing its body and labels. - Full SDLC label normalization: Applies the review, category, QA, priority, and risk labels through guarded tracker operations, with one consolidated rationale comment. - Lock handoff and release: Transfers the in-progress lock to the PR for chained runs and always releases the issue lock, even on failure. - Use Case: An autofix chain (verify → root-cause → fix) finishes editing files; this Skill commits the work, pushes the branch, opens a ready PR against the configured base branch, labels it, and emits the PR: reference line so the review skill can continue. ## Quick Start Ask the agent to run om-open-pr on the current branch to commit the pending changes, push them, and open a labeled pull request against the configured base branch.

Frequently Asked Questions about om-open-pr

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

FAQPage Schema
How do I open a pull request from an autonomous agent pipeline?▼

Invoke om-open-pr after the fixing step has edited and validated files. It commits the changes, pushes the branch, opens a ready-for-review PR against the configured base branch, applies the label set, and emits a PR reference line for the next skill.

How does the skill avoid creating duplicate pull requests?▼

Before opening anything, it searches for an existing PR for the head branch or one referencing the issue. If found, it reuses that PR by pushing updates and refreshing its body and labels instead of opening a second one.

Can I open a draft pull request instead of a ready one?▼

Yes, pass the --draft flag for explicitly incomplete work such as spec-only design PRs or interrupted runs. By default every completed autonomous run opens the PR as ready for review.

What happens to the issue lock if the PR opening fails?▼

The issue lock is always released, even on failure paths like no changes, push errors, or PR creation failure. The skill treats lock release as a finally-block so a crash still clears the in-progress label.

Which labels does the skill apply to a new pull request?▼

It applies the review pipeline label, the category label, a QA label (needs-qa or skip-qa, never both), exactly one priority label, and exactly one risk label, all through guarded tracker operations with one consolidated rationale comment.