feature

Create standardized git feature branches and linked crosslink issues.

6|3|Updated Jun 25, 2026
One-click install
npx skills add https://github.com/dollspace-gay/crosslink --skill feature-dollspace-gay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature
Source: https://github.com/dollspace-gay/crosslink/tree/main/crosslink/resources/claude/skills/feature
Command: npx skills add https://github.com/dollspace-gay/crosslink --skill feature-dollspace-gay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually creating standardized feature branches and linking them to project tracking issues is tedious, prone to naming inconsistencies, and easy to forget during fast-paced development work.

Core Features & Use Cases

  • Automated Branch Naming: Slugifies human-readable feature descriptions to create valid feature/<slug> branch names that follow project conventions.
  • Precondition Validation: Checks for uncommitted changes and duplicate branch names to avoid git errors, prompting for user input when issues are detected.
  • Auto Issue Tracking: Creates a linked crosslink issue with medium priority and the feature label to track feature work from the very start.
  • Use Case: When starting work on a new feature like "add batch retry logic", this skill handles all setup steps so you can begin coding immediately without manual bookkeeping.

Quick Start

Use the feature skill to create a feature branch and linked crosslink issue for adding batch retry logic.

Frequently Asked Questions about feature

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

FAQPage Schema
How do I automatically create a git feature branch and link it to issue tracking?

To create a git feature branch and link it to issue tracking, this skill automates branch creation and generates a linked crosslink issue with default medium priority and a feature label. It slugifies human-readable descriptions into valid branch names.

What is the best way to standardize feature branch naming in git?

Standardizing feature branch naming is achieved by slugifying human-readable feature descriptions into valid `feature/<slug>` formats. This ensures consistent branch naming conventions across software development workflows without manual formatting.

How does precondition validation work when creating a new feature branch?

Precondition validation for feature branches checks for uncommitted changes and duplicate branch names to avoid git errors. When issues are detected, the system prompts for user input to resolve them before proceeding.

Can I automatically create crosslink issues with default priority when starting feature work?

Yes, you can automatically create crosslink issues when starting feature work. The system generates a linked tracking issue with default medium priority and applies a feature label to track work from the start.

What happens if I have uncommitted changes before creating a feature branch?

If uncommitted changes exist before creating a feature branch, the precondition validation detects them to prevent git errors. It prompts for user input to resolve the detected issues before proceeding with branch creation.