New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

PR

by talmolab in talmolab/sleap

Create a well-structured GitHub PR with proper branching, testing, formatting, and documentation.

BSD-3-Clause-ClearAuto-check passedDevelopment

Install PR

skills CLI
$ npx skills add talmolab/sleap --skill pr -a claude-code

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

GitHub CLI
$ gh skill install talmolab/sleap 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/talmolab/sleap.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
617
Token cost
~1.7k tokens
SKILL.md length
561 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
BSD-3-Clause-Clear

At a glance

Create a well-structured GitHub PR with proper branching, testing, formatting, and documentation.

  • Works in 9 steps: Branch Setup → Understand the Problem → Implement Changes → …
  • The user says create a PR
  • SKILL.md covers Overview, Step 1: Branch Setup, Step 2: Understand the Problem and Step 3: Implement Changes, plus 13 more sections
  • Calls uv, git and gh; reaches docs.sleap.ai

What it does

PR is an agent skill from talmolab/sleap. Create a well-structured GitHub PR with proper branching, testing, formatting, and documentation. Use when the user says "create a PR", "make a PR", "open a pull request", or wants to submit changes for review. Handles the full workflow: branch creation, implementation, testing, formatting, committing, and PR creation with comprehensive descriptions.

Its SKILL.md is about 1.7k 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, covering Pull requests and Commit messages. It works with GitHub. The repository describes itself as: A deep learning framework for multi-animal pose tracking.

When your agent uses it

  • The user says create a PR
  • Open a pull request
  • Wants to submit changes for review

Example prompts

  • “create a PR”
  • “make a PR”
  • “open a pull request”
  • “/pr”

Requirements

  • Python 3

Workflow steps

9 steps, taken from the step headings in SKILL.md.

  1. Branch Setup
  2. Understand the Problem
  3. Implement Changes
  4. Write Tests
  5. Format Code
  6. Run Tests with Coverage
  7. Commit Changes
  8. Push to GitHub
  9. Create Pull Request

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • uv
    • git
    • gh

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • docs.sleap.ai

    Also links to:

    • claude.com

    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 1.7k tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 561 words of instructions outside code blocks.

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

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 passed

The automated check found no risky patterns in SKILL.md.

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 talmolab/sleap at commit 4786f14, republished under its BSD-3-Clause-Clear licence (© talmolab). 561 words, ~1,689 tokens.

