gza-task-infolisted

# Gza Task Info Gather comprehensive information about a specific gza task, including database details, git branch status, commits, and execution logs. ## Process ### Step 1: Get task ID The user should provide a full prefixed task ID (for example, `gza-1234`). Extract it from the input. ### Step 2: Query task from database Run a Python one-liner to get all task details as JSON: ```bash uv run python -c "from gza.db import get_task; import json; print(json.dumps(get_task(<ID>), indent=2, default=str))" ``` This will show: - id, prompt, status, task_type, task_id (slug) - branch, log_file, report_file - has_commits, duration_seconds, num_turns_reported, num_turns_computed, cost_usd - created_at, started_at, completed_at - tags, depends_on, based_on, spec - create_review, same_branch, task_type_hint - output_content, session_id ### Step 3: Check branch status (if task has a branch) If the task has a branch field set, gather git information. First, determine the base branch by running `git rev-parse --abbrev-ref @{upstream} 2>/dev/null | sed 's|.*/||'`. If that fails (no upstream set), fall back to `main`. Store this as `BASE_BRANCH`. 1. **Check if branch exists:** ```bash git branch -a | grep <branch-name> ``` 2. **Show recent commits on the branch:** ```bash git log <branch-name> --oneline -10 ``` 3. **Check if branch is merged to base branch:** ```bash git branch --merged $BASE_BRANCH | grep <branch-name> || echo "Not merged to $BASE_BRAN