create-pr

Name: create-pr
Availability: InStock
Author: Nymbo

Create pull requests with conventional commits and lint, test, and build checks.

Updated Aug 23, 2026

Search Tags:#git #build #branching #review #lint #pull-request #conventional-commits

Ready to run

npx skills add https://github.com/Nymbo/Skills --skill create-pr-nymbo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/Nymbo/Skills/tree/main/create-pr
Command: npx skills add https://github.com/Nymbo/Skills --skill create-pr-nymbo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Guides creating a well-scoped PR with lint/build checks, conventional commits, and a clear description.

Core Features & Use Cases

Branching & commits: Descriptive branch names and small commits.
Quality gates: Run lint/tests/build before PR.
PR body: Descriptive summary and validation steps.

Quick Start

Use this skill to prepare a PR for a set of changes with a clear title and body including validation steps.

Frequently Asked Questions about create-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create a pull request that passes lint and build checks?▼

Create a pull request by making focused code changes, running lint and build checks locally before pushing, using conventional commit messages, and providing a clear PR description with validation steps. This ensures your PR is easy to review and safe to merge.

What's the best way to structure commits and branch names for a pull request?▼

Use descriptive branch names that reflect your changes and write small, focused commits following conventional commit format (e.g., feat:, fix:, docs:). This makes your PR history clear and easier for reviewers to follow.

How do I write a pull request description that helps reviewers?▼

Include a clear summary of what changed and why, then add validation steps that show how to test the changes. This gives reviewers confidence that your PR is complete and ready to merge.

Can I use conventional commits with my existing git workflow?▼

Yes, conventional commits work with any git workflow. They're a commit message format that pairs with descriptive branch names and automated quality checks to ensure consistent, reviewable PRs across your team.

What should I verify before submitting a pull request?▼

Run lint checks, execute tests, and verify the build succeeds locally. Include these validation steps in your PR description so reviewers understand exactly what you tested and can reproduce your verification.