github-clilisted

# GitHub CLI Skill Use the instance and rules below when constructing all `gh` commands. ## Instance All `gh` CLI and `git` operations use host: `github.com` ### Prerequisites (one-time setup by user) If not already authenticated, inform the user that authentication is required and ask them to complete the following steps manually. Do not perform these steps yourself. 1. Install the `gh` CLI if not already installed: ```bash brew install gh ``` 2. Run the following command to authenticate with GitHub: ```bash gh auth login ``` ## PR Code Review When asked to review a GitHub PR (URL or PR ID provided), extract the `<owner/repo>` and `<PR_ID>` from the URL (ask the user if the repo is missing), then use `gh api` to fetch the PR metadata (`repos/<owner>/<repo>/pulls/<PR_ID>`) and its diff (`repos/<owner>/<repo>/pulls/<PR_ID>/files --paginate`). To fully understand the context and impact of all code changes, read the complete source branch codebase — the diff alone does not capture the surrounding logic, dependencies, or broader design that the changes interact with. Report the PR title, author, and branches, then review all changed files for: secrets/injection/XSS (security), inefficient algorithms/memory leaks (performance), code smells/dead code (quality), missing error handling, excessive or sensitive logging, and missing/outdated documentation. For each finding, include the file path, line number(s), the problematic snippet, and a suggested fix. If nothing is wron