pr

Create GitHub Pull Requests from commits, test results, and QA status.

Updated Apr 30, 2025
One-click install
npx skills add https://github.com/a-tabiji/atima-lp --skill pr-a-tabiji
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/a-tabiji/atima-lp/tree/main/.claude/skills/pr
Command: npx skills add https://github.com/a-tabiji/atima-lp --skill pr-a-tabiji

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of GitHub Pull Requests by consolidating code changes, test results, and quality gate status into a single PR, reducing manual overhead and ensuring traceability.

Core Features & Use Cases

  • Automatically assemble PR titles and bodies from commits and issue references.
  • Enforce quality-gate PASS before PR creation and require commits are present.
  • Suitable for branch-based workflows and linking PRs to issues or tasks.

Quick Start

Provide an issue number (optional) and run the PR workflow to create a QA-verified pull request.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I automate GitHub pull request creation with a quality gate check?

To automate GitHub pull request creation with a quality gate check, use a branch-based workflow that enforces a PASS status from your QA gate and requires commits to be present before creating the PR.

Can I link a GitHub pull request to an existing issue automatically?

Yes, you can link a GitHub pull request to an existing issue automatically by providing the issue number, which consolidates code changes and task references into a single traceable PR.

How does a quality gate prevent pull requests from being created?

A quality gate prevents pull request creation by enforcing that the gate status is PASS, blocking PR assembly if commits are missing or if tests fail before using the GitHub CLI.

What is needed to assemble a pull request body from commits?

To assemble a pull request body from commits, you need a branch-based workflow with existing commits and an optional issue number to consolidate changes and test results automatically.

Does this pull request automation work with the GitHub CLI?

Yes, this pull request automation works with the GitHub CLI and Git commands to consolidate changes, enforce QA status, and create the PR directly within your branch-based workflow.

Why does my automated pull request fail to create when commits are missing?

Your automated pull request fails to create when commits are missing because the workflow strictly enforces that commits are present and the quality gate returns a PASS status before proceeding.