GitHub

GitHub with Grok Bot

Sets the boundary for a GitHub connection: read a repo you choose, draft a summary, do not push.

Open Grok Bot, paste the instruction below, add your own details, then you review and send yourself.

Start here

Paste into Grok Bot

Copy this instruction into Grok Bot. Replace blanks with your own names and dates before you rely on a draft.

You answer questions about a GitHub repo the human can already access. You do not push, merge, or invite collaborators.

If a GitHub plugin is connected, they name the repo and the question (what changed, what is risky, what to try next).
You:
1. Stay inside that repo.
2. Summarize in plain language and point at file paths they can open.
3. Refuse to print secrets, tokens, or .env values. If a diff contains one, tell them to rotate it.
4. Do not open a pull request unless they paste the exact change and say "draft only". Even then, they push.

If the plugin is off, they paste a diff or a file. Same rules.
Never ask them to paste a personal access token.

What this does not do

It does not merge pull requests, store personal access tokens, or replace a code review by a human.

How often

Each day

One repo question per working session. Paste the diff if the answer looks invented.

Each week

Disconnect the GitHub plugin if you did not use it.
Rotate any token that touched a chat.

Plugins

Tool. GitHub can show a repository you choose. This playbook asks for a summary from read access. It does not need permission to push or merge.

A GitHub connection with read access to repos you choose. Write access is unnecessary for this playbook.

Paste the diff or the file. For a frontend skill, paste the SKILL.md from the MeloSkill listing instead of connecting GitHub.

Risks and limits

Tokens in chat leak. Do not paste them. If you did, revoke the token.
A summary can miss a bug. Read the diff before you merge.
MeloSkill is not affiliated with GitHub, xAI, Grok, or Grok Bot.

FAQ

Should I paste a personal access token so the bot can see private repos?

No. Use the product’s GitHub connection with the smallest access, or paste a diff. A token in chat is a leak. If you already pasted one, revoke it.

Will this merge pull requests?

No. It drafts a summary of a repo you choose. You read the diff before you merge. Write access is unnecessary for this playbook.

What if I do not connect GitHub?

Paste the diff or the file. For a frontend skill, paste the SKILL.md from the skills index instead of connecting GitHub.

Is a summary the same as a code review?

No. A summary can miss a bug. A person still reviews the change. Check a bot’s permissions first on box inspector.