pr-from-issue

Create a GitHub pull request from a completed issue after passing mix test.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams reliably turn a completed GitHub issue into a ready-to-merge pull request by enforcing branch, test, and cleanliness checks before any PR is created.

Core Features & Use Cases

  • Issue completion enforcement: Reads the issue body and only proceeds when it contains the exact phrase indicating it is ready to be closed.
  • Pre-PR guardrails: Blocks PR creation from the main branch, ensures test configuration has Wallaby/Chromedriver headless enabled, and stops on any uncommitted changes.
  • Quality gate execution: Runs the full test suite with mix test and fails fast if tests do not pass.
  • PR automation from git history: Pushes the feature branch to origin, generates a conventional-style PR title from the branch name, and builds the PR body from commit messages while referencing the issue to close it.

Quick Start

Run this skill after you’ve finished the work for an issue, marked it with the required completion phrase in the issue description, committed your changes with conventional commit messages, and verified tests locally.

Frequently Asked Questions about pr-from-issue

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

FAQPage Schema
How do I automatically create a GitHub pull request from a completed issue?

To create a pull request from a completed issue, the Skill reads the issue body via GitHub CLI, validates the completion phrase, runs mix test, pushes the branch, and generates a conventional commit PR title and body that closes the issue.

Can I open a pull request directly from the main branch?

No, you cannot open a pull request from the main branch. The Skill enforces pre-PR guardrails by blocking PR creation from main, ensuring you are working from a dedicated feature branch before pushing and opening the request.

How do I ensure CI tests pass before opening a PR from an issue?

To ensure CI tests pass before opening a PR, the Skill executes a full quality gate by running mix test and fails fast if any tests do not pass, preventing the branch from being pushed to origin until tests succeed.

Does this PR automation tool support Wallaby Chromedriver headless configuration?

Yes, the PR automation tool supports Wallaby Chromedriver by checking and updating config/test.exs to set chromedriver headless to true if needed, ensuring the test suite runs correctly in a headless environment before creating the PR.

What is the best way to generate a PR title and body from conventional commit messages?

The best way to generate a PR title and body from conventional commit messages is to use git history automation that derives the PR title from the branch name and builds the PR body from commit messages while referencing the issue to close.

Why does my issue to PR workflow fail on uncommitted git changes?

Your issue to PR workflow fails on uncommitted git changes because the Skill enforces a clean git state as a pre-PR guardrail, stopping the process immediately if it detects any uncommitted changes before running tests or pushing the branch.