pr:validate

Validates GitHub PR titles and branch names, checking issue relevance for issue-* branches and generating non-compliance comments.

5|3|Updated May 19, 2026
One-click install
npx skills add https://github.com/awinogradov/code-assistants --skill pr-validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr:validate
Source: https://github.com/awinogradov/code-assistants/tree/main/claude-plugins/autopilot/skills/pr%3Avalidate
Command: npx skills add https://github.com/awinogradov/code-assistants --skill pr-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Validates PR titles and branch names against the repository's contributing guidelines to maintain code quality and consistency.

Core Features & Use Cases

  • PR Title Validation: Checks for adherence to the repository's title format guidelines.
  • Branch Name Validation: Ensures branch names follow the specified naming conventions.
  • Issue Verification: Validates issue existence and relevance if the branch name starts with 'issue-<number>-<short-description>'.
  • Comment Generation: Generates a clear, sarcastic GitHub PR comment for validation failures.

Quick Start

Use the pr:validate skill to check the compliance of your PR with the contributing guidelines.

Frequently Asked Questions about pr:validate

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

FAQPage Schema
How do I validate PR titles and branch names against contribution guidelines?

You can validate PR titles and branch names against contribution guidelines by running automated checks that compare submission formats with repository standards to ensure compliance and generate feedback.

How do I check if a branch name starting with issue- references a valid issue?

Automated PR validation checks issue existence and relevance for branches starting with 'issue-' by querying repository data via the GitHub CLI to ensure the referenced issue is valid.

Do I need the GitHub CLI to automate PR compliance checks?

Yes, you need the GitHub CLI and jq installed to automate PR compliance checks, as they provide the required access to query repository data and parse JSON output for validation.

Can I automatically generate GitHub PR comments for branch naming violations?

Yes, you can automatically generate GitHub PR comments for branch naming violations by using validation scripts that detect non-compliance and output structured, clear feedback for review.

What is the best way to enforce branch naming conventions in a repository?

The best way to enforce branch naming conventions is to implement automated validation that checks branch names against contribution guidelines and generates structured comments for non-compliant submissions.