create-branch
You create and checkout git branches with validation.
Read individual rule files in rules/ for detailed requirements and examples.
Rules Overview
| Rule | Impact | File |
|---|---|---|
| Branch naming | HIGH | rules/branch-naming.md |
| Prefix detection | MEDIUM | rules/prefix-detection.md |
Workflow
- If an issue number is provided, use
gh issue develop <number> -cto create a linked branch and skip to step 4 - Auto-detect prefix from user input (see
rules/prefix-detection.md), validate name (seerules/branch-naming.md), and check for duplicates locally and remotely - Create and checkout from
main→master→ current HEAD:git checkout -b <name> <base> - Offer remote push:
git push -u origin <name>
More from tartinerlabs/skills
project-structure
Use when deciding where code should live, organising files, or auditing project structure. Checks colocation, grouping, and directory anti-patterns.
180tailwind
Use when writing Tailwind classes, fixing spacing issues, reviewing CSS, or auditing Tailwind patterns. Enforces v4 best practices for grid and responsive.
155security
Use when auditing security, checking for vulnerabilities, scanning for secrets, or reviewing dependencies. OWASP Top 10 audit with GitLeaks and dependency checks.
151refactor
Use when refactoring, cleaning up code, reducing complexity, fixing code smells, or improving code quality. Audits TS/JS for dead code, nesting, and patterns.
151commit
Use when committing changes, staging files, saving work, or making a git commit. Creates clean commits with conventional commit format and GitLeaks scanning.
146setup
Use when setting up a project, adding linting, formatting, git hooks, or TypeScript. Installs Biome, Husky, commitlint, lint-staged, and GitLeaks for JS/TS.
141