create-pull-request
Create Pull Request
This skill ensures pull requests are created correctly using the gh CLI, adhering to branch naming, commit formatting, and PR templates.
Before Creating a PR (Pre-flight Checklist)
Before running gh pr create, please verify the state of the repository. Explain to the user why these checks are important for a clean Git history and smooth review process:
- Check uncommitted changes: Are there uncommitted changes? (Run
git status). If yes, ask the user if they want them committed or stashed. - Review your own diff: Do the changes match the PR intent? (Run
git diff main...HEADor similar). Avoid creating a PR without reviewing the diff so you can catch accidental inclusions like secrets or debug statements. - Check the branch: Are you on the correct branch? Ensure you are opening a PR from a feature branch rather than directly from
mainormasterto prevent accidental merges of incomplete work. - Push the branch: Ensure the branch is pushed to the remote (
git push -u origin <branch-name>) before creating the PR, otherwise theghCLI will fail.
Expected Output
When a user asks to create a PR, clearly state the steps you are taking to verify the state of the repository and the branch. Once checks are complete, provide the exact gh pr create command that will be executed, and wait for the user to confirm before proceeding.
Branch & Title Conventions
- Branch Naming: Use
type/issue-number-slugortype/slug.
More from hrdtbs/agent-skills
plan-self-review
Self-evaluate a plan on a 100-point scale after it is created or updated. Make sure to use this skill immediately whenever you create a plan or update a plan, even if the user does not explicitly ask for a review. This skill ensures that the plan is clear, comprehensive, feasible, and consistent before execution.
46commit
Expert-level commit creation and formatting following Conventional Commits. Make sure to use this skill whenever you need to create a commit message, save changes to git, structure a logical commit history, or when the user mentions 'commit', 'git commit', 'コミット', '変更をコミット', or asks you to push their code.
40mcp-builder
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
4prompt-evaluator
Evaluate and score user-written LLM prompts on a 100-point scale across 5 axes (Clarity, Structure, Information Content, Specificity, Context), providing specific improvement suggestions and a revised prompt. Make sure to use this skill whenever the user asks to evaluate, review, score, or improve a prompt, or when they say things like 'このプロンプトどう？', 'プロンプトを評価して', 'rate my prompt', 'review this prompt', or 'is this prompt good enough?'. This skill focuses on scoring existing prompts, not writing new ones from scratch.
4skill-judge
Evaluate Agent Skill design quality against official specifications and best practices. Use when reviewing, auditing, or improving SKILL.md files and skill packages. Provides multi-dimensional scoring and actionable improvement suggestions.
4skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
4