One-click install
npx skills add https://github.com/kapilvirenahuja/garura --skill start-feature-kapilvirenahuja
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start-feature
Source: https://github.com/kapilvirenahuja/garura/tree/main/core/components/plays/start-feature
Command: npx skills add https://github.com/kapilvirenahuja/garura --skill start-feature-kapilvirenahuja

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It turns an arbitrary starting state (uncommitted changes, an issue number, or a title) into a ready-to-work GitHub-tracked workflow without losing your local work.

Core Features & Use Cases

  • Resolves or creates the tracking GitHub issue from either explicit input (issue number/title) or inferred work from your current changed files.
  • Creates or switches to the correct feature branch following the naming convention type/issue_number-slug, while preserving any uncommitted changes.
  • Initializes the STM workspace for that issue so you have a consistent place to store and continue evidence and artifacts.
  • Use Case: You have local modifications and want a feature branch that’s properly tied to an open GitHub issue; run the play to get the issue, branch, and STM directory set up in one step.

Quick Start

Ask an agent to run /start-feature with either no arguments, an issue number like 42, or a descriptive title like Add OAuth login.

Frequently Asked Questions about start-feature

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

FAQPage Schema
How do I create a feature branch from uncommitted changes without losing my local work?

To create a feature branch from uncommitted changes without losing local work, this Skill preserves your working tree state while automatically checking out the correct branch and resolving the associated GitHub issue.

How do I set up a GitHub issue and feature branch workflow from a descriptive title?

Setting up a GitHub issue and feature branch workflow from a descriptive title is done by passing the title to the Skill, which creates the issue, generates a type/issue_number-slug branch, and initializes the STM directory.

Can I resume work on an existing GitHub issue and feature branch using intent-driven development?

Yes, you can resume work on an existing GitHub issue and feature branch by passing the issue number, which switches to the correct branch and initializes the STM workspace to continue your development work.

What is deterministic orchestration for starting enterprise development workflows?

Deterministic orchestration for starting enterprise development workflows is an agent-delegated process that resolves GitHub issues, checks out feature branches, and initializes STM directories while preserving uncommitted local file changes.

Does the STM workspace initialization require an explicit issue number?

No, STM workspace initialization does not require an explicit issue number; it applies confidence-gated inference to generate the issue from uncommitted changes or accepts an explicit issue number or descriptive title.