playbooks

home / skills / ruvnet / ruflo / github-automation

github-automation skill

/.agents/skills/github-automation

This skill automates GitHub workflow tasks, PR management, and issue tracking to streamline code review and release processes for teams.

npx playbooks add skill ruvnet/ruflo --skill github-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.4 KB
---
name: github-automation
description: >
  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.
---

# 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

Overview

This skill provides GitHub workflow automation for pull request lifecycle, issue tracking, code review coordination, and release management. It integrates with GitHub Actions and repository management tools to automate repetitive tasks and enforce repository policies. Use it to streamline PR creation, run automated review swarms, and orchestrate release workflows across teams.

How this skill works

The skill inspects repository state, open PRs, issues, and CI workflow configuration, then executes declarative commands to create PRs, manage issues, set up workflows, and publish releases. It coordinates specialized agents (pr-manager, code-review-swarm, issue-tracker, release-manager, workflow-automation) to distribute responsibilities and run automated checks. Actions can be triggered manually or via event hooks to GitHub Actions for continuous automation.

When to use it

  • Creating or updating pull requests that need templates, reviewers, or CI labels
  • Automating code reviews using an ensemble of automated reviewers before human review
  • Managing issue triage, labeling, and bulk updates across repositories
  • Setting up or modifying CI/CD workflows and GitHub Actions templates
  • Coordinating release tasks: changelogs, version bumps, and publishing artifacts

Best practices

  • Adopt conventional commits so automation can infer changelog entries and release types
  • Require at least one human review before merge and run CI on every PR
  • Keep workflow templates in a central folder and reuse templates across repos
  • Automate release notes generation and tag creation to reduce human error
  • Limit agent privileges: grant only required repo scopes for automation tokens

Example use cases

  • Create a standardized PR with branch, title, body template, labels, assignees, and required reviewers
  • Run an automated review swarm to surface style, security, and test coverage issues before human review
  • Bulk-close or re-label stale issues and create follow-up tasks for maintainers
  • Bootstrap CI using a provided template and validate workflows across multiple repositories
  • Perform a release: bump version, generate changelog from commits, tag and publish artifacts

FAQ

Which repositories should I not use this skill on?

Skip this skill for local-only changes or projects hosted outside GitHub, since it requires GitHub API and Actions access.

What permissions are required for the automation token?

Provide granular repo scopes: read/write issues, pull requests, workflows, and releases. Avoid granting org-wide admin if not necessary.