Agent skill · Code Review & Quality

github-automation

GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.

rUv71,307★ · +1,002/wk · 3 repos on radarProfile →
claude-codecodexMIT
Install
npx skills add ruvnet/ruflo --skill github-automation --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 1 KB
Bundled scripts: none
Path: .agents/skills/github-automation/SKILL.md
Open the folder on GitHub →
Where it comes from
Source: ruvnet/ruflo
Stars: 67,015 · +629 this week
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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

What's inside
Steps it walks through
  1. Purpose
  2. When to Trigger
  3. Commands
  4. Create Pull Request
  5. Review Code
  6. Manage Issues
  7. Setup Workflow
  8. Release Management
  9. Agent Types
  10. Best Practices
Commands it runs
gh pr create --title "feat: description" --body "## Summary\n..."
npx claude-flow github review --pr 123
npx claude-flow github issues list --state open
npx claude-flow github issues create --title "Bug: ..."
npx claude-flow workflow create --template ci
npx claude-flow deployment release --version 1.0.0
More from ruflo
All skills →
security-auditComprehensive security scanning and vulnerability detection. Includes input validation, path…Securitysparc-methodologySPARC development workflow: Specification, Pseudocode, Architecture, Refinement, Completion. A…Documentationswarm-orchestrationMulti-agent swarm coordination for complex tasks. Uses hierarchical topology with specialized…Securitymemory-managementAgentDB memory system with HNSW vector search. Provides 150x-12,500x faster pattern retrieval…Data & Analyticsadr-verifyRead back adr-patterns + adr-edges namespaces, surface dangling refs / supersede cycles / status…Documentationagent-performance-monitorAgent skill for performance-monitor - invoke with $agent-performance-monitorAI & Agents
About this skill
What does the github-automation skill do?

GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.

How do I install it?

Run `npx skills add ruvnet/ruflo --skill github-automation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From ruvnet/ruflo, a repository with 67,015 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.