skills.rest
jeremy-newhouse
jeremy-newhouseCOMMUNITY
Explore all skills by this author →
GitHub

wa:dev-branch

Create or switch to a feature branch with enforced naming conventions.

Updated Mar 26, 2026
Search Tags:#branch naming#git branching#feature workflow#dev-branch automation#CI-ready conventions#statusline updates
One-click install
npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-dev-branch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wa:dev-branch
Source: https://github.com/jeremy-newhouse/eck-e2e-weather-app/tree/main/.claude/skills/dev-branch
Command: npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-dev-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces delays and mistakes by automatically creating or switching to a correctly named feature branch following the project’s branch convention.

Core Features & Use Cases

  • Branch assessment and safe switching: Checks the current git status and determines whether the user is already on a matching feature branch, otherwise it guides next steps to avoid wrong-branch work.
  • Naming-convention enforcement: Builds branch names in the required feat/WA-{issue-number}-{short-desc} or fix/WA-{issue-number}-{short-desc} format, enforcing lowercase, hyphen-separated, and max-length rules for the short description.
  • Staged workflow with status updates: Updates the statusline at the start of each stage and resets it on completion or error to keep execution traceable.

Quick Start

Run the command to create or switch to a properly named feature branch for a given issue description, such as: /wa:dev-branch feat/WA-123-short-description.

Frequently Asked Questions about wa:dev-branch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce git branch naming conventions for feature workflows?▼

To enforce git branch naming conventions, this Skill validates the working tree state and constructs branch names following the feat/WA-{issue-number}-{short-desc} or fix/WA- format, ensuring lowercase, hyphen-separated, and max-length rules.

Can I skip creating a feature branch if I am already on the correct dev branch?▼

Yes, you can skip branch creation. The Skill inspects the current branch and status to determine if you are already on a matching feature branch, optionally skipping stage creation and avoiding wrong-branch work.

What is the correct format for creating a feature branch from the dev HEAD?▼

The correct format for creating a feature branch from the dev HEAD requires a feat/ or fix/ prefix, followed by the issue number and a lowercase, hyphen-separated short description, such as feat/WA-123-short-description.

Does this branching automation require a specific rigor mode to validate the working tree?▼

The branching automation resolves the rigor mode from a standard setting or a --rigor flag to determine how strictly it validates the working tree state before creating the branch from the dev HEAD.

Why does the feature workflow statusline reset when branch creation fails?▼

The feature workflow statusline resets when branch creation fails to handle errors safely and keep execution traceable. It updates the statusline at the start of each stage and clears it upon completion or failure.

Related Skills

Explore More Software Engineering Skills→
OpenAuthorityOpenAuthority
8

git_status

Report staged, unstaged, and untracked files from git status --porcelain.

Official
Intermediate
JoeCP17JoeCP17
8

commit-push

Stage changes, create a conventional commit, and push to the remote branch.

Community
Intermediate
jeremy-newhousejeremy-newhouse

wa:git-flow

Automate Git Flow branching, commits, pushes, and pull requests.

Community
Advanced
bordenetbordenet
8

git-branch-conventions

Validate new git work branch names against semantic prefix and formatting rules.

Community
Basic