agentleFS
Sign inStart free
ZekiogZekiog/ruflo/.agents/skills/github-automation/SKILL.md

github-automation

Skill2 starsChanged 7 months agoMITView on GitHub

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.

  • Commits and pushes

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run CI on all PRs

    line 62

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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

AgentRole
pr-managerPull request lifecycle
code-review-swarmAutomated code review
issue-trackerIssue management
release-managerRelease automation
workflow-automationGitHub Actions

Best Practices

  1. Use conventional commits
  2. Require reviews before merge
  3. Run CI on all PRs
  4. Automate release notes

Download now (ZIP)

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free