pr

Commits, tests, pushes the feature branch, and opens a pull request via the forge CLI.

Updated May 9, 2026
One-click install
npx skills add https://github.com/natelandau/cc-plugin --skill pr-natelandau
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/natelandau/cc-plugin/tree/main/plugins/natelandau-toolkit/skills/pr
Command: npx skills add https://github.com/natelandau/cc-plugin --skill pr-natelandau

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Opening a pull request involves many error-prone steps: committing outstanding work, rebasing on the trunk, running linters and tests, pushing the branch, and writing a title and description that will survive as the squash commit. This Skill automates that entire workflow with guardrails so nothing is missed and the trunk is never touched. ## Core Features & Use Cases - End-to-end PR workflow: Detects the feature branch, default branch, and remote host, then commits, rebases, verifies the build is green, pushes, and opens the PR. - Multi-forge support: Uses the correct CLI for the remote host: gh for GitHub, tea for Gitea/Forgejo, and glab for GitLab, including draft handling per forge. - Squash-ready title and description: Writes a conventional-commit title and a lead block wrapped at 72 characters, with BREAKING CHANGE footers and optional review sections, honoring repo PR templates when present. - Use Case: After finishing a feature branch, ask to "put this up for review" and the Skill regroups a sprawled commit history, runs the full test gate, pushes the branch, and opens a ready-for-review PR with a properly formatted description. ## Quick Start Ask the assistant to open a pull request for the current branch, for example by saying "get this branch reviewed".

Frequently Asked Questions about pr

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

FAQPage Schema
How do I open a pull request for the current branch?

Ask to open, create, or make a PR, or say something like "get this reviewed". The Skill commits outstanding work, rebases on the default branch, runs the project's linters and tests, pushes the branch, and creates the PR with a conventional-commit title.

Which CLI tools create pull requests on GitHub, GitLab, and Gitea?

GitHub uses gh, GitLab uses glab, and Gitea or Forgejo uses tea. The Skill detects the remote host and uses the matching authenticated CLI, stopping with instructions if the right one is missing or not logged in.

Does the PR description follow conventional commit format?

Yes. The title is a conventional-commit subject like feat(scope): subject, and the lead block becomes the squash commit body wrapped at 72 characters. Breaking changes get both a ! marker and a BREAKING CHANGE footer.

What happens if a pull request already exists for my branch?

The Skill checks for an existing PR before pushing. If one is already open, it shows the PR URL and stops, offering to update it instead of creating a duplicate.

Why was my push rejected as non-fast-forward when opening a PR?

The branch was pushed before the rebase rewrote it, so the histories diverged. The Skill never force-pushes; it asks you to run git push --force-with-lease manually, then continues.

Can I open a draft pull request instead of a ready one?

Yes, but only when you explicitly ask. The Skill adds --draft for gh and glab, or prefixes the title with [WIP] for tea, which has no draft flag. By default every PR opens ready for review.