Menu
General GitHub operations using the gh CLI. Search issues, read issue details, find pull requests, and manage labels.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Search older daily logs and memory files for past context via npx qmd
Create a GitHub issue from a Slack thread conversation. Analyzes the discussion, extracts key points, searches for related issues, and creates a well-structured issue.
Aliases for commonly used repositories. The agent can interact with any public GitHub repo, but these aliases provide shortcuts.
Review, audit, or summarize a GitHub pull request — fetch the diff, check for bugs/security/test/contract issues, post inline comments or approve/request-changes via `gh`, and report back to Slack. Use this whenever the user asks to review, look at, check, audit, summarize, "take a pass at", or give feedback on a PR (or shares a github.com/.../pull/<n> URL) — even if they don't use the word "review" explicitly.
Create a new runtime skill that persists across deploys. Use when the user asks to add a new capability, automate a workflow, or teach the bot a new behavior. Also use when the user says "learn how to..." or "remember how to..." for repeatable procedures.
Validate, commit, and push memory files to git
| name | github |
| description | General GitHub operations using the gh CLI. Search issues, read issue details, find pull requests, and manage labels. |
Use the gh CLI for all GitHub operations. The tool is pre-authenticated via GITHUB_TOKEN.
gh issue list --repo {repo} --search "<query>" --limit 10 --json number,title,url,state,labels
gh issue view {number} --repo {repo} --json title,body,comments,labels,state
gh issue create --repo {repo} --title "..." --body "..." --label "bug,enhancement" --assignee "username"
gh issue edit {number} --repo {repo} --add-label "bug,high" --add-assignee "username"
gh issue list --repo {repo} --label "bug" --state open --json number,title,url
gh pr list --repo {repo} --search "<query>" --json number,title,url,state
When you need to make changes to a repo and open a PR:
WORK=$(mktemp -d)
gh repo clone {owner}/{repo} "$WORK"
cd "$WORK"
git checkout -b {branch-name}
Branch naming: feat/, fix/, or chore/ prefix, kebab-case (e.g. fix/validate-timeout).
Edit files as needed. Always run the project's build and test commands before committing.
git add {specific-files}
git commit -m "Short imperative description"
git push -u origin HEAD
gh pr create --repo {owner}/{repo} --title "Short title" --body "$(cat <<'EOF'
## Summary
- <what changed and why>
## What could break
- <risks or side effects>
## How to test
- <steps to verify>
EOF
)"