ios-libs-issuelisted

# iOS Libs Issue Skill File a well-formed GitHub issue against the iOS lib repo configured in `tusk/config.json` (`project_libs.ios_app.repo`) without leaving the workflow. The originating tusk task summary, tusk version, and a link back to the local task are auto-attached so the upstream issue stays connected to the work that surfaced it. This skill is content-only — there are no `bin/tusk` hooks to invoke. Adding the same flow for another platform (e.g. `android-libs-issue`) is a copy-edit job that touches only this file's sibling. ## Step 1: Resolve the Originating Local Task The skill is invoked from a tusk client repo while the user is in the middle of work that surfaced a bug or gap in the iOS lib. Determine the originating task ID: 1. If the user invoked `/ios-libs-issue <id>` with an explicit ID, use it. 2. Otherwise parse it from the current branch: ```bash TASK_ID=$(tusk branch-parse | python3 -c 'import json,sys; print(json.load(sys.stdin).get("task_id") or "")') ``` 3. If neither produces a task ID, prompt: > No tusk task detected from `/ios-libs-issue <id>` or the current branch. Provide a task ID, or type `cancel` to abort. Once the ID is in hand, fetch the task so its summary can be embedded in the issue body: ```bash tusk task-get "$TASK_ID" ``` Record `task.summary` and `task.id` for Step 4. ## Step 2: Resolve the iOS Lib Repo from Config The lib repo is **never hard-coded**. Read it from `project_libs.ios_app.repo` at runtime: ```bash