intake-issue

Automating GitHub issue intake uses scripts to parse an issue URL or number, derive a consistent branch type and slug, create a dedicated git worktree in a sibling directory, and bootstrap the development environment for immediate work.

A git worktree creates an isolated working directory alongside your main repository, allowing you to checkout a feature branch for a specific issue without disrupting your current development state or stashing changes.

Yes, you need the gh CLI installed and authenticated to fetch GitHub issue data from a URL or issue number. However, if you provide raw text instead, jq handles the JSON parsing without requiring gh.

To initialize a development environment automatically, the skill runs an init-worktree script that executes appropriate package manager install scripts and sets up required tools within the new worktree directory to ensure dependencies are ready for development.

Yes, this automated worktree setup is applicable to issue-driven workflows across teams. It standardizes branch naming and environment bootstrapping so every team member starts from a consistent development state when picking up a submitted issue.

A limitation of using git worktrees is that they consume additional disk space for each isolated branch directory. You should also avoid checking out the same branch in multiple worktrees simultaneously, as git restricts a branch to a single working tree to prevent file conflicts.