Feature Request: Built-in Issue/Ticket + Git Worktree Integration

Summary

Claude Code already documents git worktrees as a parallel workflow pattern (in common-workflows.md), but there's an opportunity to make this a first-class citizen by integrating worktrees with issue/ticket-based workflows.

Problem

When developers work on multiple GitHub issues in parallel, they currently need to:

1. Manually create worktrees
2. Navigate to each worktree
3. Start Claude Code sessions separately
4. Manually track which worktree is for which issue

This is friction that could be automated.

Proposed Solution

A built-in command or workflow that:

1. Takes a GitHub issue reference (e.g., #346 or a URL)
2. Creates an isolated worktree with a branch following naming conventions
3. Fetches issue context (title, description, labels, milestone)
4. Installs dependencies automatically
5. Runs baseline tests to verify clean state
6. Enters plan mode ready to implement

Example Usage

claude --work-on "#346"
# or
claude --work-on "https://github.com/org/repo/issues/346"

Or as an interactive command:

> /work-on #346

What This Would Automate

| Manual Step | Automated |
|-------------|-----------|
| git worktree add ... | ✅ Auto-create |
| cd <worktree> | ✅ Auto-navigate |
| npm install | ✅ Auto-detect & install |
| gh issue view #346 | ✅ Auto-fetch context |
| Session naming | ✅ Auto-name based on issue |

Benefits

1. Parallel Work Made Easy - Work on 5 issues simultaneously with full isolation
2. No Branch Conflicts - Each worktree has independent state
3. Issue Context Loaded - Claude knows what to implement
4. Clean Baseline - Tests run before starting work
5. Consistent Workflow - Same pattern for all issue-based work

Current Workaround

I've implemented this as a custom skill (work-on-ticket), but it would be more powerful as a built-in feature with:

• Native GitHub integration (already exists via gh CLI)
• Session management (track which session is for which issue)
• Worktree cleanup when PRs merge

Related

• Documentation: "Run parallel Claude Code sessions with Git worktrees" in common-workflows.md
• Existing worktree support works well, this would just add issue-context integration

Environment

• Claude Code version: Latest
• OS: macOS
• Use case: Multi-issue parallel development

---

Happy to provide more details or help test if this is something the team is interested in building!