菜单
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.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/aws-samples/sample-agent-skill-eval --skill pr-naming-convention命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
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.
基于 SOC 职业分类
正在显示 SKILL.md
| 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>"
]
}
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)