start-next-task

Automate switching a feature worktree to a fresh next-task branch.

8|Updated Oct 11, 2023

Search Tags:#automation #git #workflow #branching #pr-management #fleet-claim

Ready to run

npx skills add https://github.com/jakildev/IrredenEngine --skill start-next-task

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: start-next-task
Source: https://github.com/jakildev/IrredenEngine/tree/main/.claude/skills/start-next-task
Command: npx skills add https://github.com/jakildev/IrredenEngine --skill start-next-task

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cleanly transitions a worktree from a completed task to a fresh next-task branch to keep PRs isolated and ready for further work.

Core Features & Use Cases

Handles standard and stack-mode workflows by basing the new branch on origin/master or the just-opened PR's head ref, respectively.
Validates PR state, ensures a clean working tree, and fetches latest origin to avoid stale references.
Derives a human-readable branch name, reads the target CLAUDE.md area to prime context, and reports the outcome to the user.

Quick Start

Read the relevant CLAUDE.md for the new task area and create a new branch from the appropriate base.

Frequently Asked Questions about start-next-task

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

FAQPage Schema

How do I transition to a new git branch after opening a pull request?▼

To transition to a new git branch after opening a pull request, automate switching from the completed task to a fresh next-task branch. It validates the PR state, fetches origin, and checks out a newly derived branch name to keep PRs isolated.

What is the best way to manage stacked PR workflows in git?▼

Managing stacked PR workflows in git involves basing the new branch on the just-opened PR's head ref instead of origin/master. This stack mode ensures the next task builds directly upon the previous pending changes.

How does branch automation handle local changes when starting a new task?▼

Branch automation handles local changes by discarding them before checking out the new branch. It ensures a clean working tree by validating state, fetching the latest origin, and discarding uncommitted modifications.

Can I use this workflow to read project context before checking out a branch?▼

Yes, you can use this workflow to read project context before checking out a branch. It reads the target CLAUDE.md file for the specified area to prime context and reports the outcome after the new branch is active.

Why does my next-task branch need to validate PR state and fetch origin?▼

Your next-task branch needs to validate PR state and fetch origin to avoid stale references and ensure the new branch is based on the correct, up-to-date base. This validation keeps PRs cleanly isolated and ready.

Do I need a clean working tree to automate git branch switching?▼

Yes, you need a clean working tree to automate git branch switching. The automation validates the PR state and discards local changes to ensure the worktree transitions cleanly from the completed task to the fresh branch.