dev-as-pr

Create a branch, empty commit, and draft pull request for feature work.

11|1|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/Takazudo/claude-resources --skill dev-as-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-as-pr
Source: https://github.com/Takazudo/claude-resources/tree/main/skills/dev-as-pr
Command: npx skills add https://github.com/Takazudo/claude-resources --skill dev-as-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Start a development workflow by creating a branch, an empty start commit, pushing to origin, and opening a draft PR to begin implementation.

Core Features & Use Cases

  • Automates branch creation from a target base or current branch.
  • Creates an empty start commit and pushes the branch to remote.
  • Opens a draft PR to kick off implementation and capture initial scope for review.

Quick Start

Create a branch from the target base or current branch, push it to origin, and open a draft PR to begin implementation.

Frequently Asked Questions about dev-as-pr

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

FAQPage Schema
How do I start a feature by opening a draft PR before writing code?

This workflow creates a new branch from your current base, pushes an empty initial commit to origin, and opens a draft pull request to establish the PR-first development cycle.

What is a PR-first workflow and how does an empty commit help?

A PR-first workflow opens a draft PR immediately to define scope and enable early review. Creating an empty initial commit allows pushing the branch and opening the PR before any feature code is written.

Do I need Git and GitHub CLI installed to automate opening a draft PR?

Yes, automating this draft PR workflow requires Git and GitHub CLI access to the repository. The process reads issue descriptions to seed branch names and PR metadata directly through these tools.

Can I automatically link a GitHub issue to a newly created branch and draft PR?

Yes, when issue references are provided, the workflow attaches them to the draft PR. It reads the issue descriptions to derive branch names and seed PR metadata automatically.

What's the best way to automate branch creation and push to origin for a new feature?

The best way is using an automated workflow that handles branch creation from a target base, creates an empty start commit, and pushes the branch to remote origin to kick off implementation.