github-automation

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