Github Automation
Automate GitHub pull requests, issues, code review swarms, Actions workflows, and releases from your coding agent without leaving the repo.
Overview
GitHub Automation is an agent skill most often used in Ship (also Build integrations, Operate iterate) that automates GitHub PRs, issues, Actions workflows, and releases via gh and claude-flow.
Install
npx skills add https://github.com/ruvnet/ruflo --skill github-automationWhat is this skill?
- Creates PRs with gh and conventional-commit-friendly titles and bodies
- Runs claude-flow GitHub review and issue list/create commands from the agent
- Defines five agent roles: pr-manager, code-review-swarm, issue-tracker, release-manager, workflow-automation
- Scaffolds CI workflows via claude-flow workflow create --template ci
- Automates release versioning with claude-flow deployment release
- Documents 5 specialized GitHub agent roles
- Lists 4 best practices for reviews, CI, and releases
Adoption & trust: 656 installs on skills.sh; 58.5k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are shipping solo on GitHub but PRs, reviews, issues, and releases still mean jumping between the UI, shell snippets, and ad-hoc agent prompts.
Who is it for?
Indie builders using GitHub with gh and ruflo/claude-flow who want agent-driven PR and release hygiene.
Skip if: Local-only work, non-GitHub remotes, or teams that do not use GitHub Issues/Actions.
When should I use this skill?
PR creation, code review, issue management, release automation, or workflow setup on GitHub.
What do I get? / Deliverables
After running the skill, your agent can create PRs, drive review/issue automation, scaffold CI workflows, and cut releases with documented commands and role-specific swarms.
- Opened or updated pull requests with structured bodies
- CI workflow scaffold from template
- Versioned release via deployment release command
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Ship because the skill centers on PR lifecycle, required reviews, CI on every PR, and merge gates—not on writing application code. Review is the primary subphase: coordinated code review, PR creation, and pre-merge quality checks are the documented triggers.
Where it fits
Wire claude-flow GitHub agents into your repo so feature branches get PR templates and issue links automatically.
Spin up a code-review-swarm before merge when you cannot wait on a human reviewer.
Run deployment release with a semver tag after CI passes on the main branch.
File and triage production bugs via gh issue create while your agent tracks open state.
How it compares
Use as a procedural GitHub ops playbook, not a hosted MCP server that replaces the GitHub API.
Common Questions / FAQ
Who is github-automation for?
Solo and indie developers on GitHub who want their coding agent to handle PRs, issues, CI workflow setup, and release commands with gh and claude-flow.
When should I use github-automation?
Use it when creating pull requests, managing open issues, automating code review, configuring GitHub Actions CI, or running release automation; it also supports Build-phase integration work when wiring repo automation and Operate-phase iteration when cutting patch releases.
Is github-automation safe to install?
Treat it like any third-party skill: review the Security Audits panel on this Prism page and restrict agent permissions before running shell and GitHub commands against production repos.
SKILL.md
READMESKILL.md - Github Automation
# GitHub Automation Skill ## Purpose GitHub workflow automation, PR management, and repository coordination. ## When to Trigger - Creating pull requests - Managing issues - Setting up CI/CD workflows - Code review automation - Release management ## Commands ### Create Pull Request ```bash gh pr create --title "feat: description" --body "## Summary\n..." ``` ### Review Code ```bash npx claude-flow github review --pr 123 ``` ### Manage Issues ```bash npx claude-flow github issues list --state open npx claude-flow github issues create --title "Bug: ..." ``` ### Setup Workflow ```bash npx claude-flow workflow create --template ci ``` ### Release Management ```bash npx claude-flow deployment release --version 1.0.0 ``` ## Agent Types | Agent | Role | |-------|------| | `pr-manager` | Pull request lifecycle | | `code-review-swarm` | Automated code review | | `issue-tracker` | Issue management | | `release-manager` | Release automation | | `workflow-automation` | GitHub Actions | ## Best Practices 1. Use conventional commits 2. Require reviews before merge 3. Run CI on all PRs 4. Automate release notes