elite-dev

Opens a pull request following common conventions: an ETT task link as the first line of the body (skipped only when the developer confirms no ETT task applies), a bulleted summary, unwrapped paragraphs, a footer that references the linked GitHub issue (and closes it on merge when eligible), and labels copied from that issue. Use whenever creating a PR — "open a PR", "create the PR", "let's PR this" — or after `gh stack submit --auto`, which can create several PRs in one call that each need this treatment.

Turns a GitHub issue into an implementation plan that proves code reuse before it proposes new code: reads the issue, searches the repo for an existing helper, type, or pattern that already covers each piece of the work, follows the house conventions in the repo's own CLAUDE.md, and asks the developer about every ambiguity instead of guessing. Runs inside plan mode and ends by calling ExitPlanMode. Use right after an issue is marked started — "let's plan issue 24", "plan #40", "how should we build issue 51", or an explicit "/plan-issue 40".

Fetches unresolved review comments on a pull request (from any reviewer — Copilot, a human, another bot), verifies each finding against the actual code, presents them formatted for the developer to triage, then — only after explicit go-ahead — applies the agreed fixes, commits/pushes, replies to each addressed comment explaining the fix, and resolves its thread. Use when the user says things like "review the PR comments", "address Copilot's feedback", "fix the review comments on PR 153", or pastes a `#pullrequestreview-<id>` URL. Do NOT use this to write the original code review — only to work through comments a review already produced.

Set up or clean up a git worktree for a parallel Claude/dev session on a TypeScript/JavaScript or .NET repo. Use when starting a new worktree ("set up a worktree for issue X", "start a parallel session"), or when a PR merges and its worktree needs removing. Not needed for a single-task session working directly in the main checkout.

Marks a GitHub issue as started: assigns it to the developer and, if this repo uses a GitHub Projects board, sets its Status to "In Progress". Use as soon as work on an issue begins — a planning session counts, not just writing code — e.g. "let's plan issue 24", "let's start #40", "begin working issue 51", or an explicit "/start-issue 40". Invoke it at the start of that work, before diving into planning or implementation.