start-work

Create a git worktree for a ticket and run repository setup.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/ambroselittle/agent-skills --skill start-work-ambroselittle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start-work
Source: https://github.com/ambroselittle/agent-skills/tree/main/skills/start-work
Command: npx skills add https://github.com/ambroselittle/agent-skills --skill start-work-ambroselittle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Create isolated git worktrees for a ticket, wire up repository setup, and optionally launch your editor, so you can start coding without affecting the main repo.

Core Features & Use Cases

  • Automates the end-to-end setup for a ticket: resolving the target repository, creating a new worktree, and configuring branch and base settings.
  • Supports automated repo setup detection and optional editor launch to streamline the first coding session.
  • Useful for parallel workstreams, reproducible environments, and quick onboarding of new tickets.

Quick Start

Provide a ticket ID or slug to begin, or run with no arguments to be prompted.

Frequently Asked Questions about start-work

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

FAQPage Schema
How do I create an isolated git worktree for a new ticket?

You can start a git worktree by providing a ticket ID or slug, which resolves the target repository, creates the worktree, configures branch settings, and optionally launches your editor.

What is git worktree isolation used for in development workflows?

Git worktree isolation allows developers to work on parallel workstreams across multiple repos without affecting the main repository, ensuring reproducible environments and clean branch configurations.

Can I run repository setup scripts automatically when creating a worktree?

Yes, automated repository setup detection runs after the worktree is created to wire up dependencies and environment configurations, streamlining your first coding session.

How do I start working on a ticket across multiple git repositories?

Starting work on a ticket across multiple repos is handled by resolving the source repository, determining the base branch, and guiding the end-to-end worktree creation workflow.

What happens if I run the worktree setup with missing ticket context?

Running with missing context triggers interactive prompts that ask for the missing ticket ID or slug, ensuring the worktree and branch are configured correctly.

Does the worktree setup support launching my code editor?

Yes, the workflow includes an optional editor launch step that opens the newly created worktree directory directly in your preferred coding environment.