pr

Run build and test commands, then create a GitHub pull request.

11|1|Updated May 15, 2026
One-click install
npx skills add https://github.com/usk6666/yorishiro-proxy --skill pr-usk6666
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/usk6666/yorishiro-proxy/tree/main/.claude/skills/pr
Command: npx skills add https://github.com/usk6666/yorishiro-proxy --skill pr-usk6666

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of creating a GitHub Pull Request, ensuring that code is built and tested successfully before submission.

Core Features & Use Cases

  • Automated Build & Test: Runs make build and make test to verify code integrity.
  • Change Verification: Displays git diff for review.
  • Conventional Commits: Generates PR titles in the feat(scope): description format.
  • Automated PR Creation: Uses gh pr create with generated title and body.

Quick Start

Use the pr skill to create a pull request for your changes.

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 after build and test?

You can automate GitHub pull request creation by running build and test commands to verify code integrity, then generating a conventional commit-style title and summary body to execute `gh pr create` automatically.

Can I generate conventional commit-style PR titles automatically from git diff?

Yes, conventional commit-style PR titles in the `feat(scope): description` format can be generated automatically by verifying `git diff` changes and summarizing them before executing the pull request creation command.

Does this PR automation tool run make build and make test before creating a pull request?

Yes, this PR automation tool runs `make build` and `make test` to verify code integrity and displays `git diff` for review before automating the pull request creation process.

What is the best way to streamline a GitHub contribution workflow with CI/CD automation?

The best way to streamline a GitHub contribution workflow is to automate code integrity checks using build and test commands, generate conventional commit titles, and execute `gh pr create` for automated pull request submission.

Do I need the GitHub CLI installed to automate pull request creation?

Yes, you need the GitHub CLI installed because the automation process executes the `gh pr create` command to submit the pull request with a generated title and body after build and test verification.

What happens if my code fails build or test verification during pull request automation?

If code fails build or test verification, the pull request automation process halts to ensure code integrity, preventing the generation of a conventional commit title and the execution of `gh pr create`.