github-automation · sickn33 — Claude Code skill: GitHub ops via Rube MCP
github-automation drives GitHub issues, pull requests, branches, workflows and permissions through Rube MCP, and halts when repository policy points elsewhere.
MIT ★ 50,109 updated 2026-10-29
npx skills add sickn33/agentic-awesome-skills --skill github-automation -a claude-codeWhat github-automation does
GitHub work goes through Rube MCP, which exposes Composio's GitHub toolkit. The skill pulls current tool schemas with RUBE_SEARCH_TOOLS before building a call, and activates a github connection via RUBE_MANAGE_CONNECTIONS with OAuth if none exists yet. It never asks for your credentials or writes them anywhere.
Then comes the policy gate. It reads AGENTS.md along with contribution and maintainer docs, then looks at the default branch and its protection. When a repository ships its own guarded merge or release command, that command is the one to call: inside agentic-awesome-skills the skill points at antigravity-maintainer-batch-release and npm run merge:batch, which tie review to an exact SHA. A generic merge tool stays off the table unless policy allows it and you asked for the merge.
Expect friction in a few places. Rube tool names and schemas move, so discovery happens at runtime. Org permissions and external checks can block a call that looks fine. Deletion, force-push and protection edits need explicit sign-off, and the skill carries risk: critical.
What it helps with
- catch a duplicate issue before opening a new one
- pin a review to the full head SHA
- read failed job logs before touching the source
- check branch protection right before a merge
- show before-and-after state for a collaborator role change
Example prompts for the agent
- List open issues in
owner/repoand tell me whether one already covers the failing CI. - Open a PR from
fix/login, bind the review to the current head SHA, and show which required checks are still pending. - Dispatch
deploy.ymlwithworkflow_dispatchand report the run state once it reaches the end.
How to install github-automation
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill github-automation -a claude-code2Manually: put the files in place
~/.claude/skills/github-automation/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/github-automation/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill github-automation -a codex2Manually: put the files in place
.agents/skills/github-automation/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill github-automation -a cursor2Manually: put the files in place
.cursor/skills/github-automation/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install sickn33/agentic-awesome-skills skills/github-automation2Manually: put the files in place
.github/skills/github-automation/SKILL.md1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill github-automation -a gemini-cli2Platform CLI
gemini skills install https://github.com/sickn33/agentic-awesome-skills --path skills/github-automationManually: put the files in place
.devin/skills/github-automation/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill github-automation -a opencodeClaude.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-automation
How do I install github-automation in Claude Code?
Run npx skills add sickn33/agentic-awesome-skills --skill github-automation -a claude-code. The skill file lands at ~/.claude/skills/github-automation/SKILL.md.
What does github-automation do?
It runs GitHub issues, pull requests, branches, workflows and permission tasks through Rube MCP, checking repository policy and binding review decisions to a specific SHA.
When should I use gh instead?
When repository policy calls for it. The skill tells you to prefer the native gh workflow or a maintainer command in that case.
Source text
SKILL.md · MIT
--- name: github-automation description: "Operate GitHub issues, pull requests, branches, checks, workflows, and permissions through Rube MCP. Use when GitHub work must be queried or changed programmatically with repository-policy safeguards." risk: critical source: community date_added: "2026-02-27" --- # GitHub Automation via Rube MCP Use Composio's GitHub toolkit through Rube MCP while preserving repository policy, exact revision identity, and branch protection. ## When to Use Use for programmatic GitHub issue, pull-request, branch, Actions, deployment, collaborator, or protection tasks when Rube MCP is available. Prefer the native `gh` workflow or a repository-specific maintainer command when local repository policy requires it. ## Setup 1. Confirm `RUBE_SEARCH_TOOLS` is available. 2. Search for the current GitHub tool schemas before composing calls. 3. Use `RUBE_MANAGE_CONNECTIONS` with toolkit `github` and complete OAuth only if the connection is not active. 4. Resolve the exact `owner/repo`; do not rely on a similarly named repository. Never request, print, or persist GitHub credentials in prompts or artifacts. ## Repository Policy Gate Before mutation, read `AGENTS.md`, contribution and maintainer docs, then inspect the default branch and effective protection. Repository-native commands and required checks take precedence over generic Rube operations. If a repository provides a guarded merge or release command, use it instead of the generic merge tool. In `agentic-awesome-skills`, use `antigravity-maintainer-batch-release` and `npm run merge:batch` so exact-SHA review, fresh check-suite binding, and protected `main` are enforced. ## Workflows ### Issues 1. List or search existing issues before creating a duplicate. 2. Distinguish issues from pull requests in mixed results. 3. Read the current item, comments, labels, and linked PRs before changing state. 4. Create, comment, label, assign, or close only within the user's requested scope. 5. Re-read the item and verify the resulting state. Paginate until the requested result set is complete. Treat silent omission of labels or assignees as a permissions failure, not success. ### Pull requests 1. Resolve the PR and capture its number, base, full head SHA, draft state, author, fork identity, and mergeability. 2. Inspect changed files, reviews, conversations, and required check runs. 3. Bind every review or approval decision to the current full head SHA. 4. Create or update the PR body truthfully; never mark pending tests or reviews as completed. 5. Immediately before merge, re-read base/head identity, branch protection, mergeability, required checks, and repository policy. 6. Use the repository's guarded merge path. Call a generic merge tool only when policy permits it and the user authorized the merge. 7. Verify the PR reports `MERGED` and confirm the target branch contains the intended commit. Do not treat a successful API call that enables auto-merge or queues work as an immediate merge. ### Branches and references 1. Resolve the source commit SHA and target ref explicitly. 2. Create topic branches rather than updating protected/default branches directly. 3. Reject non-fast-forward or force updates unless the user explicitly authorizes them and repository policy permits them. 4. Confirm the remote ref after mutation. Deletion, force-push, default-branch changes, and protection changes are destructive or high-impact actions requiring explicit authorization. ### Actions and deployments 1. Resolve the workflow by trusted ID or path and confirm `workflow_dispatch` support before dispatch. 2. Bind run inspection to the intended event, ref, and head SHA. 3. Distinguish `queued`, `in_progress`, `action_required`, `completed`, and `skipped` states. 4. Read failed job logs before proposing source changes. 5. Wait for terminal success and verify the deployed or published surface separately. Do not approve fork workflow runs by raw run ID when the repository provides a guarded approval command. ### Permissions and protection 1. Read collaborators, role, branch protection, and applicable rulesets before proposing changes. 2. Treat a 404 protection response as “not configured” only after confirming repository and branch identity. 3. Show the exact before/after policy and impact before any protection or permission mutation. 4. Re-read effective state after the change. ## Failure Rules - Re-resolve tool schemas when Rube reports missing or changed parameters. - Stop on repository ambiguity, stale head/base SHA, missing permissions, incomplete pagination, or inconclusive protection state. - Never bypass required checks, reviews, merge queues, maintainer commands, or server-side branch protection. - Do not claim a merge, workflow, deployment, or permission change succeeded without reading the resulting remote state. ## Example **User request:** > Operate GitHub issues, pull requests, branches, checks, workflows, and permissions through Rube MCP. ## Limitations - Available Rube tool names and schemas can change; discover them at runtime. - GitHub permissions, organization policy, and external checks can block otherwise valid operations. - This skill does not authorize repository deletion, force pushes, protection changes, merges, deployments, or releases beyond explicit user intent.
© sickn33 · MIT · sickn33/agentic-awesome-skills
Similar skills
All skills for Git and GitHub →github-automation by other authors comes first.