skills.rest
dokipen
dokipenCOMMUNITY
Explore all skills by this author →
GitHub

new-work

Create isolated git worktrees with issue-numbered branches tracking the default remote.

1|1|Updated Mar 5, 2026
Search Tags:#workflow#branching#worktree#git-worktree#feature-development#developer-tool#issue-number
One-click install
npx skills add https://github.com/dokipen/claude-cadence --skill new-work-dokipen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: new-work
Source: https://github.com/dokipen/claude-cadence/tree/main/.gemini/skills/new-work
Command: npx skills add https://github.com/dokipen/claude-cadence --skill new-work-dokipen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Starting work on a new issue can clutter the default branch; this Skill creates an isolated git worktree and a corresponding feature branch to keep development clean and organized.

Core Features & Use Cases

  • Creates a dedicated worktree for the new issue-based feature under .worktrees/
  • Validates branch naming to start with the issue number for traceability
  • Sets up the branch to track the default remote and prepares a clean starting point

Quick Start

Run the /new-work <issue-number>-<branch-name> command to create a dedicated worktree and branch for the feature.

Frequently Asked Questions about new-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 feature branch?▼

To create an isolated git worktree, run the /new-work command with an issue number and branch name. This sets up a dedicated worktree under the .worktrees/ directory and configures a corresponding branch to track the default remote.

Why use git worktrees instead of branching directly on the main branch?▼

Git worktrees keep your main branch clean by creating an isolated working directory for each new issue. This prevents development clutter and ensures traceability without switching branches in a single directory.

What is the correct branch naming convention for issue-based feature development?▼

The correct branch naming convention requires the branch name to start with the issue number for traceability. You format this as <issue-number>-<branch-name> when running the worktree creation command.

Does the worktree creation process automatically configure remote tracking?▼

Yes, the worktree creation process automatically configures remote tracking. It sets up the new feature branch to track the default remote and initializes the .worktrees/ directory if it does not already exist.

How do I set up a clean starting point when starting work on a new issue?▼

To set up a clean starting point for a new issue, use a dedicated worktree command that validates branch naming and initializes an isolated directory. This prepares a clean feature branch tracking the default remote.

Related Skills

Explore More Software Engineering Skills→
ReScienceLabReScienceLab
10

using-git-worktrees

Create an isolated git worktree for a feature branch with automatic project setup.

Official
Advanced
AndyAnh174AndyAnh174

git-pushing

Stage all changes, commit with a conventional message, and push to the default remote branch.

Community
Basic
codekilncodekiln
3

git-worktrees

Create and manage git worktrees for parallel feature development.

Community
Intermediate
bryonjacobbryonjacob

working-in-git-worktrees

Create, switch, and remove isolated git worktrees for parallel development.

Community
Basic