skills.rest
Nebulavenus
NebulavenusCOMMUNITY
Explore all skills by this author →
GitHub

dev-create-pr

Create a pull request from uncommitted Git changes with local review and lint checks.

36|6|Updated Mar 25, 2026
Search Tags:#automation#git#workflow#commit#branch#code-review#pull-request
One-click install
npx skills add https://github.com/Nebulavenus/forge-gpu --skill dev-create-pr-nebulavenus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-create-pr
Source: https://github.com/Nebulavenus/forge-gpu/tree/main/.claude/skills/dev-create-pr
Command: npx skills add https://github.com/Nebulavenus/forge-gpu --skill dev-create-pr-nebulavenus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Examines the working tree, identifies relevant changes, and automatically produces a branch, commit, and pull request with a descriptive message.

Core Features & Use Cases

  • Phase 1 — Survey the working tree
  • Phase 2 — Classify changes by relevance
  • Phase 3 — Create a branch (if needed)
  • Phase 4 — Stage, review, and local checks with /dev-local-review
  • Phase 5 — Compose the commit message
  • Phase 6 — Push to the remote and prepare for PR
  • Phase 7 — Create the pull request via gh pr
  • Safety checks: mandatory local review, linting, and type checks before commit

Quick Start

Run the skill to examine uncommitted changes, create a branch if needed, commit with a descriptive message, and open a pull request.

Frequently Asked Questions about dev-create-pr

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

FAQPage Schema
How do I automate pull request creation from uncommitted code changes?▼

Automating pull request creation involves examining your working tree, classifying changes, creating a branch if on main, staging, and committing with a descriptive message before pushing to open a review-ready pull request.

What is a safe workflow for creating a Git branch and pull request for feature work?▼

A safe workflow for creating a Git branch enforces mandatory local code review, linting, and type checks before committing, ensuring your feature work is auditable and review-ready before opening a pull request.

How do I stage and commit changes with an automatically generated descriptive message?▼

To stage and commit changes with a descriptive message, the workflow surveys your working tree, stages relevant code, composes an automated commit message based on the changes, and prepares the push to your remote repository.

Can I create a pull request using gh pr directly from my current working tree?▼

Yes, you can create a pull request using gh pr directly from your working tree by automatically staging classified changes, committing them with a descriptive message, and executing the push and PR creation steps.

What are the steps to turn scattered code changes into a review-ready pull request?▼

Turning scattered code changes into a review-ready pull request requires surveying the working tree, classifying changes by relevance, creating a branch, staging, running local checks, composing a commit message, and pushing to create the PR.

Related Skills

Explore More Software Engineering Skills→
agentclashagentclash
25

git-rules

Validate git commit hygiene and working tree status post-commit.

Official
Basic
JacobPEvansJacobPEvans
3

rebase-pr

Rebase pull requests onto main with signed commits and GitHub API checks.

Community
Advanced
marcioaltoemarcioaltoe
14

project-workflow

Automate Bun and TypeScript pre-commit quality gates with specified commands.

Community
Intermediate
simpleapps-comsimpleapps-com

conventional-commits

Enforce Conventional Commits v1.0.0 formatting for Git commit messages.

Official
Basic