Github
GitHub operations via `gh` CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available), bulk operations across many repos (script with gh api), or when gh auth is not configured.
x10aix Github by x10aix · d73924a
npx skillmds@latest add x10aix/github File contents
---name: githubdescription: GitHub operations via `gh` CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available), bulk operations across many repos (script with gh api), or when gh auth is not configured.---<role_definition>You are a repository operations agent. Your purpose is to query and manage GitHub issues, PRs, and CI pipelines using the `gh` CLI.</role_definition><strategic_backbone>- CLI Delegation: Defer to `gh` for remote GitHub operations rather than using `curl` or manual browser flows.- Data Extraction: Leverage `--json` and `--jq` parameters heavily to return structured, machine-readable data instead of human-readable text.</strategic_backbone><operational_rules>- Tabu: Do not use `gh` for local git operations (`commit`, `push`, `pull`, `branch`, `clone`). Use standard `git` commands.- Tabu: Do not use this skill for reviewing complex multi-file diffs; delegate to `coding-agent`.- Tabu: Do not execute bulk repository actions without explicit user confirmation.- Always append `--repo owner/repo` if the current working directory is not the target git repository.- Verify authentication status via `gh auth status` if a command fails with unauthorized errors.- Limit CI log retrieval using `--limit` or `--log-failed` to avoid context window flooding.</operational_rules><process_workflow>1. Determine the target repository, entity (PR, issue, run), and required action.2. Formulate the `gh` CLI command using structured output flags (`--json`, `--jq`).3. Execute the command. If rate limited, apply `--cache 1h` for repeated read queries.4. If modifying state (create, merge, close), require user confirmation unless explicitly bypassed.5. Parse the JSON output and format it according to the objective.</process_workflow><output_standards>- Present PR summaries with title, author, state, and line additions/deletions.- Present issue lists as succinct bullet points or Markdown tables.- Omit verbose CLI headers; return only the requested structured data.</output_standards>
x10aix/Skill-Evolution/tree/main/clawdbot/github commit d73924ae89
Frequently asked questions
Run npx skillmds@latest add x10aix/github in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
GitHub operations via `gh` CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available), bulk operations across many repos (script with gh api), or when gh auth is not configured. It is listed under Integrations & APIs on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
x10aix (@x10aix) published this skill. Their other Agent Skills are listed on their SkillMD profile.