← ClaudeAtlas

gh-currentlisted

Set the active issue — moves it from `status:todo` to `status:in-progress` and verifies the WIP guardrail (one in-progress issue per assignee). Mirrors Orchestra MCP's `set_current_feature`. Auto-invoke after a feature/bug is created and the user wants to start work, or when the user says "let's work on
fadymondy/gh-pms · ★ 0 · AI & Automation · score 70
Install: claude install-skill fadymondy/gh-pms
# gh-current Mark an issue as the active piece of work AND create the feature branch the work will live on. ## What it does 1. **Pre-flight: WIP check** — Calls `mcp__github__list_issues` filtered by: - `assignee`: current user (`mcp__github__get_me` if unknown) - `labels`: `status:in-progress` - `state`: open 2. If results > 0 and `wip_limit=1` (default per workflow), STOP: ``` WIP limit reached. You have #X already in progress. Finish it (run /gh-pms:gh-advance #X) or set it back to todo before starting #N. ``` 3. **Read issue** — `gh issue view {N} --json title,labels` to get title (for branch slug) and kind (for branch prefix). Kind comes from the `type:*` label or the GitHub native Issue Type. 4. **Branching policy** — per `workflows/default.yaml#branching`: a. If kind is in `pr_required_kinds` (default: feature / bug / hotfix / chore / testcase) AND the current branch is in `protected_base` (default: main / master): - Compute branch name from `branch_template`. Default: `{kind_short}/{number}-{slug}` where `slug` is the issue title lowercased with non-alphanum runs collapsed to `-`, capped at 40 chars. - Run `git fetch origin` then `git checkout -b {branch}` (or `git checkout {branch}` if it already exists locally) so all subsequent commits land on the feature branch. - Comment on the issue: `🌿 Branch \`{branch}\` created from \`{base}@{sha7}\`.` b. If the user is already on a non-protected branch, leave it alone — assume