feature

Create a Git-flow feature branch with a structured naming convention.

1|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/jugrajsingh/skillgarden --skill feature-jugrajsingh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature
Source: https://github.com/jugrajsingh/skillgarden/tree/main/plugins/gitmastery/skills/feature
Command: npx skills add https://github.com/jugrajsingh/skillgarden --skill feature-jugrajsingh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of starting a new feature branch according to Git-flow conventions, ensuring consistency and clarity in your development workflow.

Core Features & Use Cases

  • Branch Creation: Initiates a new branch for feature development.
  • Git-flow Integration: Seamlessly integrates with the Git-flow branching model.
  • Naming Convention Enforcement: Guides users to adopt a structured naming convention for branches.
  • Use Case: When starting work on a new user authentication module, you can use this Skill to create a branch named PROJ-123-user-authentication.

Quick Start

Use the gitmastery feature skill to start a new branch for user authentication.

Frequently Asked Questions about feature

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

FAQPage Schema
How do I start a new feature branch using git-flow conventions?

To start a new feature branch using git-flow, you need to create a branch originating from the develop branch. This skill automates the initiation process and ensures your branch follows a structured naming convention like '<ticket>-<short-description>'.

What is the standard naming convention for a git feature branch?

A standard naming convention for a git feature branch typically uses a '<ticket>-<short-description>' format. This skill enforces this structure to maintain consistency and clarity across your development workflow.

Can I specify a custom branch name or does the skill prompt me interactively?

You can specify a custom branch name directly, or the skill can prompt you interactively. It supports both direct naming and interactive prompting to ensure the feature branch meets the required git-flow conventions.

How do I ensure consistency when creating feature branches for new modules?

Ensuring consistency when creating feature branches requires enforcing a structured naming convention like '<ticket>-<short-description>'. This skill automates that enforcement, guiding users to adopt standard git-flow branching models for new modules.

Does this branching skill require any specific git dependencies?

No specific dependencies are required to use this feature branching skill. It operates independently to initiate new feature branches and enforce naming conventions without relying on external components or modules.