github-workflowlisted

# GitHub workflow Manual-only workflow authored by Vraj. It is complete and standalone: use the active host's documented connector, API, or CLI, and never assume a particular harness, model, extension, or sibling skill is installed. ## Authority and scope - Treat repository, issue, pull request, review, and CI inspection as read-only unless the user explicitly authorizes a write. - Commit, push, posting comments, changing labels, retrying CI, and creating or updating a pull request are external writes. Perform each only when the user's instruction clearly grants that action; do not infer it from “fix”, “review”, or “prepare”. Never merge or force-push without separate explicit authority. - Resolve the exact repository, ref, item number, and target before acting. If any is ambiguous, ask instead of guessing. Never claim an action, check, or log that was not actually observed. ## Select a capability 1. Discover the active host's available connector, API, and CLI capabilities. 2. Prefer a structured connector or API for repository metadata, issues, pull requests, comments, reviews, labels, reactions, and check results. 3. Use local git for checkout status, branches, diffs, and commits. Use the host's documented GitHub CLI for gaps such as current-branch PR discovery, remote checks, and workflow logs. 4. If no capability can perform the requested operation, report the blocker and offer a safe read-only alternative. Do not invent commands or route to