do-pr

Create GitHub pull requests after branch safety, test, and CI checks.

11|Updated Dec 28, 2024
One-click install
npx skills add https://github.com/wadvanced/aurora_uix --skill do-pr-wadvanced
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: do-pr
Source: https://github.com/wadvanced/aurora_uix/tree/main/.claude/skills/do-pr
Command: npx skills add https://github.com/wadvanced/aurora_uix --skill do-pr-wadvanced

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents broken or poorly formatted pull requests by enforcing branch safety rules, running a quality gate, and ensuring tests pass before pushing and opening the PR.

Core Features & Use Cases

  • Automated pre-merge safety checks: Ensures the branch is not main, Chromedriver is configured for headless mode, and the working tree is clean.
  • Quality gate enforcement: Runs the gate skill and blocks PR creation if unresolved errors remain.
  • Test-first workflow with guarded push and PR creation: Runs mix test, pushes the branch to the remote, generates a conventional PR title from the branch name, and creates the PR with a structured body including a test plan.

Quick Start

Use this skill to create a pull request for your current branch by running it and letting it complete all checks, tests, push, and PR creation steps.

Frequently Asked Questions about do-pr

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

FAQPage Schema
How do I create a GitHub pull request that automatically runs tests and checks before pushing?

To safely open a pull request, you can use an automated workflow that verifies branch safety, runs local tests like mix test, enforces a CI quality gate, and then pushes your code to create the PR. This prevents broken code from being submitted.

What pre-merge checks are needed before pushing a branch to GitHub?

Essential pre-merge checks include ensuring you are not on the main branch, confirming the working tree is clean, configuring Chromedriver for headless mode, and running a quality gate to block submissions with unresolved errors.

Do I need to run mix test before creating a pull request?

Yes, running mix test is required in a test-first workflow. The process executes mix test with failure reporting to ensure all tests pass before it pushes the branch and opens the pull request against the base main branch.

How is the pull request title generated from a git branch?

The pull request title is derived automatically from the git branch name and history. This ensures a conventional PR title and structured body, which includes a defined test plan, are created without manual formatting.

Can I force push git changes when opening a pull request through an automated gate?

No, the push operation is performed without force flags to ensure branch safety. The automated workflow enforces deterministic preconditions and quality gating before using gh pr create against base main.