dev-pr-open

Pushes committed branches and opens draft pull requests on GitHub.

154|57|Updated Feb 7, 2020
One-click install
npx skills add https://github.com/FHIR/fhir-codegen --skill dev-pr-open-fhir
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-pr-open
Source: https://github.com/FHIR/fhir-codegen/tree/main/.github/skills/dev-pr-open
Command: npx skills add https://github.com/FHIR/fhir-codegen --skill dev-pr-open-fhir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning finished local commits into a properly scoped pull request is error-prone: wrong branches get pushed, issues are left unreferenced, changelog entries are forgotten, and re-runs create duplicate PRs. This Skill acts as a release engineer that validates the repository state, resolves the exact commit scope, and publishes the branch and PR safely. ## Core Features & Use Cases - Dual scope modes: Slot mode publishes one work slot's commits resolved from its plan.md; branch mode (the default) publishes every commit ahead of the default branch, grouped by discovered slot. - Safety gates before any mutation: Verifies GitHub integration is enabled in AGENTS.md, gh CLI authentication, remote owner/repo cross-check, clean index, and that HEAD is not the default branch. - Changelog management: Detects or records the changelog location, dedupes entries by stable anchors, and makes exactly one path-limited docs(changelog) commit with approval. - Idempotent PR handling: Updates an existing open PR in place instead of creating duplicates, assembles the body with one Closes #N line per bound issue, and always opens as a draft. - Use Case: After finishing several slots of work on a feature branch, ask the Skill to publish everything; it echoes the commit list, drafts changelog entries and the PR body for approval, pushes the branch, and opens a draft PR closing all bound issues. ## Quick Start Publish all my local commits as a draft pull request, adding changelog entries and closing every bound issue.

Frequently Asked Questions about dev-pr-open

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

FAQPage Schema
How do I open a pull request for local commits with the GitHub CLI?▼

Authenticate gh, push the branch with git push -u origin HEAD, then run gh pr create with --repo, --base, --head, --title, and --body-file. This Skill automates that flow, including scope resolution, changelog entries, and draft creation.

How do I close multiple GitHub issues from one pull request?▼

Add one Closes #N line per issue in the PR body, each on its own line, so merging closes all of them. The Skill collects the union of Issue trailers and slot bindings and never collapses several issues into a single line.

Can this Skill push or create a PR without enabling anything?▼

No. It is opt-in and off by default: the repository's AGENTS.md must contain a GitHub Integration section with Enabled set to yes. Otherwise it offers to enable the integration and stops cleanly if declined.

What happens if I re-run the PR open workflow after a failed push?▼

The Skill is idempotent: it excludes its own docs(changelog) commits from the branch scope, dedupes changelog entries by stable anchors, and updates an existing open PR in place rather than creating a second one.

Why does the Skill refuse to run on the default branch?▼

Publishing from the default branch is a hard fail because the PR would have no meaningful diff base. It never creates a branch on the user's behalf; the remedy is to create a branch at HEAD yourself and re-run.

Does it ever force-push or merge the pull request?▼

Never. It uses only git push -u origin HEAD with no force variants, never merges the PR, never closes issues directly, and never takes the PR out of draft.