auto_task.execute_with_stacked_prs

Goal

• Execute one GitHub issue as a stack of sequential branches and PRs
  • Name each branch <BASE>_<ID> (ID = 1, 2, 3, ...)
  • Branch each one from the previous branch, so the PRs stack in review order
• Create the whole stack without stopping for review
  • The user reviews, edits, and merges each PR bottom-up later
• Follow .claude/skills/auto_task.rules.md for how tasks are queued, specified, and named

Input

• The user passes a task in the format

When to Use This Skill

• Use only when tasks favor stacked execution: complete specs, a real dependency chain, and a user who prefers one batch review over interruptions
• If a spec is unclear, follow .claude/skills/auto_task.rules.md section "Ask for Clarification Before Executing an Unclear Plan". Do not build on a guess
• Resolve all doubts with the user before you start, so the stack runs uninterrupted

Workflow

Confirm the Task List

• Follow .claude/skills/auto_task.rules.md section "Confirm the Task List Before Executing". Each ordered task is one branch
• Confirm task <ID+1> depends only on <ID>, not on master or earlier tasks
• If the order or a dependency is unclear, ask before starting. A wrong dependency means rebasing the whole stack above it

Create the Issue and the First Branch (_1)

• Follow .claude/skills/auto_task.rules.md section "One GitHub Issue Is the Unit of Work": one issue covers the whole stack

• Create the issue and the first branch / PR <BASE>_1

  > git_create_issue_and_branch.py \
      --gh_issue_title "<TITLE>" --gh_issue_body "<Description of entire stack>" \
      --suffix 1
  

• The description of the entire task is

• Commit the file passed by the user (e.g., tasks.md)

• Implement task 1, run its tests, commit, push

Stack Each Following Branch (_<ID>)

• For ID from 2 to N, while still checked out on <BASE>_<ID-1>:
  • Derive <BASE>_<ID> from the issue, not from the current branch name. Branch it from <BASE>_<ID-1>, not from master: