Skills Guide

Pull Request Management

VerifiedSafe

Creates pull requests with proper formatting. Use when opening PRs, preparing changes for review, or enforcing conventions for titles, descriptions, labels, and branch names.

Sby Skills Guide Bot
DevelopmentBeginner
706/2/2026
Claude CodeCursorWindsurfCopilotCodex
#pull-requests#conventional-commits#github#branch-naming#labeling

Recommended for

Backend developerClaude CodeCode reviewCursorFrontend developerCopilot

Our review

Creates properly formatted pull requests with conventional commit titles, structured description, appropriate labels, and standardized branch naming.

Strengths

  • Automates PR creation with clear conventions
  • Integrates Conventional Commit format for titles
  • Provides a description template with test plan
  • Applies relevant labels automatically

Limitations

  • Requires the AI tool to have access to gh CLI and a GitHub repository
  • Does not handle complex PR workflows (reviewers, assignees)
  • Depends on git history and branch diffs being available
When to use it

Use this skill when you need to open a standardized pull request on GitHub with consistent formatting.

When not to use it

Avoid for PRs requiring advanced customization or integrations with other platforms (GitLab, Bitbucket).

Security analysis

Safe
Quality score85/100

The skill only offers guidance on PR formatting and suggests standard git and gh commands for reviewing changes and creating PRs. No destructive, exfiltrating, or obfuscated actions are involved.

No concerns found

Examples

Create PR from current branch
Create a pull request for my current branch with a summary of the changes and a test plan. Use the conventional commit format for the title.
Open labeled PR
Open a PR for branch feat/search-pagination with label enhancement and documentation. Include verification steps.

name: pr description: Creates pull requests with proper formatting. Use when creating PRs, opening pull requests, or preparing changes for review.

Pull Requests

PR Title

Use the Conventional Commit Format, same as commit messages:

<type>(<scope>): <description>

Types

  • feat: User-facing features or behavior changes (must change production code)
  • fix: Bug fixes (must change production code)
  • docs: Documentation only
  • style: Code style/formatting (no logic changes)
  • refactor: Code restructuring without behavior change
  • test: Adding or updating tests
  • chore: CI/CD, tooling, dependency bumps, configs (no production code)

PR Description Template

## Summary

One sentence describing the overall change.

- Optional supporting details
- If needed

## Test plan

- [ ] How to verify it works

Labels

Apply all labels that fit. Use gh pr create --label <label> or gh pr edit --add-label <label>:

  • enhancement - User-facing features or improvements (must change production code behavior)
  • refactor - Production code changes that don't alter behavior
  • bug - Fixes broken production code functionality
  • test - Changes to tests
  • documentation - Documentation changes

No label needed for dependency bumps, CI/CD, tooling, or infrastructure changes.

Branch Naming

Use type/short-description:

feat/search-pagination
fix/year-search-bug
chore/pre-commit-hooks

Instructions

  1. Run git log main..HEAD to see commits for this branch
  2. Run git diff main...HEAD to see all changes
  3. Summarize the changes in 1-2 sentences
  4. Create a test plan with verification steps
  5. Apply appropriate labels
Related skills

Next.js App Router Expert

Development

A skill that turns Claude into a Next.js App Router expert.

Claude CodeCursoradvanced
890
234
2,846
Admin

README Generator

Development

Creates professional and comprehensive README.md files for your projects.

claudeCursorWindsurfbeginner
259
72
821
Admin

API Documentation Writer

Development

Generates comprehensive API documentation in OpenAPI/Swagger format.

claudeCursorWindsurfintermediate
156
44
682
Admin