How do I install the Pr Naming Convention skill?

Run npx skillmds@latest add aws-samples/pr-naming-convention in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pr Naming Convention safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pr Naming Convention?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pr Naming Convention free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pr Naming Convention?

aws-samples (@aws-samples) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pr Naming Convention by aws-samples

Name: Pr Naming Convention
Author: aws-samples

Pr Naming Convention

Validates PR titles and branch names against the company naming convention. Use when the user mentions PR titles, branch naming, pull request naming conventions, or asks to check whether a PR title or branch name follows the standard format.

aws-samples debc522 5 files · 12.3 KB Updated Sep 17, 2026

File contents

PR Naming Convention Validator

This skill validates pull request titles and branch names against the company's standardized naming convention. It helps catch formatting issues before code review.

When to use this skill

A user asks you to validate a PR title or branch name
A user wants to create a new PR and needs the correct title format
A user asks about the team's PR or branch naming rules
A user wants to fix a malformed PR title or branch name

Convention summary

PR title format: [TEAM-<number>] <type>: <description>

Types: feat, fix, docs, refactor, test, chore
Description: max 72 characters, lowercase start, no trailing period

Branch name format: <team>/<ticket>-<description>

Example: platform/TEAM-42-add-auth
Description uses kebab-case (lowercase + hyphens)

For the full convention with examples and edge cases, read references/naming-rules.md in this skill's directory.

How to validate

Use the validation script at scripts/check_pr.py in this skill's directory. The script uses pure regex matching — no shell commands, no eval, no external dependencies beyond Python's standard library.

Validating a PR title

python <skill-path>/scripts/check_pr.py title "[TEAM-42] feat: add user authentication"

Validating a branch name

python <skill-path>/scripts/check_pr.py branch "platform/TEAM-42-add-auth"

Output format

The script prints a JSON object to stdout:

{
  "valid": true,
  "input": "[TEAM-42] feat: add user authentication",
  "type": "title"
}

On failure, the output includes an errors array explaining what went wrong:

{
  "valid": false,
  "input": "fix stuff",
  "type": "title",
  "errors": [
    "PR title must match format: [TEAM-<number>] <type>: <description>"
  ]
}

Helping users fix issues

When a PR title or branch name fails validation, don't just report the error — suggest a corrected version. For example:

User input: "added login feature for TEAM-42" Suggested fix: "[TEAM-42] feat: add login feature"

User input (branch): "feature/login-page" Suggested fix: "platform/TEAM-42-add-login-page" (ask the user for the team name and ticket number if not provided)

---name: pr-naming-conventiondescription: Validates PR titles and branch names against the company naming convention. Use when the user mentions PR titles, branch naming, pull request naming conventions, or asks to check whether a PR title or branch name follows the standard format.---# PR Naming Convention ValidatorThis skill validates pull request titles and branch names against the company'sstandardized naming convention. It helps catch formatting issues before code review.## When to use this skill- A user asks you to validate a PR title or branch name- A user wants to create a new PR and needs the correct title format- A user asks about the team's PR or branch naming rules- A user wants to fix a malformed PR title or branch name## Convention summary**PR title format:** `[TEAM-<number>] <type>: <description>`- Types: `feat`, `fix`, `docs`, `refactor`, `test`, `chore`- Description: max 72 characters, lowercase start, no trailing period**Branch name format:** `<team>/<ticket>-<description>`- Example: `platform/TEAM-42-add-auth`- Description uses kebab-case (lowercase + hyphens)For the full convention with examples and edge cases, read`references/naming-rules.md` in this skill's directory.## How to validateUse the validation script at `scripts/check_pr.py` in this skill's directory.The script uses pure regex matching — no shell commands, no eval, no externaldependencies beyond Python's standard library.### Validating a PR title```bashpython <skill-path>/scripts/check_pr.py title "[TEAM-42] feat: add user authentication"```### Validating a branch name```bashpython <skill-path>/scripts/check_pr.py branch "platform/TEAM-42-add-auth"```### Output formatThe script prints a JSON object to stdout:```json{ "valid": true, "input": "[TEAM-42] feat: add user authentication", "type": "title"}```On failure, the output includes an `errors` array explaining what went wrong:```json{ "valid": false, "input": "fix stuff", "type": "title", "errors": [ "PR title must match format: [TEAM-<number>] <type>: <description>" ]}```## Helping users fix issuesWhen a PR title or branch name fails validation, don't just report the error —suggest a corrected version. For example:**User input:** `"added login feature for TEAM-42"`**Suggested fix:** `"[TEAM-42] feat: add login feature"`**User input (branch):** `"feature/login-page"`**Suggested fix:** `"platform/TEAM-42-add-login-page"` (ask the user for theteam name and ticket number if not provided)

Frequently asked questions