agentleFS
Sign inStart free
nb-99nb-99/skillektion/skills/gh-cli/SKILL.md

gh-cli

Skill1 starsChanged 3 months agoMITView on GitHub

Operate on GitHub from the terminal with the gh CLI. Use for GitHub repositories, issues, pull requests, reviews, Actions/workflow runs, releases, code scanning alerts, and code search.

  • Reads credentials
  • Commits and pushes

31 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agent-browser, web-design-guidelines and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • VercelSkill

    agent-browser

    Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

    Also in 5 projects that use this

  • VercelSkill

    web-design-guidelines

    Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

    Also in 5 projects that use this

  • MicrosoftSkill

    git-commit

    Stage user-selected paths, confirm the exact staged set, and create one local Conventional Commit, or generate a commit message for staged changes without committing. Use when you want a guarded commit or a ready-to-paste message.

    Also in 3 projects that use this

  • OpenAISkill

    using-git-worktrees

    Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

    Also in 3 projects that use this

  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 8 projects that use this

  • OpenAISkill

    executing-plans

    Use when you have a written implementation plan to execute in a separate session with review checkpoints

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the gh CLI for all GitHub operations.

    line 8
  2. Distinctive:

    Read freely. An explicit user request that names the GitHub target and a bounded write action authorizes that action.

    line 11
  3. Distinctive:

    Always confirm immediately before destructive, irreversible, privilege-changing, or materially broader work.

    line 15

“Common” is measured: kept by at least 6 in 10 of the 17 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 via the gh CLI

Use the gh CLI for all GitHub operations. gh api covers anything without a dedicated subcommand.

Read freely. An explicit user request that names the GitHub target and a bounded write action authorizes that action. Otherwise, show the exact mutation and ask for confirmation before running it.

Always confirm immediately before destructive, irreversible, privilege-changing, or materially broader work. This includes merges, closing or deleting content, publishing or deleting releases, changing access or secrets, and any action whose effects exceed the request. Recheck the repository and object identifier before every mutation.

Repos & info

gh repo view OWNER/REPO
gh api repos/OWNER/REPO
gh search repos "QUERY" --limit 10
gh search code "QUERY"            # cross-repo code search

Issues

gh issue list --repo OWNER/REPO --state open
gh issue view NUMBER --repo OWNER/REPO --comments
gh issue create --repo OWNER/REPO --title T --body B   # WRITE
gh issue comment NUMBER --body B                        # WRITE

Pull requests

gh pr list --repo OWNER/REPO
gh pr view NUMBER --comments
gh pr diff NUMBER
gh pr checks NUMBER                 # CI status
gh pr create --base main --head BRANCH --title T --body B   # WRITE
gh pr review NUMBER --approve|--request-changes -b B        # WRITE
gh pr merge NUMBER --squash                                 # HIGH-RISK: confirm

Actions / workflows

gh run list --repo OWNER/REPO --limit 10
gh run view RUN_ID --log
gh run view RUN_ID --log-failed     # only failed step logs
gh run rerun RUN_ID                 # HIGH-RISK: confirm
gh workflow list
gh workflow run WORKFLOW --ref BRANCH   # HIGH-RISK: confirm

Releases

gh release list --repo OWNER/REPO
gh release view TAG
gh release create TAG --notes N     # HIGH-RISK: confirm

Code scanning / security (via gh api)

gh api repos/OWNER/REPO/code-scanning/alerts --paginate
gh api repos/OWNER/REPO/code-scanning/alerts/ALERT_NUMBER
gh api repos/OWNER/REPO/dependabot/alerts --paginate

Tips

  • --json FIELDS --jq '...' for structured output: gh pr list --json number,title,headRefName --jq '.[] | .title'.
  • gh api --paginate to traverse all pages.
  • Authentication uses the existing gh auth session / $GITHUB_TOKEN.

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