Agent skill

PR

by TypedDevs in TypedDevs/bashunit

Push branch and create a GitHub PR with concise, issue-linked description

MITAuto-check: notesDevelopment

Install PR

skills CLI
$ npx skills add TypedDevs/bashunit --skill pr -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install TypedDevs/bashunit pr --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/TypedDevs/bashunit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/pr .claude/skills/pr && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
pr
GitHub stars
434
Token cost
~1k tokens
SKILL.md length
429 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Push branch and create a GitHub PR with concise, issue-linked description

  • Works in 7 steps: Review the branch context above — the… → MANDATORY: Update CHANGELOG.md — Read… → Push branch → …
  • Development work in your project
  • SKILL.md covers Current Branch Context, Arguments, Instructions and Example Usage
  • Calls git, gh and jq

What it does

PR is an agent skill from TypedDevs/bashunit. Push branch and create a GitHub PR with concise, issue-linked description

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. It works with GitHub and Bash. The repository describes itself as: A simple yet powerfull testing library for bash scripts. The licence is MIT.

When your agent uses it

  • Development work in your project

Example prompts

  • “/pr”

Requirements

  • Pre-approved tools (allowed-tools): Bash, Read, Grep, Glob

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Review the branch context above — the commits and changed files are already loaded.
  2. MANDATORY: Update CHANGELOG.md — Read CHANGELOG.md and check the ## Unreleased section. If the changes from this branch are NOT already…
  3. Push branch
  4. Generate PR title
  5. Create PR using the template from .github/PULL_REQUEST_TEMPLATE.md
  6. Move issue to "In Review" in GitHub Project (if issue number provided)
  7. Report the PR URL to the user.

What it can do on your machine

Read from SKILL.md and the folder at commit 8f297fb. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash
    • Read
    • Grep
    • Glob

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • gh
    • jq

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

PR loads about 1k tokens when it runs. Until then it costs about 19 tokens; SKILL.md has 429 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~19
When it runs · the whole SKILL.md, loaded when a task matches
~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash, Read, Grep, Glob

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from TypedDevs/bashunit at commit 8f297fb, republished under its MIT licence (© TypedDevs). 429 words, ~1,038 tokens.

