pr-guidelines

Enforce project-specific Git guidelines for branch pushes and pull requests.

5|Updated Jan 21, 2011
One-click install
npx skills add https://github.com/minusfive/dot --skill pr-guidelines
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-guidelines
Source: https://github.com/minusfive/dot/tree/main/.claude/skills/pr-guidelines
Command: npx skills add https://github.com/minusfive/dot --skill pr-guidelines

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides clear, actionable guidelines to ensure that branches are pushed correctly and pull requests are created in a standardized, review-ready format, preventing common errors and improving code review efficiency.

Core Features & Use Cases

  • Commit Convention Enforcement: Ensures adherence to Conventional Commits for both branches and PR titles.
  • Push Verification: Guides users to confirm successful remote pushes before proceeding.
  • PR Formatting: Specifies requirements for PR titles and bodies, emphasizing conciseness and relevance.
  • Use Case: When a developer is ready to submit their changes, this Skill ensures they follow the project's established workflow for pushing code and creating a pull request, making the review process smoother for everyone.

Quick Start

Follow the pr-guidelines skill to push your branch and create a pull request.

Frequently Asked Questions about pr-guidelines

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

FAQPage Schema
How do I enforce code review guidelines for git pull requests?

To enforce code review guidelines for git pull requests, this skill specifies strict requirements for commit message formatting, branch pushing, and PR titles to ensure consistency and clarity in the development workflow.

What is the best way to format commit messages and PR titles for consistency?

The best way to format commit messages and PR titles is by adhering to Conventional Commits. This skill enforces these specific formatting guidelines for both branch commits and pull request titles to keep projects standardized.

How do I verify a remote branch push before creating a pull request?

To verify a remote branch push before creating a pull request, this skill guides you to confirm push success. It adheres to commit guidelines and verifies the remote push was successful before allowing PR creation.

Does this PR workflow skill require any specific git branching dependencies?

No, this PR workflow skill does not require any specific git branching dependencies. It operates independently to enforce project-specific guidelines for pushing branches and creating standardized, review-ready pull requests.

Why does my pull request creation fail after pushing a git branch?

Pull request creation may fail if the remote push was not successful or if commit messages and PR titles do not adhere to Conventional Commits. This skill verifies push success and enforces formatting guidelines before PR creation.

Can I use these pull request guidelines to streamline an existing development workflow?

Yes, you can use these pull request guidelines to streamline an existing development workflow. The skill provides actionable rules for branch pushing and PR formatting, preventing common errors and improving code review efficiency.