Download SKILL.mdSave it as .claude/skills/pr/SKILL.md (or your agent's skills folder).
name
pr
description
Create a well-structured GitHub PR with proper branching, testing, formatting, and documentation. Use when the user says "create a PR", "make a PR", "open a pull request", or wants to submit changes for review. Handles the full workflow: branch creation, implementation, testing, formatting, committing, and PR creation with comprehensive descriptions.

Create a GitHub Pull Request

Overview

This skill guides the complete PR workflow from branch creation to PR submission. Follow all steps in order to ensure high-quality, well-documented contributions.

Step 1: Branch Setup

Pull latest develop
bash
git checkout develop
git pull origin develop
Create feature branch

Use a descriptive branch name following the pattern: {type}/{description}

Types:

  • feature/ - New functionality
  • fix/ - Bug fixes
  • refactor/ - Code restructuring
  • docs/ - Documentation updates
  • test/ - Test additions/improvements
bash
git checkout -b feature/descriptive-name

Step 2: Understand the Problem

Before coding, clearly identify:

  1. Core problem: What issue are we solving?
  2. Scope: What files/modules will be affected?
  3. Approach: What's the implementation strategy?
  4. Edge cases: What scenarios need special handling?

If there's an associated GitHub issue, fetch it for context:

bash
gh issue view <issue-number>

Step 3: Implement Changes

  • Make focused, incremental changes
  • Follow existing code patterns and style
  • Add docstrings and comments for complex logic
  • Consider backwards compatibility

Step 4: Write Tests

Location

Tests go in the tests/ directory, mirroring the source structure.

Requirements
  • Cover all new functionality
  • Test edge cases and error conditions
  • Test both success and failure paths
  • Aim for high coverage of changed code
Test file naming
  • test_{module_name}.py for module tests
  • Place in corresponding tests/ subdirectory

Step 5: Format Code

Run formatting and linting:

bash
# Format code
uv run ruff format sleap tests

# Fix auto-fixable lint issues
uv run ruff check --fix sleap tests

Then manually fix any remaining errors which cannot be automatically fixed by ruff.

Step 6: Run Tests with Coverage

Run the full test suite with coverage:

bash
uv run pytest -q --maxfail=1 --cov --cov-branch && rm -f .coverage.* && uv run coverage annotate
Check coverage for changed files

The coverage annotate command creates {module_name.py},cover files next to each module.

To find which files changed:

bash
git diff --name-only $(git merge-base origin/develop HEAD)

Review the ,cover files for your changed modules to ensure adequate coverage.

Coverage markers in annotated files
  • > means line was executed
  • ! means line was NOT executed (needs test coverage)
  • - means line is not executable (comments, blank lines)

Step 7: Commit Changes

Pre-commit format+lint gate

Always re-run format and lint on changed files immediately before committing. This catches formatting drift from edits made after the initial Step 5 pass:

bash
uv run ruff format sleap tests
uv run ruff check --fix sleap tests

If either command modifies files, stage the changes before committing.

Commit structure

Make well-structured, atomic commits:

  • Each commit should be a logical unit of work
  • Write clear, descriptive commit messages
  • Use conventional commit format when appropriate
Show full SKILL.md (215 more words)Show less
Commit message format
<type>: <short description>

<optional longer description>

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Types: feat, fix, refactor, test, docs, chore

Step 8: Push to GitHub

bash
git push -u origin <branch-name>

Step 9: Create Pull Request

Create the PR
bash
gh pr create --base develop --title "<descriptive title>" --body "$(cat <<'EOF'
## Summary
<1-3 bullet points describing the changes>

## Changes Made
- <detailed list of changes>

## Example Usage
```python
# For enhancements, show how to use the new functionality

API Changes

  • <list any API changes, new parameters, removed functionality>

Testing

  • <describe test coverage>
  • <note any manual testing done>

Design Decisions

  • <explain key architectural choices>
  • <note trade-offs considered>

Future Considerations

  • <potential improvements not in scope>
  • <known limitations>

Closes #<issue-number> (if applicable)

🤖 Generated with Claude Code EOF )"


### If updating an existing PR

Fetch current PR description:
```bash
gh pr view <pr-number> --json body -q '.body'

Update PR description:

bash
gh pr edit <pr-number> --body "<new body>"
Fetch associated issue for context

If an issue is linked:

bash
gh issue view <issue-number>

Use issue context to ensure PR description addresses all requirements.

PR Description Checklist

  • Summary clearly explains the "what" and "why"
  • All significant changes are documented
  • Example usage provided for new features
  • API changes explicitly listed
  • Breaking changes highlighted
  • Test coverage described
  • Design decisions explained with reasoning
  • Related issues linked

Docs Preview

PRs that modify docs/, sleap/, or mkdocs.yml will automatically get a docs preview deployed at:

https://docs.sleap.ai/pr/<pr-number>/

A comment will be posted on the PR with the preview link.

Quick Reference Commands

bash
# Branch setup
git checkout develop && git pull origin develop
git checkout -b feature/my-feature

# Format and lint
uv run ruff format sleap tests
uv run ruff check --fix sleap tests

# Test with coverage
uv run pytest -q --maxfail=1 --cov --cov-branch && rm -f .coverage.* && uv run coverage annotate

# Find changed files
git diff --name-only $(git merge-base origin/develop HEAD)

# Pre-commit format+lint gate (always run before committing)
uv run ruff format sleap tests
uv run ruff check --fix sleap tests

# Commit
git add <files>
git commit -m "feat: description"

# Push and create PR
git push -u origin <branch>
gh pr create --base develop --title "Title" --body "Description"

# View/edit existing PR
gh pr view <number>
gh pr edit <number> --body "New description"

# View linked issue
gh issue view <number>

CI Checks

PRs trigger the following CI checks:

  • Lint: uv run ruff check sleap tests and uv run ruff format --check sleap tests
  • Tests: uv run pytest --cov=sleap on Ubuntu, Windows, and macOS
  • Docs Preview: Auto-deployed for changes to docs/, sleap/, or mkdocs.yml

Ensure all checks pass before requesting review.

© talmolab, BSD-3-Clause-Clear. 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 talmolab/sleap.

Open the folder on GitHubat commit 4786f14

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 skilltalmolab/sleap617—~1.7kAutomated safety check: PassBSD-3-Clause-Clear
PR Finalize Reviewmicrosoft/garnet12k—~3.1kAutomated safety check: PassMIT
React Router Pull Request Creatorremix-run/react-router57k—~2.5kAutomated safety check: PassMIT
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT
Gh PR Metadatamodule-federation/core2.7k—~1kAutomated safety check: PassMIT
Draft Pull Request Creatorwordpress-mobile/WordPress-Android3.2k—~881Automated safety check: NotesGPL-2.0

Similar skills

  • PR Finalize Review

    microsoft/garnet

    Official

    Checks that a pull request's title and description match its implementation and reviews the code for Garnet best practices, reporting findings without posting them.

    12k GitHub stars~3.1k tokensUpdated today
    DevelopmentAuto-check passed

  • React Router Pull Request Creator

    remix-run/react-router

    Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.

    57k GitHub stars~2.5k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Verdaccio Pull Request Workflow

    verdaccio/verdaccio

    Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Gh PR Metadata

    module-federation/core

    Update the current GitHub PR title and body for this repository so they match the repo's pull request template and conventional-commit title style.

    2.7k GitHub stars~1k tokensUpdated today
    DevelopmentAuto-check passed

  • Draft Pull Request Creator

    wordpress-mobile/WordPress-Android

    Commits and pushes current changes, writes a pull request title and body from the branch history and template, and opens a draft PR on GitHub after you approve it.

    3.2k GitHub stars~881 tokensUpdated today
    DevelopmentAuto-check: notes

  • Submit PR

    tisfeng/Easydict

    创建或复用当前 checkout 已提交变更的 GitHub PR，必要时推送任务分支。PR 审查使用 review-pr；仅本地提交使用 git-commit。

    15k GitHub stars~595 tokensUpdated 2 days ago
    DevelopmentAuto-check passed

More from talmolab/sleap

  • Qt Testing

    talmolab/sleap

    Capture and visually inspect Qt GUI widgets using screenshots.

    617 GitHub stars~557 tokensUpdated 8 days ago
    Auto-check passed

  • Investigation

    talmolab/sleap

    Scaffolds a structured investigation in scratch/ for empirical research and documentation.

    617 GitHub stars~899 tokensUpdated 8 days ago
    Auto-check passed

  • Sleap Support

    talmolab/sleap

    Handle SLEAP GitHub support workflow for issues and discussions.

    617 GitHub stars~2k tokensUpdated 8 days ago
    Auto-check passed

Works with

Categories

Questions about PR

What does PR do?

Create a well-structured GitHub PR with proper branching, testing, formatting, and documentation. PR is an agent skill from talmolab/sleap. Create a well-structured GitHub PR with proper branching, testing, formatting, and documentation.

When should I use PR?

PR fits situations like: the user says create a PR; open a pull request; wants to submit changes for review.

How do I install PR in Claude Code?

Run `npx skills add talmolab/sleap --skill pr -a claude-code`. Or copy the skill folder (.claude/skills/pr in talmolab/sleap) 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 talmolab/sleap --skill pr -a codex`. Or copy the skill folder (.claude/skills/pr in talmolab/sleap) 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 talmolab/sleap --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 (uv, git and gh). Our summary lists: Python 3.

Does PR access the network?

SKILL.md names 2 domains. In commands or code: docs.sleap.ai; the agent is likely to contact it when it follows the instructions. As links in the text: claude.com. This is read from the text; nothing was executed.

Is PR safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does PR use?

PR is published under the BSD-3-Clause-Clear 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 1.7k tokens (SKILL.md is roughly 6.8k 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: PR Finalize Review (microsoft/garnet, 12k stars), React Router Pull Request Creator (remix-run/react-router, 57k stars), Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars) and Gh PR Metadata (module-federation/core, 2.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains PR?

talmolab (a GitHub organization) maintains it in talmolab/sleap, which has 617 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on September 30, 2026.

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