Download SKILL.mdSave it as .claude/skills/pr/SKILL.md (or your agent's skills folder).
name
pr
description
Push branch and create a GitHub PR with concise, issue-linked description
allowed-tools
Bash, Read, Grep, Glob
user-invocable
true
argument-hint
[#issue]

Create Pull Request

Push branch and create a PR with a concise, issue-linked description.

IMPORTANT: This skill MUST be used for ALL pull request creation — even when the user says "create pr" without /pr. Never create a PR without following these steps.

Current Branch Context

  • Branch: !git branch --show-current
  • Commits: !git log main..HEAD --oneline 2>/dev/null
  • Changed files: !git diff main..HEAD --stat 2>/dev/null

Arguments

  • $ARGUMENTS - Issue reference (optional, e.g., #42 or 42). If provided, the PR will be linked to this issue.

Instructions

  1. Review the branch context above — the commits and changed files are already loaded.

  2. MANDATORY: Update CHANGELOG.md — Read CHANGELOG.md and check the ## Unreleased section. If the changes from this branch are NOT already listed there, you MUST update it before proceeding. Do NOT skip this step. Do NOT proceed to push without verifying.

  • Add entries under the appropriate subsection (### Added, ### Changed, ### Fixed, etc.)
  • Reference issue numbers where applicable (e.g., (Issue #123))
  • Commit the update:
    bash
    git add CHANGELOG.md && git commit -m "docs: update changelog"
  1. Push branch:
bash
git push -u origin HEAD
  • The pre-commit hook runs tests, shellcheck, and linting automatically on commit. Ensure all checks passed before pushing.
  • If push fails, read the output, fix the issue, commit the fix, and retry. Do NOT use --no-verify to bypass.
  1. Generate PR title:
  • If $ARGUMENTS contains an issue number, fetch the issue title:
    bash
    gh issue view <number> --json title -q '.title'
  • PR title format: <type>(<scope>): <short description> (conventional commit style, under 70 chars)
  • Derive the type from the branch prefix (feat/ → feat, fix/ → fix, docs/ → docs)
  1. Create PR using the template from .github/PULL_REQUEST_TEMPLATE.md:
Show full SKILL.md (166 more words)Show less
bash
gh pr create --title "<title>" --assignee @me --label "<label>" --body "$(cat <<'EOF'
## 🤔 Background

Related #<issue-number>

<1-2 sentences: motivation and context for the changes>

## 💡 Changes

- <bullet 1: what changed and why>
- <bullet 2>
- <bullet 3> (optional)
- <bullet 4> (optional)
EOF
)"

MANDATORY: Always follow the PR template structure (## 🤔 Background + ## 💡 Changes). Never use a different format.

Assignee: Always assign to @me (the PR creator).

Labels: Add the single most relevant label based on the branch prefix and change context:

  • bug — branch starts with fix/ and addresses a defect
  • enhancement — branch starts with feat/ or adds new functionality
  • documentation — branch starts with docs/ or only changes docs
  • refactor — code restructuring with no behavior change
  • ui — visual/frontend-only changes
  • investigation — spikes, research, or exploratory work

Body guidelines:

  • Background: Link the issue with Related #<number>, then 1-2 sentences of context. NEVER use Closes or Fixes.
  • Changes: 2-4 short bullet points. Focus on what and why, not implementation details.
  • No file lists, no class names, no code snippets in the body.
  • Keep the entire body under 15 lines.
  1. Move issue to "In Review" in GitHub Project (if issue number provided):
bash
# Read project config from .claude/github-project.json
ITEM_ID=$(gh project item-list PROJECT_NUMBER --owner OWNER --format json \
  | jq -r '.items[] | select(.content.number == ISSUE_NUMBER) | .id')

gh project item-edit \
  --id "$ITEM_ID" \
  --project-id "PROJECT_ID" \
  --field-id "STATUS_FIELD_ID" \
  --single-select-option-id "IN_REVIEW_OPTION_ID"

Note: Requires project scope. Run gh auth refresh -s project if needed.

  1. Report the PR URL to the user.

Example Usage

/pr
/pr #42
/pr 15

© TypedDevs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/pr of TypedDevs/bashunit.

Open the folder on GitHubat commit 8f297fb

Compare with similar skills

PR next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

PR compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
PR this skillTypedDevs/bashunit434—~1kAutomated safety check: NotesMIT
Beava PR Reviewbeava-dev/beava138—~2.1kAutomated safety check: PassApache-2.0
Lade Releasezifeo/lade133—~749Automated safety check: PassMPL-2.0
Ru ReviewDicklesworthstone/repo_updater128—~2.9kAutomated safety check: PassCustom licence
ForgeDock PR Review AdapterRapierCraftStudios/ForgeDock117—~620Automated safety check: PassAGPL-3.0
Opsmill Dev Analyzing Bugsopsmill/infrahub529—~2.3kAutomated safety check: PassApache-2.0

Similar skills

  • Beava PR Review

    beava-dev/beava

    Reviews a beava PR diff for real bugs, beava-specific architectural invariants, and AI-generated "slop" patterns (hollow code, phantom imports, inflated comments, disconnected pipelines).

    138 GitHub stars~2.1k tokensUpdated 4 mo ago
    DevelopmentAuto-check passed
  • Lade Release

    zifeo/lade

    Prepare a Lade release: update CHANGELOG.md and bump crate versions with cargo set-version.

    133 GitHub stars~749 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Ru Review

    Dicklesworthstone/repo_updater

    Review GitHub issues and PRs across repositories using the ru CLI tool.

    128 GitHub stars~2.9k tokensUpdated 6 days ago
    DevelopmentAuto-check passed
  • ForgeDock PR Review Adapter

    RapierCraftStudios/ForgeDock

    Adapts a shared pull request review flow to the ForgeDock repository, with its own change categories, shell and installer checks, and optional sub-agent fan-out.

    117 GitHub stars~620 tokensUpdated today
    DevelopmentAuto-check passed
  • Performs root-cause analysis of a bug — from a GitHub issue, an issue URL, or a free-text description — before any reproduction or fix is written.

    529 GitHub stars~2.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Portfolio

    thesun4sky/jobstack

    포트폴리오 최적화 스킬. An agent skill from thesun4sky/jobstack.

    143 GitHub stars~2.1k tokensUpdated 1 mo ago
    DevelopmentAuto-check: notes

More from TypedDevs/bashunit

All 11 skills in this repo
  • Commit

    TypedDevs/bashunit

    Stage and commit changes using conventional commits format. An agent skill from TypedDevs/bashunit.

    434 GitHub stars~781 tokensUpdated yesterday
    Auto-check: notes
  • Gh Issue

    TypedDevs/bashunit

    Fetch GitHub issue, create branch, plan and implement with TDD, then open PR

    434 GitHub stars~721 tokensUpdated yesterday
    Auto-check: notes
  • Gh Issues

    TypedDevs/bashunit

    Walk over all open GitHub issues that are unassigned or assigned to the current user, and process each one via the /gh-issue skill, sequentially.

    434 GitHub stars~1.7k tokensUpdated yesterday
    Auto-check: notes
  • Pre Release

    TypedDevs/bashunit

    Run comprehensive pre-release validation checklist. An agent skill from TypedDevs/bashunit.

    434 GitHub stars~488 tokensUpdated yesterday
    Auto-check: notes
  • Release

    TypedDevs/bashunit

    Run pre-release validation and execute the release process. An agent skill from TypedDevs/bashunit.

    434 GitHub stars~618 tokensUpdated yesterday
    Auto-check: notes
  • Review

    TypedDevs/bashunit

    Review a GitHub pull request; defaults to the current branch's PR when no number is given

    434 GitHub stars~449 tokensUpdated yesterday
    Auto-check: notes

Works with

Categories

Questions about PR

What does PR do?

Push branch and create a GitHub PR with concise, issue-linked description. PR is an agent skill from TypedDevs/bashunit.

When should I use PR?

PR fits situations like: development work in your project.

How do I install PR in Claude Code?

Run `npx skills add TypedDevs/bashunit --skill pr -a claude-code`. Or copy the skill folder (.claude/skills/pr in TypedDevs/bashunit) into .claude/skills/pr in your project. Claude Code loads it when a task matches its description.

How do I install PR in Codex?

Run `npx skills add TypedDevs/bashunit --skill pr -a codex`. Or copy the skill folder (.claude/skills/pr in TypedDevs/bashunit) into .agents/skills/pr in your project. Codex loads it when a task matches its description.

Can I use PR in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add TypedDevs/bashunit --skill pr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pr, .gemini/skills/pr, .github/skills/pr and .opencode/skills/pr in your project.

What does PR need to run?

Going by SKILL.md and its folder, PR needs the command-line tools its instructions call (git, gh and jq). Its frontmatter pre-approves these tools: Bash, Read, Grep, Glob.

Does PR access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is PR safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does PR use?

PR is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does PR use?

About 1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to PR?

Skills that share tags, products or a category with PR: Beava PR Review (beava-dev/beava, 138 stars), Lade Release (zifeo/lade, 133 stars), Ru Review (Dicklesworthstone/repo_updater, 128 stars) and ForgeDock PR Review Adapter (RapierCraftStudios/ForgeDock, 117 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains PR?

TypedDevs (a GitHub organization) maintains it in TypedDevs/bashunit, which has 434 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 6, 2026.

Source: TypedDevs/bashunit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.