branch-namer

Generate descriptive git branch names that follow the project's naming convention. Use this skill whenever the user asks to create a branch, name a branch, start working on a feature or fix, checkout a new branch, or when you're about to run `git checkout -b` or `git switch -c`. Also trigger when you see a vague branch name like `fix/auth` or `feature/billing` that lacks a description of what's actually changing — the branch name should always tell you *what* the change does, not just its category.

1.14x

Quality

88%

Does it follow best practices?

Impact

93%

1.14x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Evaluation results

100%

10%

Sprint Kickoff: Prepare Git Branches for Upcoming Work

Type selection and slug quality

Criteria

Without context

With context

feat not feature

100%

Correct CI branch type

100%

Correct test branch type

100%

Correct fix branch type

100%

Scope from commitlintrc

83%

100%

Billing scope

100%

Auth scope

100%

Slug word count

100%

Slug leads with verb

20%

100%

No type repetition in slug

100%

80%

17%

Technical Debt Cleanup: Branch Setup for Two Restructuring Tasks

Refactor vs chore type distinction

Criteria

Without context

With context

Indexer uses refactor

100%

Notifications uses chore

Indexer scope

100%

Notifications scope

100%

Indexer slug describes change

100%

Notifications slug describes change

100%

Slug word count

100%

Slug verb-led

100%

Under 50 characters

100%

Branch plan reasoning

40%

50%

100%

Provider Console Minimum Balance Feature

Sub-path scope and slug crafting

Criteria

Without context

With context

feat type prefix

100%

feat not feature

100%

Provider scope used

100%

Sub-path scope considered

100%

Domain term in slug

100%

Slug word count

100%

Under 50 characters

100%

Character count documented

100%

Slug verb-led

100%

No type in slug

100%

Repository: akash-network/console
Commit: 609b56d

Evaluated: 6 days ago
Agent: Claude Code
Model: Claude Sonnet 4.6

Table of Contents

Sprint Kickoff: Prepare Git Branches for Upcoming Work Technical Debt Cleanup: Branch Setup for Two Restructuring Tasks Provider Console Minimum Balance Feature

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.