new-branch-and-pr

Creates a fresh branch, commits changes, and opens a pull request.

3|Updated Apr 8, 2025
One-click install
npx skills add https://github.com/ZanzyTHEbar/dragonarchy --skill new-branch-and-pr-zanzythebar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-branch-and-pr
Source: https://github.com/ZanzyTHEbar/dragonarchy/tree/main/packages/opencode/.config/opencode/skills/new-branch-and-pr
Command: npx skills add https://github.com/ZanzyTHEbar/dragonarchy --skill new-branch-and-pr-zanzythebar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It removes the manual overhead of setting up a clean branch, committing focused changes, and opening a pull request when starting work that should ship through a standard review workflow. ## Core Features & Use Cases - Branch Creation: Derives the repository's default branch and creates a descriptive branch from its latest state. - Conventional Commits: Commits focused changes using Conventional Commit messages. - PR Automation: Pushes the branch and opens a concise pull request with summary and test notes. - Use Case: You ask the agent to fix a bug and ship it for review; it creates a branch, commits the fix, and returns a PR URL with verification notes. ## Quick Start Ask the agent to create a new branch for your change and open a pull request with a summary and test notes.

Frequently Asked Questions about new-branch-and-pr

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

FAQPage Schema
How do I create a branch and open a pull request automatically?

Ask the agent to start work on a clean branch and open a PR. It derives the default branch, creates a descriptive branch from its latest state, commits with a Conventional Commit message, pushes, and returns the PR URL.

What commit message format does the branch and PR workflow use?

It uses Conventional Commit messages for focused changes. Each branch is kept scoped to a single change set, and the PR includes a summary plus test notes for reviewers.

Does it commit or push without my approval?

No. The guardrails explicitly prohibit committing, pushing, force-pushing, or creating a PR without explicit user approval, and unrelated user or agent changes are preserved.

Can it handle repositories using jj instead of standard git?

Yes, if the repository uses jj and a different local workflow is documented, the skill follows that documented workflow instead of the default branch-from-default-branch behavior.

What happens if a branch or PR already exists for the change?

The skill deduplicates by branch before creating a PR and derives repository, remote, and base branch values dynamically, avoiding duplicate pull requests for the same work.