skills.rest
fallow-rs
fallow-rsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

open-draft-pr

Commits, pushes, and opens a ready pull request for local changes on GitHub.

4.4k|154|Updated Mar 17, 2026
Search Tags:#Git#Conventional Commits#gh CLI#gitHub#signed commits#Code review#Pull request
One-click install
npx skills add https://github.com/fallow-rs/fallow --skill open-draft-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: open-draft-pr
Source: https://github.com/fallow-rs/fallow/tree/main/.agents/skills/open-draft-pr
Command: npx skills add https://github.com/fallow-rs/fallow --skill open-draft-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turning local changes into a reviewable pull request involves several error-prone steps: scoping the change, running validation, writing a conventional commit, pushing the branch, and drafting a clear PR description. This Skill standardizes that entire workflow for the fallow repository so nothing is skipped.

Core Features & Use Cases

  • Structured PR Workflow: Reviews changed files, runs the smallest relevant validation, commits with signing, pushes the branch, and opens a ready-for-review PR via the GitHub CLI.
  • Conventional Commits and Branch Naming: Enforces conventional commit messages and descriptive branch names like feat/<slug>, fix/<slug>, or refactor/<slug>.
  • Use Case: After fixing a bug in the fallow analyzer, ask the assistant to publish the work; it validates the touched area, creates a signed conventional commit on a fix/<slug> branch, pushes it, and opens a ready PR with a high-signal title and body.

Quick Start

Commit my current changes with a conventional message, push the branch, and open a ready pull request on GitHub.

Frequently Asked Questions about open-draft-pr

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

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

Review the changed files, run relevant validation, create a signed conventional commit, push the branch, then run gh pr create with a descriptive title and body. This Skill automates that exact sequence for the fallow repository.

How to write conventional commit messages for a pull request?▼

Use a type prefix like feat, fix, refactor, docs, or chore followed by a concise summary, and mirror that convention in the branch name such as feat/<slug>. The Skill prepares the commit message and PR title following these rules.

Does this Skill create draft pull requests?▼

No. Despite its historical name, PRs are opened as ready for review by default. A draft PR is only created when the user explicitly asks for one by passing --draft to gh pr create.

Can I use signed commits when opening a PR?▼

Yes, signed commits are a requirement of this workflow. When committing is requested, the Skill commits with signing enabled before pushing the branch and opening the pull request.

What happens if validation checks are not run before the PR?▼

The Skill runs the smallest relevant validation for the touched area, but if some checks are skipped it summarizes that honestly in the PR rather than claiming full validation coverage.

Related Skills

Explore More Software Engineering Skills→
olliecrowolliecrow

git-commit

Commit all uncommitted changes into small, logical commits with clear messages.

Community
Advanced
HybridAIOneHybridAIOne
126

github-pr-workflow

Manage GitHub pull request workflows from branch creation to CI-verified merge.

Official
Intermediate
Open-PawsOpen-Paws
3

code-review

Automate layered code review for pull requests in CI pipelines.

Official
Advanced
vercelvercel
142.0k

gh-stack

Manage stacked pull requests and dependent branches using the gh-stack CLI extension.

Official
Advanced