Is creating-branches-and-prs safe to install?

SaferSkills independently audited creating-branches-and-prs (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

.claude/skills/creating-branches-and-prs/SKILL.md · 1 file

.claude/skills/creating-branches-and-prs/SKILL.md2.0 KB · Markdown

name: creating-branches-and-prs

description: Creates git branches and GitHub pull requests following the project naming convention. Enforces the format type-issue_number-short-description for both branches and PR titles. Use when creating a branch, opening a PR, or asking about branch/PR naming.

Creating Branches and PRs

Naming Convention

Both branches and PR titles use the same format:

<type>-<issue_number>-<short-description>

Rules

Lowercase, hyphens only — no spaces, underscores, slashes, or camelCase
Type prefix — matches the issue label
Issue number — the GitHub issue this work addresses
Short description — 2-4 words summarizing the change

Types

Type	When	Maps to label
`feat`	New functionality	`enhancement`
`fix`	Bug fix	`bug`
`chore`	Maintenance, CI, deps, migrations	`chore`

Examples

Issue	Branch / PR title
#8 Add repo_type column	`chore-8-repo-type-column`
#9 dbt render_models	`feat-9-dbt-render-models`
#11 Indexer reindex_files	`feat-11-indexer-reindex-files`
#14 Tests for reindex	`feat-14-reindex-on-save-tests`

Creating a Branch

git checkout main
git pull origin main
git checkout -b <type>-<issue_number>-<short-description>

Creating a PR

Link the PR to its issue using Closes #<number> in the body. This auto-closes the issue on merge.

gh pr create \
  --title "<type>-<issue_number>-<short-description>" \
  --body "$(cat <<'EOF'
Closes #<issue_number>

## Summary
<1-3 bullet points>

## Test plan
<checklist from the issue's Test Plan section>
EOF
)"

PR Body Structure

See PR-TEMPLATE.md for the full template.

Validation Checklist

Before creating a branch or PR, verify:

[ ] Type matches the issue label (enhancement → feat, bug → fix, chore → chore)
[ ] Issue number exists and is open
[ ] Branch is based on latest main
[ ] PR body includes Closes #<number>

creating-branches-and-prs— agent skill

Is creating-branches-and-prs safe to install?

Creating Branches and PRs

Naming Convention

Rules

Types

Examples

Creating a Branch

Creating a PR

PR Body Structure

Validation Checklist

Audit the pieces. Scan the whole. Decide.