github-automation

Automate GitHub repositories, issues, pull requests, and CI/CD workflows via Rube MCP.

1|Updated Jul 20, 2026
One-click install
npx skills add https://github.com/gonzoblasco/ai-developer-stack --skill github-automation-gonzoblasco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-automation
Source: https://github.com/gonzoblasco/ai-developer-stack/tree/main/tools-automation/github-automation
Command: npx skills add https://github.com/gonzoblasco/ai-developer-stack --skill github-automation-gonzoblasco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing GitHub repositories, issues, pull requests, branches, and CI/CD pipelines manually through the web UI is slow and repetitive. This Skill lets you perform all of these operations programmatically through Composio's GitHub toolkit via Rube MCP, directly from your AI assistant. ## Core Features & Use Cases - Issue and PR Management: Create, list, search, comment on, and merge issues and pull requests with safety checks like mergeable status verification and explicit confirmation before merging. - Repository and Branch Operations: Create personal or organization repositories, manage branches via git references, and update repository settings. - CI/CD and Permissions: List and trigger GitHub Actions workflows, check CI status on commits, manage deployments, and inspect collaborators and branch protection rules. - Use Case: Ask your assistant to review an open PR, verify its CI checks pass, and merge it with the squash method after your approval — all in one conversation. ## Quick Start Connect the Rube MCP server, activate the GitHub toolkit connection, then ask the assistant to list open pull requests in your repository and summarize their CI status.

Frequently Asked Questions about github-automation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub pull requests with an AI assistant?▼

Connect Rube MCP and activate the GitHub toolkit, then use tools like GITHUB_FIND_PULL_REQUESTS, GITHUB_GET_A_PULL_REQUEST, and GITHUB_MERGE_A_PULL_REQUEST. Always verify mergeable status and require explicit confirmation before merging.

How to trigger a GitHub Actions workflow programmatically?▼

Use GITHUB_CREATE_A_WORKFLOW_DISPATCH_EVENT with the workflow ID or filename and a target ref. The workflow must have a workflow_dispatch trigger configured, and inputs are limited to 10 key-value pairs matching its definition.

Does GitHub issue listing also return pull requests?▼

Yes, GITHUB_LIST_REPOSITORY_ISSUES returns both issues and pull requests because GitHub treats PRs as issues internally. Check the pull_request field on each item to distinguish between them.

Why does creating a GitHub branch fail with a 422 error?▼

GITHUB_CREATE_A_REFERENCE returns 422 when the reference already exists or the ref format is invalid. The ref must start with 'refs/' and contain at least two slashes, such as 'refs/heads/new-branch'.

What are the limits of GitHub code search via API?▼

Code search only indexes files under 384KB on the default branch and returns a maximum of 1000 results. Commit search additionally requires text keywords alongside qualifiers; qualifier-only queries are rejected.