← ClaudeAtlas

start-devlisted

Start development — create worktree, implement tasks, validate, push, and open a PR. Use when the user has approved a plan or wants to begin coding from a GitHub issue, task description, or spec file. Covers everything from 'here's what to build' to 'PR is open for review'.
Tamircohen28/tamirs-superpowers · ★ 0 · Code & Development · score 76
Install: claude install-skill Tamircohen28/tamirs-superpowers
## Live context !`git branch --show-current 2>/dev/null | sed 's/^/current branch: /' || echo "not a git repo"` !`gh repo view --json defaultBranchRef --jq '"default branch: \(.defaultBranchRef.name)"' 2>/dev/null || true` !`gh issue list --state open --limit 5 --json number,title --jq '.[] | " #\(.number): \(.title)"' 2>/dev/null | head -5 || true` # start-dev Full implementation flow: set up workspace, implement all tasks, validate, push, and open a PR. ## Input Parse `$ARGUMENTS` as one of: - GitHub issue number(s) (e.g. `#258` or `258 259 260`) - A task description to implement directly - A file path to a spec or plan If empty, ask what to implement and stop. ## Required execution flow ### 1. Understand the work - If given issue numbers: `gh issue view <number>` - If given a description or file: read and parse tasks from it ### 2. Set up workspace Skip if already on a feature branch inside a worktree. Derive a short branch name from the task (e.g. `feat/add-user-auth`, `fix/null-pointer-login`): ```bash DEFAULT_BRANCH=$(gh repo view --json defaultBranchRef --jq .defaultBranchRef.name 2>/dev/null || echo "main") git fetch origin git worktree add .claude/worktrees/<branch-name> -b <branch-name> origin/$DEFAULT_BRANCH ``` All editing must happen inside the worktree directory, not the main checkout. ### 3. Implement For each task: 1. Read the files that need modification 2. Make the changes 3. Commit with conventional commit format: ``` <type>(<scope>):