Agent skill · software engineering · sickn33
github-automation
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.
Why this skill is useful
Adds specific commands and workflows for programmatically managing GitHub repositories that the AI wouldn't reliably generate on its own.
What it needs
Requires rube installed locally. Requires github account access. About 3k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
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 RUBESEARCHTOOLS is available. 2. Search for the current GitHub tool schemas before composing calls. 3. Use RUBEMANAGECONNECTIONS 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/github-automation--a57ae0