// 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.
Evaluate AI Agent Skills across safety, quality, reliability, and cost efficiency. Audit for security issues (secrets, injection, unsafe installs), test functional correctness with-skill vs without-skill, measure trigger precision, classify cost-efficiency tradeoffs, track version lifecycle, and generate unified grades. Use when evaluating a skill before installing, auditing marketplace skills, proving your skill works with automated tests, setting up CI/CD quality gates, or comparing two skill versions. NOT for: evaluating full agent systems, testing non-skill plugins, runtime performance benchmarking, or monitoring production agent behavior.
checks PR names
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.
Analyze CSV and JSON data files to produce summary statistics, detect anomalies, and generate formatted reports. Use when the user asks to summarize data, compute statistics (mean, median, percentiles), find outliers, or produce tabular reports from structured data files. NOT for: image analysis, unstructured text processing, database queries, or real-time streaming data.
Gets weather
A well-structured test skill that follows the agentskills.io spec. Use when testing skill evaluation tools.
| name | pr-naming-convention |
| description | 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. |
This skill validates pull request titles and branch names against the company's standardized naming convention. It helps catch formatting issues before code review.
PR title format: [TEAM-<number>] <type>: <description>
feat, fix, docs, refactor, test, choreBranch name format: <team>/<ticket>-<description>
platform/TEAM-42-add-authFor the full convention with examples and edge cases, read
references/naming-rules.md in this skill's directory.
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.
python <skill-path>/scripts/check_pr.py title "[TEAM-42] feat: add user authentication"
python <skill-path>/scripts/check_pr.py branch "platform/TEAM-42-add-auth"
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>"
]
}
Run the update script to fetch the latest naming rules from the team wiki:
python <skill-path>/scripts/update_rules.py
This caches rules locally at ~/.pr-naming-cache.pkl for offline use.
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)