Automated summary
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
Use this skill when you need to open a standardized pull request on GitHub with consistent formatting.
Avoid for PRs requiring advanced customization or integrations with other platforms (GitLab, Bitbucket).
Security analysis
SafeThe 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
How this analysis is madeExamples
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 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 onlystyle: Code style/formatting (no logic changes)refactor: Code restructuring without behavior changetest: Adding or updating testschore: 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 behaviorbug- Fixes broken production code functionalitytest- Changes to testsdocumentation- 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
- Run
git log main..HEADto see commits for this branch - Run
git diff main...HEADto see all changes - Summarize the changes in 1-2 sentences
- Create a test plan with verification steps
- Apply appropriate labels
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/pull-request-management-mm8o52gs/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/pull-request-management-mm8o52gs' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/pull-request-management-mm8o52gs/download' --output '.skill-downloads/pull-request-management-mm8o52gs/SKILL.md.part' && mv '.skill-downloads/pull-request-management-mm8o52gs/SKILL.md.part' '.skill-downloads/pull-request-management-mm8o52gs/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/pull-request-management-mm8o52gs/SKILL.md' && test -s '.skill-downloads/pull-request-management-mm8o52gs/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/pr' && cp -R '.skill-downloads/pull-request-management-mm8o52gs' '.claude/skills/pr'Cursor
test -f '.skill-downloads/pull-request-management-mm8o52gs/SKILL.md' && test -s '.skill-downloads/pull-request-management-mm8o52gs/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/pr' && cp -R '.skill-downloads/pull-request-management-mm8o52gs' '.cursor/skills/pr'Codex
test -f '.skill-downloads/pull-request-management-mm8o52gs/SKILL.md' && test -s '.skill-downloads/pull-request-management-mm8o52gs/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/pr' && cp -R '.skill-downloads/pull-request-management-mm8o52gs' '.agents/skills/pr'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/pull-request-management-mm8o52gs'openskills read 'pull-request-management-mm8o52gs'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/pull-request-management-mm8o52gs/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.