feature

Create feature branches and crosslink issues from user descriptions.

27|3|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/forecast-bio/ferray --skill feature-forecast-bio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature
Source: https://github.com/forecast-bio/ferray/tree/main/.claude/skills/feature
Command: npx skills add https://github.com/forecast-bio/ferray --skill feature-forecast-bio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates creating a dedicated feature branch from a natural-language description and registers a matching crosslink issue to ensure traceability and consistent naming.

Core Features & Use Cases

  • Feature branch creation: derive a branch name feature/<slug> from a user-provided description.
  • Crosslink issue tracking: automatically create a crosslink issue titled from the feature description and link it to the branch.
  • Precondition validation: verify there are no uncommitted changes and that the target branch does not already exist before checkout.

Quick Start

Provide a human-readable feature description and the skill will generate the feature branch and corresponding crosslink issue.

Frequently Asked Questions about feature

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

FAQPage Schema
How do I automate creating a git feature branch and a linked issue from text?

To automate creating a git feature branch and a linked issue, provide a natural-language description. The tool generates a standardized feature branch name and automatically creates a matching crosslink issue for traceability.

How does branch name slug generation work for feature branches?

Slug generation for feature branches works by deriving a standardized branch name, formatted as feature/<slug>, directly from your human-readable feature description to ensure consistent naming across your development workflow.

Can I create a feature branch if I have uncommitted changes in my working tree?

You cannot create a feature branch with uncommitted changes in your working tree. Precondition validation checks for a clean working tree and verifies the target branch does not already exist before proceeding with checkout.

What is the best way to ensure traceability between feature branches and issues?

The best way to ensure traceability between feature branches and issues is to automate crosslink issue creation. This process links the generated feature branch directly to an issue titled from your original feature description.

Does this branching workflow require any external dependencies?

This branching workflow does not require external dependencies. It operates independently to perform precondition checks, generate branch name slugs, checkout branches, and create crosslink issues from your feature description.