create-pr
NewCreates GitHub pull requests with properly formatted titles that pass the check-pr-title CI validation. Use when creating PRs, submitting changes for review, or when the user says /pr or asks to create a pull request.
Summary
This skill automates the creation of GitHub pull requests with properly formatted titles that comply with the check-pr-title CI validation rules.
- It streamlines the PR submission process by ensuring titles follow the required convention, reducing manual errors and saving time for developers.
Install & Usage
~/.claude.jsonAdd the configuration to "mcpServers": { "create-pr": { "command": "...", "args": [] } }
/mcpUse Cases
Usage Examples
/create-pr
Create a pull request for my feature branch 'add-user-auth' with title 'feat: add user authentication'
/pr from branch 'fix-login-bug' with title 'fix: resolve login timeout issue'
Security Audits
Frequently Asked Questions
What is create-pr?
This skill automates the creation of GitHub pull requests with properly formatted titles that comply with the check-pr-title CI validation rules. It streamlines the PR submission process by ensuring titles follow the required convention, reducing manual errors and saving time for developers.
How to install create-pr?
To install create-pr: open your mcp config (~/.claude.json), then add the config to "mcpServers": { "create-pr": { "command": "...", "args": [] } }. Finally, /mcp in Claude Code.
What is create-pr best for?
create-pr is a mcp categorized under Development. It is designed for: code-review, coding, communication, devops. Created by n8n-io.
What can I use create-pr for?
create-pr is useful for: Create a pull request with a correctly formatted title after completing a feature branch.; Submit changes for code review with a title that passes CI validation automatically.; Quickly generate a PR when the user types /pr in the chat.; Ensure PR titles follow the project's commit message convention (e.g., 'feat: add login') to avoid CI failures.; Create a PR for a hotfix branch with a title that includes the issue number and type.; Draft a PR for a documentation update with a conventional title like 'docs: update README'..