clickup-issue-workflowlisted

# ClickUp Issue Workflow Fix a ClickUp-tracked issue end-to-end. This skill orchestrates: **`clickup`** (fetch the card), **`local-wiki`** (persist it locally first), **`tweak`** (plan the fix if it's non-trivial), **`git-actions`** (branch / commit / push / MR), and **`mr-review`** (drive the review-thread fix loop). ## Before step 1 — ingest the card locally Persist the ClickUp card into the project's local wiki **before** writing any fix code, so the context survives. Hand off to **`local-wiki`** (it locates the wiki — prefers `docs/wiki/` — and obeys the wiki's own `AGENTS.md`). It fetches the card via **`clickup`** (`show_task.py <ID>` + `show_comments.py <ID>`) and writes the append-only raw corpus + rebuilds the topic page per the wiki's governance. ## Steps 1. **Branch first.** Before writing any code, ask which **base branch — develop or main**. Create the working branch from that base, named `fix/{clickup_id}` (e.g. `fix/TUKS-490`). Use **`git-actions`** for the branch. 2. **Fix the issue on that branch.** If the fix is non-trivial, plan it with **`tweak`** first. 3. **Do not open a merge request on your own.** Only create the MR — targeting **develop** — when the user explicitly asks for it. 4. **After the MR exists, wait for the `ai_code_review` pipeline to finish.** It's injected by an included CI template (so it won't appear in the repo's own `.gitlab-ci.yml`); poll via `glab ci list` (filter by branch ref) or `glab mr view <iid>`. 5. **Work through eve