smithery/ruvnet

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.

Installation

$ npx skills add smithery/ruvnet --skill github-automation

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/ruvnet · top by installs.

npx skills add smithery/ruvnet

Browse all from smithery/ruvnet

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,471 B
  • docs SUMMARY.md 317 B

History

  1. First recorded snapshot · 0 installs

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

gh pr create --title "feat: description" --body "## Summary\n..."

Review Code

npx claude-flow github review --pr 123

Manage Issues

npx claude-flow github issues list --state open
npx claude-flow github issues create --title "Bug: ..."

Setup Workflow

npx claude-flow workflow create --template ci

Release Management

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