mcpField
C
create-draft-pr

create-draft-pr

github.com/jnsahajDevelopment106105 installsUpdated 3w ago
Repository

About create-draft-pr

A skill for preparing and opening a draft pull request from current changes. It guides agents through reviewing the diff, committing and pushing a branch, then writing a focused PR description.

Key features

  1. 01Review status, diff, and commit history
  2. 02Create a branch when starting on main
  3. 03Commit and push changes
  4. 04Draft a PR description
  5. 05Open a draft PR with GitHub CLI

Use cases

  1. 01Turn completed changes into a draft PR
  2. 02Ensure a PR description follows a consistent structure

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/jnsahaj/skills --skill create-draft-pr

After installing, type/create-draft-prin Claude Code to confirm it loaded.

Details

From the project README

Create Draft PR

Commit all changes, push to remote, and create a draft pull request with a focused generated description.

Steps

  1. Run git status to see changes
  2. Run git diff to understand what changed
  3. Run git log to see commit message style
  4. If on main, create a new branch in the format <initials>/<feature> or the project's branch naming convention, then switch to it
  5. Stage and commit changes with a concise message
  6. Push branch to remote with -u flag
  7. Generate the PR description using the pr-description skill's description format.
  8. If the change is user-facing, workflow-oriented, or architectural, include a concise UX flow section using the ux-flow-plan style.
  9. Create draft PR using gh pr create --draft
  10. If you created the branch (were on main), switch back to main after the PR is created

PR Body Format

Use the pr-description skill's format as the base:

## Summary

<One sentence describing the overall change>

- Additional note if needed
- Another note if needed

## Problem

Describe the issue being addressed. What was broken, missing, or suboptimal? Be specific about the root cause.

## Solution

Explain the approach taken to fix the problem. Include code snippets only when they clarify the core approach.

When relevant, add this section between Problem and Solution:

## UX Flow

```text
Current flow
└─ ...

Desired flow
└─ ...
```

Only include UX Flow when it helps explain the product behavior, user journey, or architecture boundary. Keep it short and use the ux-flow-plan tree style.

Rules

  • PR title should be succinct (no "feat:" prefix, but "fix:" is ok for bug fixes)
  • Use pr-description as the source of truth for PR body structure.
  • Include UX Flow from ux-flow-plan only when relevant; omit it for mechanical, dependency, or tiny internal changes.
  • Do NOT include a file-by-file summary of code changes.
  • Do NOT include a test plan with checkboxes.
  • Do NOT include "Generated with Claude Code" or similar footers
  • Keep the PR description concise and focused on intent and approach
  • Use HEREDOC for the PR body to preserve formatting

Comments

Markdown supported