github
Skill6 starsChanged 8 months agoMITView on GitHub
Interact with GitHub using the GitHub CLI (gh). Use when the user asks to create repos, manage issues, pull requests, releases, gists, browse code, manage labels/milestones, review PRs, or perform any GitHub operation. Also use for reading issue details, commenting, searching issues/PRs, and checking CI status.
- Commits and pushes
176 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- t128n/skillstheir own version, first seen Nov 16, 2026
- dwesh163/nextjs-skilltheir own version, first seen Nov 16, 2026
- zkManuel0123/CodexClawtheir own version, first seen Nov 16, 2026
- br3eze-code/br3eze-codetheir own version, first seen Nov 16, 2026
- fworks-tech/agenthoodtheir own version, first seen Nov 15, 2026
- heymegabyte/claude-skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use taskflow-inbox-triage, creative-project and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AtomicBot-aiSkilltaskflow-inbox-triage
Also in 6 projects that use this
openclawSkillcreative-project
Design or revise branding, visual identities, logos, posters, illustrations, and social-media assets using project artwork or image references. Inspect the existing visual language, choose references, and iterate on named candidates.
Also in 5 projects that use this
openclawSkilllabs-graduation
Move a feature out of Control UI Labs, either on by default or still off by default. Use when asked to promote, graduate or ship a Labs feature.
Also in 5 projects that use this
jiulingyunSkillBlueBubbles
为Clawdbot构建或更新BlueBubbles外部通道插件(扩展包,REST发送/探测,webhook入站)。
Also in 22 projects that use this
hkyutongSkillnode-connect
Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale, or plugins.entries.device-pair.config.publicUrl.
Also in 18 projects that use this
friuns2Skilldiscord-e2e
Test Discord with Convex-leased QA bots: check credentials without a Gateway, exercise owned messages, or prove OpenClaw replies, files, threads, reactions, streaming, and typing. Distinguish API and Gateway evidence from manual user interactions.
Also in 10 projects that use this
Other versions176 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- jholhewres/devclaw-skills★ 419% same
Wrote their own version · 175
- molt-bot/clawdbot★ 395ksame name
- steipete/warelay★ 395ksame name
- moltbot/clawdbot★ 395ksame name
- openclaw/openclaw★ 395ksame name
- steipete/clawdis★ 394ksame name
- moltbot/moltbot★ 394ksame name
- clawdbot/clawdbot★ 394ksame name
- NousResearch/hermes-agent★ 264ksame name
- spinabot/brigade★ 11ksame name
- the-open-agent/openagent★ 5.7ksame name
165 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- find-skillsSkill
- public-tunnelSkill
- skill-creatorSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 0 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 159 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 205
Workspace repo management: All repos must be created, cloned, and managed from the repos/ folder of the workspace.
- Very specific: line 206
Private by default: When creating new repos, always use --private unless the user explicitly requests a public repo.
- Very specific: line 208
Always use
-R owner/repo: when operating on a repo other than the current working directory's repo. - Very specific: line 209
Branch safety: When creating PRs for bot-managed code changes, always use cp-* branch prefix.
- Very specific: line 210
Use
--jsonfor structured output: when you need to parse results programmatically:
“Common” is measured: kept by at least 6 in 10 of the 159 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
GitHub CLI
Perform GitHub operations using the gh CLI, which is pre-authenticated in the environment. This skill covers repositories, issues, pull requests, releases, gists, and the GitHub API.
Available Commands
Repositories
# List user's repos
gh repo list [owner] --limit 50
# Create a new repo (private by default; add --public only if explicitly requested)
gh repo create <name> --private [--description "desc"] [--clone]
# Clone a repo (always clone into the repos/ folder)
gh repo clone <owner/repo> repos/<repo>
# View repo info
gh repo view <owner/repo>
# Fork a repo (clone into repos/ folder)
gh repo fork <owner/repo> --clone -- repos/<repo>
# Delete a repo (REQUIRES user approval before executing)
gh repo delete <owner/repo> --yesIssues
# List issues
gh issue list [-R owner/repo] [--state open|closed|all] [--label "bug"] [--assignee @me]
# View issue details
gh issue view <number> [-R owner/repo]
# Create an issue
gh issue create [-R owner/repo] --title "Title" --body "Body" [--label "bug,urgent"] [--assignee "user"]
# Close an issue
gh issue close <number> [-R owner/repo] [--reason "completed"|"not_planned"]
# Reopen an issue
gh issue reopen <number> [-R owner/repo]
# Comment on an issue
gh issue comment <number> [-R owner/repo] --body "Comment text"
# Edit an issue
gh issue edit <number> [-R owner/repo] [--title "New title"] [--body "New body"] [--add-label "label"] [--add-assignee "user"]
# Pin/unpin an issue
gh issue pin <number> [-R owner/repo]
gh issue unpin <number> [-R owner/repo]
# Transfer an issue
gh issue transfer <number> <destination-repo> [-R owner/repo]Pull Requests
# List PRs
gh pr list [-R owner/repo] [--state open|closed|merged|all] [--author "user"] [--base main]
# View PR details
gh pr view <number> [-R owner/repo]
# Create a PR
gh pr create [-R owner/repo] --title "Title" --body "Body" [--base main] [--head feature-branch] [--draft] [--label "label"]
# Merge a PR
gh pr merge <number> [-R owner/repo] [--merge|--squash|--rebase] [--delete-branch]
# Review a PR
gh pr review <number> [-R owner/repo] --approve|--request-changes|--comment --body "Review text"
# Check PR status (CI checks)
gh pr checks <number> [-R owner/repo]
# Checkout a PR locally
gh pr checkout <number> [-R owner/repo]
# Close a PR without merging
gh pr close <number> [-R owner/repo]
# Comment on a PR
gh pr comment <number> [-R owner/repo] --body "Comment text"
# View PR diff
gh pr diff <number> [-R owner/repo]
# Edit a PR
gh pr edit <number> [-R owner/repo] [--title "New title"] [--body "New body"] [--add-label "label"] [--add-reviewer "user"]
# Mark PR as ready for review
gh pr ready <number> [-R owner/repo]Releases
# List releases
gh release list [-R owner/repo]
# Create a release (REQUIRES user approval before executing)
gh release create <tag> [-R owner/repo] --title "Title" --notes "Release notes" [--draft] [--prerelease]
# View a release
gh release view <tag> [-R owner/repo]
# Delete a release (REQUIRES user approval before executing)
gh release delete <tag> [-R owner/repo] --yesGists
# Create a gist
gh gist create <file> [--public] [--desc "description"]
# List gists
gh gist list
# View a gist
gh gist view <id>Search
# Search issues
gh search issues "query" [--repo owner/repo] [--state open] [--label "bug"]
# Search PRs
gh search prs "query" [--repo owner/repo] [--state open]
# Search repos
gh search repos "query" [--language typescript] [--sort stars]
# Search code
gh search code "query" [--repo owner/repo] [--language typescript]GitHub API (for anything not covered above)
# GET request
gh api repos/{owner}/{repo}
# POST request
gh api repos/{owner}/{repo}/labels -f name="priority" -f color="ff0000" -f description="High priority"
# GraphQL query
gh api graphql -f query='{ viewer { login } }'
# With JQ filtering
gh api repos/{owner}/{repo}/issues --jq '.[].title'
# Paginated listing
gh api repos/{owner}/{repo}/issues --paginate --jq '.[].title'Labels and Milestones
# List labels
gh label list [-R owner/repo]
# Create a label
gh label create "name" [-R owner/repo] --color "ff0000" --description "desc"
# Delete a label
gh label delete "name" [-R owner/repo] --yes
# Milestones (via API)
gh api repos/{owner}/{repo}/milestones --jq '.[].title'
gh api repos/{owner}/{repo}/milestones -f title="v1.0" -f due_on="2026-06-01T00:00:00Z"Workflow / CI
# List workflow runs
gh run list [-R owner/repo] [--workflow "ci.yml"]
# View a run
gh run view <run-id> [-R owner/repo]
# Watch a run in progress
gh run watch <run-id> [-R owner/repo]
# Re-run a failed workflow
gh run rerun <run-id> [-R owner/repo]Important Rules
- Workspace repo management: All repos must be created, cloned, and managed from the
repos/folder of the workspace. Always userepos/as the target directory for clone and fork operations. - Private by default: When creating new repos, always use
--privateunless the user explicitly requests a public repo. - Destructive operations require approval: Any potentially destructive operation — including deleting repos, deleting releases, deleting labels, force pushing, and any other irreversible action — MUST be confirmed with the user before executing. Never run these automatically.
- Always use
-R owner/repowhen operating on a repo other than the current working directory's repo. - Branch safety: When creating PRs for bot-managed code changes, always use
cp-*branch prefix. - Use
--jsonfor structured output when you need to parse results programmatically:gh issue list --json number,title,state,labels gh pr list --json number,title,state,headRefName - Use
--jqfor filtering JSON output directly:gh issue list --json number,title --jq '.[] | "\(.number): \(.title)"' - Pagination: For large result sets, use
--limitor--paginateto control output.
Examples
User: "What are the open bugs in my-app repo?"
→ gh issue list -R owner/my-app --label "bug" --state open --json number,title,assignees
User: "Create an issue for the login timeout problem"
→ gh issue create -R owner/my-app --title "Login timeout on slow connections" --body "..." --label "bug"
User: "Review the latest PR"
→ gh pr list -R owner/my-app --state open --limit 1 --json number,title → gh pr view <number> → gh pr diff <number>
User: "What's the CI status on PR #42?"
→ gh pr checks 42 -R owner/my-app
User: "Merge PR #42 with squash"
→ Confirm with user → gh pr merge 42 -R owner/my-app --squash --delete-branch
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

