agentleFS
Sign inStart free
claude-worldclaude-world/claude-agent/.claude/skills/github-ops/SKILL.md

github-ops

Skill5 starsChanged 8 months agoMITView on GitHub

Manage GitHub via the gh CLI — issues, pull requests, CI/CD runs, code review, releases, and raw API queries. Use when user asks about GitHub issues, PRs, CI status, merge requests, or GitHub Actions workflows.

  • Installs packages
  • Commits and pushes

23 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 3 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    Always check if CLI is installed and authenticated: gh auth status

    line 113
  2. Very specific:

    If not installed, show brew install gh && gh auth login and stop

    line 114
  3. Very specific:

    If not authenticated, show gh auth login and stop

    line 115
  4. Very specific:

    Default to the current repo (detected from git remote) unless user specifies <owner/repo>

    line 116
  5. Distinctive:

    When listing issues/PRs, show number, title, author, and date — limit to 10 by default

    line 117
  6. Very specific:

    When viewing PR diffs, truncate at 100 lines and save full diff to workspace/pr-<number>.diff

    line 118
  7. Distinctive:

    NEVER approve or merge a PR without the user explicitly confirming

    line 119
  8. Distinctive:

    Keep responses concise: action confirmation in 1-2 lines, details in collapsible sections when possible

    line 121

“Common” is measured: kept by at least 6 in 10 of the 19 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 Ops

Manage GitHub repositories using the gh CLI. Handles issues, PRs, CI runs, releases, and API queries.

Prerequisites

brew install gh
gh auth login

Choose GitHub.com, HTTPS, and authenticate via browser. Confirm with:

gh auth status

Commands

Issues

CommandDescription
gh issue listList open issues in current repo
gh issue list --repo <owner/repo>List issues in a specific repo
gh issue view <number>View issue details
gh issue create --title "..." --body "..."Create an issue
gh issue close <number>Close an issue
gh issue comment <number> --body "..."Comment on an issue
gh issue edit <number> --assignee "@me"Assign to yourself

Pull Requests

CommandDescription
gh pr listList open PRs
gh pr view <number>View PR details and diff
gh pr create --title "..." --body "..."Create a PR
gh pr merge <number> --squashMerge a PR (squash)
gh pr review <number> --approveApprove a PR
gh pr review <number> --request-changes --body "..."Request changes
gh pr comment <number> --body "..."Comment on a PR
gh pr checks <number>Show CI check status for a PR

CI / Actions

CommandDescription
gh run listList recent workflow runs
gh run view <run-id>View run details and logs
gh run rerun <run-id>Re-trigger a failed run
gh workflow run <workflow.yml>Manually trigger a workflow

Releases

CommandDescription
gh release listList releases
gh release create v1.0.0 --notes "..."Create a release
gh release view v1.0.0View release details

Raw API

gh api repos/<owner>/<repo>/issues      # List issues via API
gh api graphql -f query='...'           # GraphQL queries

Usage Examples

Create a bug report issue:

gh issue create \
  --title "Fix: null pointer in auth flow" \
  --body "Steps to reproduce: ..." \
  --label "bug" \
  --assignee "@me"

Check CI status for latest PR:

gh pr list --limit 1
gh pr checks <number>

Review a PR and request changes:

gh pr view 42
gh pr review 42 --request-changes --body "Please add tests for the edge case on line 87."

Trigger a manual workflow dispatch:

gh workflow run deploy.yml --field environment=staging

Rules

  • Always check if CLI is installed and authenticated: gh auth status
  • If not installed, show brew install gh && gh auth login and stop
  • If not authenticated, show gh auth login and stop
  • Default to the current repo (detected from git remote) unless user specifies <owner/repo>
  • When listing issues/PRs, show number, title, author, and date — limit to 10 by default
  • When viewing PR diffs, truncate at 100 lines and save full diff to workspace/pr-<number>.diff
  • NEVER approve or merge a PR without the user explicitly confirming
  • For code review, summarize the diff first, then provide specific line-level feedback
  • Keep responses concise: action confirmation in 1-2 lines, details in collapsible sections when possible

Download now (ZIP)

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