Skip to content
Back to skills

Pr

ASecurity

Push the branch and open a PR with a concise description and one label

  • 133 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 12, 2026
code-qualitybashtestingrefactoringgitdocumentation

Security analysis

A100/100

Scanned October 6, 2026

npx -y skills add gacela-project/gacela --skill pr --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Pr?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Pr
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/gacela-project-gacela/badge)](https://www.skillsdirectory.com/skills/gacela-project-gacela)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
description: Push the branch and open a PR with a concise description and one label
argument-hint: "[issue-number]"
disable-model-invocation: true
x-claude:
  allowed-tools: "Read, Edit, Bash(git *), Bash(gh *)"
x-codex:
  interface:
    display_name: "Pull request"
    short_description: "Push the branch and open a PR from the template. Args: issue number"
---

# Create Pull Request

## Context

::target claude
!`git branch --show-current`
!`git log main..HEAD --oneline`
!`git diff main..HEAD --stat`
::end
::target codex
Run `git branch --show-current`, `git log main..HEAD --oneline`, and `git diff main..HEAD --stat` first.
::end

## Instructions

1. **CHANGELOG check**: if the branch has user-facing changes and `CHANGELOG.md` is untouched, add the entry under `## Unreleased` and commit it before pushing.

2. **Local gate**: `composer test` must be green. Never push a red branch.

3. **Push**:
   ```bash
   git push -u origin HEAD
   ```

4. **Title**: `<type>(<scope>): <short description>`, under 70 characters. Take the type from the branch prefix (`feat/` → feat, `fix/` → fix, `ref/` → ref, `docs/` → docs). If the argument holds an issue number, start from its title:
   ```bash
   gh issue view <number> --json title -q '.title'
   ```

5. **Body**: read `.github/PULL_REQUEST_TEMPLATE.md` first and use its exact section headers, emojis included. Never hardcode them.
   - Say *what* changed and *why*, not how.
   - Add `Closes #<number>` so the merge closes the issue.
   - Keep it under 15 lines. No session links, tool footers, or attribution trailers.

6. **Create**:
   ```bash
   gh pr create --title "<title>" --assignee @me --label "<label>" --body "$(cat <<'EOF'
   <sections from .github/PULL_REQUEST_TEMPLATE.md>

   Closes #<issue-number>
   EOF
   )"
   ```
   Pick the one most relevant label:
   - `bug`: `fix/` branch
   - `enhancement`: `feat/` branch
   - `refactoring`: `ref/` branch, no behavior change
   - `documentation`: `docs/` branch
   - `pure testing`: only test changes
   - `dependencies`: dependency updates

7. **Report** the PR URL.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.