Create git branches named by conventional-commit type: <type>/<kebab-description>. Use when: creating any new git branch, starting work that needs a branch, or naming a branch. Triggers on: 'create branch', 'new branch', 'branch off', 'checkout -b', '/branch'.
Scanned 9/9/2026
Install to Claude Code
Skills Directorynpx -y skills add ahonn/dotfiles --skill branch --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Branch?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/ahonn-branch)More formats (shields.io, HTML) on the badges page.
---
name: branch
description: "Create git branches named by conventional-commit type: <type>/<kebab-description>. Use when: creating any new git branch, starting work that needs a branch, or naming a branch. Triggers on: 'create branch', 'new branch', 'branch off', 'checkout -b', '/branch'."
allowed-tools: Bash
argument-hint: "[work description or ticket]"
---
# Conventional Branch Names
Branch names use the same type vocabulary as conventional commits:
```
<type>/<short-kebab-description>
```
Examples: `feat/user-auth`, `fix/login-crash`, `refactor/api-client`, `chore/update-deps`.
## Rules
1. **Type** — the conventional-commit type the dominant commit on this branch would have: `feat`, `fix`, `refactor`, `perf`, `docs`, `test`, `build`, `ci`, `chore`, `revert`.
2. **Description** — 2–4 words, kebab-case, specific: what the branch delivers, not how. Lowercase only, no spaces.
3. **Ticket IDs** — if the work has a ticket, put its ID after the type: `feat/lin-123-user-auth`.
4. **No agent-branded prefixes** — never `codex/...`, `claude/...`, or `agent/...`. The branch describes the work, not the tool that wrote it.
5. **Base** — branch off the up-to-date default branch unless the work explicitly builds on the current branch.
## Procedure
1. Derive type and description from the requested work (or "$ARGUMENTS" if provided).
2. Validate: `git check-ref-format --branch <name>`.
3. Create: `git switch -c <name>`.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Implement modern responsive layouts using container queries, fluid typography, CSS Grid, and mobile-first breakpoint strategies. Use when building adaptive interfaces, implementing fluid layouts, or creating component-level responsive behavior.
Creating and refining Mermaid diagrams with live reload. Use when users want flowcharts, sequence diagrams, class diagrams, ER diagrams, state diagrams, or any other Mermaid visualization. Provides best practices for syntax, styling, and the iterative workflow using mermaid_preview and mermaid_save tools.
Use when the user wants to design a mobile app, create screens, build UI, or interact with their Sleek projects. Covers high-level requests ("design an app that does X") and specific ones ("list my projects", "create a new project", "screenshot that screen").
SwiftUI frontend visual design skill. Creates beautiful, distinctive iOS/macOS interfaces that avoid generic AI slop patterns. Covers design direction, layout systems, typography, color, spacing, brand integration, and design review. Use when designing new SwiftUI views, reviewing UI quality, creating iOS prototypes, choosing visual styles, improving app aesthetics, or when the UI looks generic or AI-generated.
Use when designing iOS interfaces, implementing accessibility (VoiceOver, Dynamic Type), handling dark mode, ensuring adequate touch targets, providing animation/haptic feedback, or requesting user permissions. Apple Human Interface Guidelines for iOS compliance.
