github · sammcj — Claude Code skill: GitHub workflows
This skill sets rules for using gh to work with GitHub, from reading PR feedback to checking GitHub Actions. It fits tasks involving issues and code review.
Apache-2.0 ★ 173 updated 2026-10-24
npx skills add sammcj/agentic-coding --skill github -a claude-codeWhat github does
The skill directs Claude Code to use gh for issues, pull requests, and releases, with commands run outside the sandbox. For a PR’s general discussion it points to gh pr view --comments or the REST endpoint; line-level review feedback and thread state are fetched in one GraphQL request.
For GitHub Actions, the skill calls for versions that have been available for at least 7 days. It gives pinact run -update --min-age 7 as an update command and zizmor . for a security audit. Running gh inside the sandbox conflicts with its instructions.
A review thread should be resolved through a GraphQL mutation only when the user explicitly asks; the skill says not to reply to a comment otherwise. To reopen a thread, use unresolveReviewThread.
What it helps with
- read general discussion on a pull request
- find unresolved line-level review threads
- update GitHub Actions versions based on release age
- audit GitHub Actions for security issues
- resolve a review thread when asked
Example prompts for the agent
- Read the general discussion on this pull request using
gh. - Find unresolved line-level review threads and show who left them.
- Audit the GitHub Actions configuration for security issues.
How to install github
1Skills CLI (Vercel)
npx skills add sammcj/agentic-coding --skill github -a claude-code2Manually: put the files in place
~/.claude/skills/github/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/github/
1Skills CLI (Vercel)
npx skills add sammcj/agentic-coding --skill github -a codex2Manually: put the files in place
.agents/skills/github/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add sammcj/agentic-coding --skill github -a cursor2Manually: put the files in place
.cursor/skills/github/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install sammcj/agentic-coding Skills/github/SKILL.md2Manually: put the files in place
.github/skills/github/SKILL.md1Skills CLI (Vercel)
npx skills add sammcj/agentic-coding --skill github -a gemini-cli2Platform CLI
gemini skills install https://github.com/sammcj/agentic-coding --path Skills/githubManually: put the files in place
.devin/skills/github/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about github
How do I install github in Claude Code?
Run npx skills add sammcj/agentic-coding --skill github -a claude-code. The skill file is at ~/.claude/skills/github/SKILL.md.
What does the github skill do?
It sets instructions for GitHub tasks with gh, including PR discussion, review threads, and GitHub Actions checks.
How does the skill handle GitHub Actions versions?
It calls for versions that have been available for at least 7 days. The suggested update command is pinact run -update --min-age 7.
Source text
SKILL.md · Apache-2.0
---
name: github
description: You MUST always activate this github skill whenever working with GitHub in any capacity, including but not limited to gh cli, API, Actions, issues, PRs and other routine Github interactions.
metadata:
info: I moved these out of my global agent rules to save a few tokens
---
# GitHub
- Use the `gh` CLI tool for interacting with GitHub (issues, PRs, releases) and perform `gh` commands outside of the sandbox
- When when working with Github Actions, you should always check for and use the latest Actions versions that are at least 7 days old, you can use `pinact run -update --min-age 7` to achieve this
- For the general PR conversation timeline (not line-level review comments), use `gh pr view --comments` or the REST `/issues/N/comments` endpoint
- When you need to read line-level review comments with their resolved state (e.g. triaging bot or human review feedback), fetch them via GraphQL in one call: `gh api graphql -f query='query { repository(owner: "OWNER", name: "REPO") { pullRequest(number: N) { reviewThreads(first: 100) { nodes { id isResolved path line comments(first: 1) { nodes { author { login } body } } } } } } }' --jq '.data.repository.pullRequest.reviewThreads.nodes[] | select(.isResolved == false)'`
- When explicitly asked by the user to "close" or "resolve" a review comment, resolve the thread via the GraphQL mutation (do not reply to a comment unless instructed): `gh api graphql -f query='mutation($id: ID!) { resolveReviewThread(input: { threadId: $id }) { thread { isResolved } } }' -f id="PRRT_..."`
- Thread IDs start with `PRRT_`. Use `unresolveReviewThread` to reopen
- You can audit Github Actions security by running `zizmor .`
© sammcj · Apache-2.0 · sammcj/agentic-coding
Similar skills
All skills for Git and GitHub →github by other authors comes first.