branch-namer

What This Skill Does

The branch-namer skill is an intelligent utility designed to eliminate the friction associated with Git branch naming conventions. It bridges the gap between natural language intent and standardized developer workflows. By analyzing your plain-English description of a task, the AI agent determines the correct semantic prefix—such as 'feature/', 'bugfix/', or 'chore/'—and generates a concise, kebab-case branch name. This tool is built to enforce consistency across team repositories, ensuring that every branch is identifiable, searchable, and follows industry-standard patterns.

Installation

You can integrate this tool into your OpenClaw environment by running the following command in your terminal:

clawhub install openclaw/skills/skills/lxgicstudios/branch-namer

Ensure that you have an active OPENAI_API_KEY environment variable configured, as the skill utilizes LLM processing to interpret your intent and map it to effective naming conventions. Node.js 18 or higher is required for optimal performance.

Use Cases

• Onboarding developers: When team members are unfamiliar with complex, project-specific naming styles, this tool automatically guides them toward the correct format.
• Large-scale refactoring: Keep your git history clean when dealing with dozens of micro-tasks by maintaining strictly categorized branches.
• Context Switching: When jumping between multiple tasks, use the tool to generate descriptive names that make it obvious what code belongs to which objective.
• Continuous Integration: Automate the creation of ticket-linked branches to bridge the gap between project management software (like Jira or Linear) and your local git environment.

Example Prompts

1. "I need to start working on the payment gateway integration, please suggest a branch name."
2. "Create a branch for me to fix the overflow issue on the mobile landing page and attach the ticket ID JIRA-402."
3. "I'm updating the internal documentation files, what is a standard chore branch name for this?"

Tips & Limitations

To get the best results, always provide enough context in your description. Instead of saying 'fix things,' specify the component, such as 'navbar-dropdown: fix alignment issues.' While the '--create' flag is convenient for automating the 'git checkout -b' process, we recommend reviewing the suggested name first, especially in shared repositories where team-specific naming rules might involve strict automated pipeline triggers. The tool relies on your environment's git configuration; ensure you are in the correct root directory before running the command to avoid path errors.