Agent skill · software engineering · marcelorodrigo
create-pr
Create Pull Requests following best conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review.
Why this skill is useful
Adds specific commands and structured guidelines for creating pull requests that the AI wouldn't reliably generate on its own.
What it needs
Requires gh installed locally. About 3k tokens when loaded. Last updated 2026-08-02. 15 stars on the source repository.
What this skill does
Create Pull Request Create pull requests following the best engineering practices. Requires: GitHub CLI (gh) authenticated and available. Prerequisites Before creating a PR, ensure all changes are committed. If there are uncommitted changes, run the commit skill skill({ name: "conventional-commit" }) first to commit them properly. If the output shows any uncommitted changes (modified, added, or untracked files that should be included), invoke the commit skill skill({ name: "conventional-commit" }) before proceeding. Process Step 1: Verify Branch State Ensure: All changes are committed Branch is up to date with remote Changes are rebased on the base branch if needed Step 2: Analyze Changes Review what will be included in the PR: Understand the scope and purpose of all changes before writing the description. Step 3: Write the PR Description Use this structure for PR descriptions (ignoring any repository PR templates): Do NOT include: "Test plan" sections Checkbox lists of testing steps Redundant summaries of the diff Do include: Clear explanation of what and why Links to relevant issues or tickets (only if available) Context that isn't obvious from the code Notes on specific areas that need careful review Step 4: Create the PR Title format follows commit conventions: feat(scope): Add new feature fix(scope): Fix the bug refactor(scope): Refactor something PR Description Examples Feature PR Bug Fix PR Refactor PR Guidelines One PR per feature/fix - Don't bundle unrelated changes Keep PRs reviewable - Smaller PRs get faster, better reviews Explain the why - Code shows what; description explains why Editing Existing PRs When updating a PR after creation, the skill automatically selects the best approach based on your GitHub CLI version: gh 2.82.1+: Uses native gh pr edit (clean, full-featured) gh < 2.82.1: Falls back to gh api (avoids Projects classic deprecation bug) Check Your Version Modern Approach (gh 2.82.1+) Legacy Fallback (gh < 2.82.1) If gh pr edit fails with a …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills marcelorodrigo/create-pr