pr

Creates or updates GitHub pull requests and monitors CI checks until completion.

1|Updated May 4, 2026
One-click install
npx skills add https://github.com/wesbragagt/nixos-config --skill pr-wesbragagt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/wesbragagt/nixos-config/tree/main/home/skills/pr
Command: npx skills add https://github.com/wesbragagt/nixos-config --skill pr-wesbragagt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Opening and maintaining a pull request involves repetitive steps: committing pending changes, pushing the branch, writing a clear title and body, and then waiting on CI. This Skill automates that entire flow and reports check failures with the exact error line and a proposed fix. ## Core Features & Use Cases - End-to-end PR workflow: Commits pending changes via the /commit skill, pushes the branch, then creates a new PR or updates an existing one with a rewritten body based on the full diff against the base branch. - Structured PR descriptions: Generates titles under 72 characters and bodies following a fixed Summary/Behavior change/Implementation/Testing/Notes structure written in Simplified Technical English. - CI monitoring and failure diagnosis: Waits for checks to register, watches them with gh pr checks --watch --fail-fast, and on failure reports the job name, failing step, quoted error line, cause, and proposed fix. - Use Case: You finish a feature branch with uncommitted changes. Invoke the skill and it commits, pushes, opens the PR against main, prints the URL, then watches CI and tells you exactly which step failed and why. ## Quick Start Ask the assistant to create a pull request for the current branch and watch the CI checks, optionally providing a title or base branch.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I create a GitHub pull request from the command line?

Use the gh CLI: push your branch with git push -u origin HEAD, then run gh pr create with a title and body. This Skill automates the full sequence, including committing pending changes and selecting the correct base branch.

How do I update an existing pull request description?

Run gh pr edit --body with the new description. This Skill regenerates the body from the full diff against the base branch rather than only the new commits, then prints the PR URL confirming the update.

How do I watch GitHub CI checks for a pull request?

Use gh pr checks --watch --fail-fast to stream check status until completion. Wait about 20 seconds after pushing so GitHub can queue the workflows, since an immediate query may return no checks.

Why does gh pr checks show no checks right after pushing?

GitHub needs time to register and queue workflows after a push, so an immediate query returns nothing. Sleep roughly 20 seconds before querying; if no checks are configured at all, that is a normal result, not a failure.

What happens when a CI check fails on my pull request?

The Skill runs gh run view --log-failed, reads the failed log, and reports the job name, failing step, the first real error line quoted, the cause, and a proposed fix. It does not apply fixes or re-run checks without your approval.

Can I force-push or merge the pull request with this workflow?

No. Force-pushing, merging, marking ready for review, and requesting reviewers are prohibited unless you explicitly ask. If a push is rejected because the branch diverged, the Skill stops and asks how to proceed.