github-chat-ops

## Overview
Use this skill whenever a non-technical person (often over WhatsApp) needs lightweight GitHub help without cloning or forking a repo. Typical asks:
- "Tell me what changed recently and who did it."
- "Create an issue describing X."
- "Follow up on existing issues or PRs."
The workflow relies entirely on the GitHub REST API using a personal access token (PAT) the requester provides during the chat.

## 1. Gather prerequisites every session
1. **Repo identifier** – ask for full URL or `owner/name`.
2. **PAT** – confirm it has `repo` scope (private repos) or `public_repo` (public). Remind them to generate a short-lived token and send it in the chat; you’ll discard it afterward.
3. **Task brief** – what they need (issue, summary, follow-up) plus timeframe (e.g., "last 7 days").

_Always restate the inputs back to them before acting. If anything is missing, pause and ask._

## 2. Handle tokens safely
- Paste the token into a temporary shell variable in the current session only:
  ```bash
  export GITHUB_TOKEN="<token-from-chat>"
  ```
- Never save tokens to disk or log files. When finished, run `unset GITHUB_TOKEN`.
- Every API call must set `Authorization: Bearer $GITHUB_TOKEN` and `Accept: application/vnd.github+json`.

## 3. Fetch repo context before acting
1. **Health check**: `GET /repos/{owner}/{repo}` – confirms access and surfaces default branch.
2. **Recent commits** (for summaries / who-did-what):
   - `GET /repos/{owner}/{repo}/commits?since=<ISO8601>&until=<ISO8601>`
   - For per-author breakdown, add `author=<username>` or group results locally.
3. **Issues & PRs**: `GET /repos/{owner}/{repo}/issues?state=all&since=<ISO8601>`.
   - Distinguish PRs via `pull_request` key.

Record the raw JSON responses (e.g., save to `/tmp/commits.json`) if you need to run jq filters before summarizing.

## 4. Deep repo inspection without cloning
When you need file-level context (to quote code in an issue or explain why a commit matters), walk the tree via the RES...