gza-task-improvelisted

# Improve Gza Task Inline Address feedback for a gza task directly in the current conversation. Feedback can come from two sources: a completed review (Must-Fix items plus Suggestions) and/or unresolved task comments attached to the implementation. If no review exists but unresolved comments do, improve still runs — comments alone are a valid feedback source. This skill is useful when a task has reached max review/improve cycles and needs human-guided fixes, or when you want to interactively resolve feedback. ## Process ### Step 0: Capture the starting checkout Before touching task state, capture where the user started: ```bash git symbolic-ref --quiet --short HEAD || git rev-parse --short HEAD ``` Save this as `<START_CHECKOUT>`. You may switch to the implementation branch to make changes, but before finishing you must return the user to `<START_CHECKOUT>`. If `<START_CHECKOUT>` is a detached HEAD, restore it with `git checkout --detach <START_CHECKOUT>`. ### Step 1: Get task ID and find the feedback (review and/or unresolved comments) The user should provide a full prefixed task ID (for example, `gza-1234`). If they provide a review task ID, resolve it to the implementation task. If no task ID is provided, ask the user. Query the task, its most recent review, and any unresolved task comments: ```bash uv run python -c " import json, sys from pathlib import Path from gza.config import Config from gza.db import SqliteTaskStore config = Config.load(Path.cwd()) store