wtp

Generate type/slug branch names and create git worktrees from task descriptions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/swat9013/dotfiles --skill wtp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wtp
Source: https://github.com/swat9013/dotfiles/tree/main/.claude-global/skills/wtp
Command: npx skills add https://github.com/swat9013/dotfiles --skill wtp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates consistent git branch naming and worktree creation from natural language task descriptions, eliminating manual branch-name crafting and repetitive worktree setup.

Core Features & Use Cases

  • Generates a type/slug branch name using task intent (feat, fix, refactor, docs, chore, test).
  • Retrieves tasks from Todoist when no argument is given and supports manual task input or selection.
  • Prompts the user to review or edit the suggested branch name and then runs wtp add -b to create the worktree.
  • Use case: Quickly turn a Todoist task or brief description into a standardized branch and a dedicated worktree to start development.

Quick Start

Run the skill with a task description or let it fetch a task from Todoist to generate a type/slug branch name and execute wtp add -b to create the worktree.

Frequently Asked Questions about wtp

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

FAQPage Schema
How do I create a git worktree from a natural language task description?

Create a git worktree from a natural language task description by generating a standardized type/slug branch name and executing wtp add -b. You can review or edit the suggested branch name and confirm the action before the worktree is created.

Can I fetch Todoist tasks to generate git branch names automatically?

Fetch Todoist tasks to generate git branch names automatically when no CLI argument is provided. If Todoist is unavailable, the workflow falls back to manual task input so you can still type a description and produce a standardized branch name.

What branch naming conventions are supported for git worktree creation?

Supported branch naming conventions for git worktree creation include standard prefixes: feat, fix, refactor, docs, chore, and test. The system applies the correct prefix and slug based on the detected intent of your natural language task description.

Do I need any external dependencies to automate git worktree setup?

No external dependencies are required to automate git worktree setup beyond the wtp CLI tool. Todoist integration is optional and used for fetching tasks, with a fallback to manual task input if the service is unavailable.

What happens if Todoist is unavailable when generating a branch name?

If Todoist is unavailable when generating a branch name, the workflow falls back to manual task input. You can type or select a task description directly, and the system will still generate a type/slug branch name and create the worktree.

Can I edit a suggested branch name before the git worktree is created?

You can edit a suggested branch name before the git worktree is created. The workflow prompts you to review or modify the generated type/slug name, ensuring the branch matches your standards before executing wtp add -b.