pivoshenko/pivoshenko.ai / skills/git-issue-start
git-issue-start
VerifiedTake a GitHub issue from open to a checked-out branch - assign it to you, mark it in progress if the repo has such a label, derive a conventional branch name from its `type: *` label, branch off the detected base. Use for "start issue 42", "work on #42", "/git-issue-start 42", "let's do 42", "pick up that issue", "take the oauth issue", "I'll take this one", or whenever the user points at a tracked issue and is about to write code for it. Resolves an issue named by title via `gh issue list --search`. Boundary: with no issue in play it is `git-branch-create`'s, and this skill delegates naming and base detection to it. Assigns and branches immediately without asking for confirmation.
Git Issue Start
Issue -> assign -> branch -> checked out. No confirm.
Flow
-
Resolve the issue:
- Number given ->
gh issue view <n> --json number,title,labels,state,assignees,body - Title or topic given ("the oauth issue") ->
gh issue list --search "<terms>" --state open --json number,title --limit 10, then view the match. Exactly one hit -> take it. Several -> list them, ask which. None -> stop, say so. Why -> guessing an issue number assigns the wrong person to the wrong work and it is invisible until someone reads the tracker
- Number given ->
-
state == CLOSED-> stop. Surface number, title, and that it is closed. Never reopen here -
The issue has sub-issues (
gh issue view <n> --json subIssues -q '.subIssues.nodes | length'> 0) -> stop, list the open ones, and ask which to start. Then run this skill again on that number. Why -> a parent's work is its sub-issues, one branch each; a single branch and a single assignment for the whole tree is the wrong unit -
Assigned to someone else -> stop and ask before taking it. Own login from
gh api user -q .login; already yours -> proceed, assignment step is a no-op. Why -> an assignee is a claim by a person, and silently overwriting it is how two people ship the same fix -
Dirty tree -> stop. Tell the user to stash or commit first. Same reasoning as
git-branch-createstep 2:checkout -bcarries staged and unstaged changes into the new branch silently -
Derive the branch type from the issue's
type: *label:Issue label Branch type type: bugfixtype: enhancementfeattype: documentationdocstype: maintenancechoretype: securityfixtype: dependenciesbuildBare names count too (
bug,enhancement,documentation,maintenance,security,dependencies,deps) - same row.type: breakingcarries no branch type of its own; fall throughNo type label -> read the title's conventional prefix (
fix(api): ...->fix). No prefix either -> infer from title + body againstgit-commit's Type Pick table. Two type labels -> pick the dominant one, never compound the branch name -
Name and base follow
git-branch-createexactly - its Naming section and its base-detection incantation. Do not restate either. The desc is the issue title, kebab-cased, verb made imperative present, with the whole<type>/<desc>name 60 chars or fewer; over -> cut per that skill's desc rules, never truncate mid-word -
Name conflict check, before the tracker changes:
git show-ref --verify --quiet refs/heads/<name>succeeds -> the branch already exists; stop, surface the conflict, no overwrite. Why -> checking after assignment would halt the run with the issue assigned and labelled in progress but no branch created - the exact half-state the Rules forbid -
Assign to self:
gh issue edit <n> --add-assignee @me -
In-progress label, only if one already exists. Fetch the repo's labels once per run per canon label resolution:
gh label list --limit 200 --json name -q '.[].name'Chain, first existing name wins:
status: in progress->status: in-progress->in progress->in-progress->wip. Whole chain missing -> skip the step silently, no output, no error. Nevergh label create. Why -> this skill syncs globally and runs on repos with different label sets; the user's own taxonomy has no in-progress label at all, so absent is the normal case, not a failure -
Create + checkout per
git-branch-createstep 5 -
Record the issue on the branch:
git config branch.<name>.issue <n>Why -> the branch name carries no ticket id, and
git-commitreads this key to write theCloses #<n>trailer. Skip it and the commit has no link back to the tracker. Notgh issue develop- the siblings readbranch.<name>.issue, and develop's GitHub-side link carries no local key forgit-commitandgit-pr-createto read -
Print the report
Report
Three lines, nothing else:
issue #42 add oauth login (type: enhancement)
assignee @pivoshenko
branch feat/add-oauth-login off origin/main
Label chain dropped -> one extra line naming what was skipped. Nothing skipped -> no extra line.
Ticket IDs in Branch Names
git-branch-create keeps ticket IDs out of branch names unless asked, and starting from an issue does not change that: the link to #n rides in branch.<name>.issue (step 12), the commit footer (Closes #42), and the PR body (Resolves: #42) - all three of which a tool actually reads. A branch name is a human label, not a foreign key.
Rules
- Never reopen a closed issue here, never close an open one. Closing is the commit footer's job via
git-commit, or the user's - Branch created but
branch.<name>.issueunset -> the link is lost silently. Set it in the same run, never later - Never steal an assignment. Someone else in
assignees-> ask first, every time - Never push the branch.
git-pr-createpushes when there is something to review - Dirty tree -> stop before touching the issue at all. No half-state where the issue is assigned but no branch exists
- Never
gh label create. Missing chain -> skip and say so - Never invent the issue. Ambiguous search -> ask; empty search -> stop
- One issue per run. Batch starts are not a thing - a branch holds one piece of work
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |