skills.rest
aws-samples
aws-samplesOFFICIAL
Explore all skills by this author →
WebsiteGitHub

pr-naming-convention

Validate PR titles and branch names against team naming conventions.

12|2|Updated Mar 15, 2026
Search Tags:#validation#regex#branch#pr#naming#ci
One-click install
npx skills add https://github.com/aws-samples/sample-agent-skill-eval --skill pr-naming-convention
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-naming-convention
Source: https://github.com/aws-samples/sample-agent-skill-eval/tree/main/examples/lifecycle-demo/v2
Command: npx skills add https://github.com/aws-samples/sample-agent-skill-eval --skill pr-naming-convention

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The PR naming-convention validator helps teams enforce consistent naming, reducing confusion and review friction caused by poorly named PRs and branches.

Core Features & Use Cases

  • Validates PR titles against the [TEAM-<number>] format.
  • Validates branch names against the <team>/TEAM-<number>-<description> pattern.
  • Provides actionable feedback and suggested corrections to bring inputs into compliance. Use cases include CI checks for PR pipelines, pre-commit checks, and onboarding new contributors to the team's naming rules.

Quick Start

Run the validation script at scripts/check_pr.py to validate a PR title or branch.

Frequently Asked Questions about pr-naming-convention

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

FAQPage Schema
How do I enforce PR naming conventions in a CI pipeline?▼

You can enforce PR naming conventions in CI by running a regex-based validation script that checks PR titles and branch names against required formats, emitting structured feedback and a non-zero exit code on violations to fail the pipeline.

What format should branch names and PR titles follow for automated validation?▼

Automated validation checks PR titles against the [TEAM-<number>] format and branch names against the <team>/TEAM-<number>-<description> pattern to ensure consistent naming across your software projects.

Can I use regex validation for branch names during pre-commit checks?▼

Yes, you can use the regex validation script as a pre-commit check to validate branch names and PR titles locally before pushing, providing actionable feedback and suggested corrections to bring inputs into compliance.

What is the best way to automate checks for inconsistent branch naming in software projects?▼

The best way to automate checks for inconsistent branch naming is to implement a regex-based validator in your CI pipelines that enforces specific patterns like <team>/TEAM-<number>-<description> and blocks non-compliant branches.

Why do my CI pipeline checks fail when validating PR titles?▼

Your CI pipeline checks fail because the PR title validator emits a non-zero exit code when titles do not match the required [TEAM-<number>] format, providing structured feedback to correct the naming violation.

Related Skills

Explore More Software Engineering Skills→
tykhoncodetykhoncode

speckit-git-validate

Validate Git feature branch names and matching spec directories.

Community
Intermediate
ManfronEnricoManfronEnrico

workspace-enforce

Block merges when high-severity workspace violations lack waivers.

Community
Advanced
CrazyDubyaCrazyDubya

git-workflow-enforcer

Enforce Conventional Commits, branch naming, and PR templates via Git hooks.

Community
Advanced
RyoMurakami1983RyoMurakami1983
2

git-initial-setup

Automates GitLab project and repository setup for streamlined onboarding and management.

Community
Intermediate