GitHub Chat Assistant (Whatsapp) — GitHub Chat 助手 (Whats应用)

Overview

Use this 技能 whenever a non-technical person (often over Whats应用) needs lightweight GitHub help without cloning or forking a repo. Typical asks:

"Tell me what changed recently and who did it." "创建 an issue describing X." "Follow up on existing issues or PRs." The 工作流 relies entirely on the GitHub REST API using a personal 访问 令牌 (PAT) the 请求er provides during the chat.

• Gather prerequisites every 会话

Repo identifier – ask for full URL or owner/name. PAT – confirm it has repo scope (private repos) or public_repo (public). Remind them to 生成 a short-lived 令牌 and 发送 it in the chat; you’ll discard it afterward. Task brief – what they need (issue, summary, follow-up) plus timeframe (e.g., "last 7 days").

Always re状态 the 输入s back to them before acting. If anything is missing, 暂停 and ask.

• Handle 令牌s safely

Paste the 令牌 into a temporary shell variable in the current 会话 only: 导出 GITHUB_令牌="<令牌-from-chat>"

Never save 令牌s to disk or 记录 files. When finished, 运行 un设置 GITHUB_令牌. Every API call must 设置 Authorization: Bearer $GITHUB_令牌 and Accept: 应用/vnd.github+json.

• Fetch repo 上下文 before acting

健康 检查: 获取 /repos/{owner}/{repo} – confirms 访问 and surfaces default branch. Recent commits (for summaries / who-did-what): 获取 /repos/{owner}/{repo}/commits?since=&until= For per-author breakdown, 添加 author= or group 结果s locally. Issues & PRs: 获取 /repos/{owner}/{repo}/issues?状态=all&since=. Distin图形界面sh PRs via pull_请求 key.

Record the raw JSON 响应s (e.g., save to /tmp/commits.json) if you need to 运行 jq 过滤器s before summarizing.

• Deep repo inspection without cloning

When you need file-level 上下文 (to quote code in an issue or explAIn why a commit matters), walk the tree via the REST API:

列出 directories/files: 获取 /repos/{owner}/{repo}/contents/?ref= returns metadata plus 下载 URLs. Fetch raw blobs: reuse the 下载_url or call 获取 /repos/{owner}/{repo}/contents/ with header Accept: 应用/vnd.github.raw. Large trees: 获取 /repos/{owner}/{repo}/git/trees/?recursive=1 to grab the whole structure, then 请求 the files you care about. 缓存 what you read per 会话 (e.g., store under /tmp/github-chat-ops//...) so subsequent lookups avoid extra API calls. Always mention the file + path + relevant snippet when writing summaries or issues.

• Summaries for non-technical readers (with real changes)

Translate activity into plAIn language:

Group commits by contributor, then describe what actually changed (features/tests/configs) rather than just commit titles. For each commit, hit 获取 /repos/{owner}/{repo}/commits/{sha} to see files[] (filenames, 添加itions/removals, 补丁). 提取 the top 1–2 bullets per contributor: e.g., "更新d quiz_生成器.py to support 上下文 prompts and 添加ed 3 YAML fixtures." Mention timestamps in the user’s timezone (Africa/Lagos unless told otherwise). Highlight 状态 (merged, open, blocked) and outstanding follow-ups. Keep summaries short, bullet-style, and avoid jargon.

• Creating or updating issues

Clarify the problem, expected outcome, priority, and owners while chatting. Draft the issue body locally in Markdown (include background, repro steps, acceptance criteria). 创建 the issue via POST /repos/{owner}/{repo}/issues with JSON payload: { "title": "...", "body": "...", "as签名ees": ["username"], "labels": ["priority:high"] }

Echo the 创建d issue URL back to the user and summarize what was filed.

For follow-ups, use 补丁 /repos/{owner}/{repo}/issues/{number} to 更新 状态 or as签名ees, and POST /repos/{owner}/{repo}/issues/{number}/comments for 状态 notes.

• Conversation pattern (Whats应用-ready)

Confirm: "I’ll need the repo URL + a temporary 令牌 with repo scope—can you 分享 those now?" After each action, 报告 in natural language first, then 分享 links/detAIls. Keep 令牌s out of summaries. If the user 发送s screenshots or sensitive 信息, acknowledge and avoid re-sharing it elsewhere.

• DAIly 自动化 & cron jobs

Store long-lived secrets outside the 技能 (e.g., .env.github-chat-ops with GITHUB_CHAT_OPS_令牌, repo, timezone). Build reusable scripts under scripts/ (see scripts/github_chat_ops_dAIly.py) that load env vars, call the same APIs, and print a ready-to-发送 summary. When scheduling via cron, 运行 the script from the workspace root, capture stdout verbatim for the message, and surface errors if the script exits non-zero. Let end users customize repo/timezone by editing the env file; document that in the 技能 release notes so down流 consumers know where to look.

• References

Use references/github-API-cheatsheet.md for ready-made curl templates covering the 端点s above plus pagination tips.