issue-start

Create an isolated git worktree for an issue and append metadata to its body.

12|1|Updated Dec 27, 2025
One-click install
npx skills add https://github.com/apokamo/kaji --skill issue-start-apokamo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-start
Source: https://github.com/apokamo/kaji/tree/main/.claude/skills/issue-start
Command: npx skills add https://github.com/apokamo/kaji --skill issue-start-apokamo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Issue handling often requires setting up isolated development environments per issue and ensuring metadata is consistently recorded in the issue discussion. This skill automates creating a dedicated worktree and appending metadata for traceability.

Core Features & Use Cases

  • Isolated worktree creation: Spins up a separate development workspace per issue.
  • Meta-information enrichment: Automatically appends issue context to the body for auditability.
  • Guided workflow integration: Fits into Kaji's issue-management flow with clear steps and checkpoints.

Quick Start

Initialize a worktree for the given issue and attach metadata to the issue body.

Frequently Asked Questions about issue-start

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

FAQPage Schema
How do I set up an isolated git worktree for issue management?

An isolated git worktree for issue management creates a separate development workspace per issue and appends metadata to the issue body for traceability. It requires Kaji tooling, a valid issue identifier, and access to git worktree and symlink operations.

Why use a dedicated git worktree per issue instead of a standard branch?

Using a dedicated git worktree per issue provides environment separation for code, docs, or experiments without switching branches in a single directory. It creates isolated local worktrees across the issue lifecycle, keeping dependencies and build artifacts separate.

Can I automate appending issue metadata to the issue body?

Yes, you can automate appending issue metadata to the issue body using Kaji's guided workflow integration. This meta-information enrichment automatically attaches issue context to the issue body for auditability and traceability when the worktree is initialized.

Do I need Kaji tooling to create a worktree and append issue metadata?

Yes, you need Kaji tooling to create a worktree and append issue metadata. The workflow requires Kaji's issue-management flow, along with access to git worktree, symlink operations, and repository overlay guidance described in the Skill.

What are the limitations of using symlink operations for issue worktree isolation?

The limitations of using symlink operations for issue worktree isolation involve requiring repository overlay guidance and access to specific symlink operations. The workflow is constrained to issue lifecycles involving branching, local worktrees, and environment separation.