agentleFS
Sign inStart free
codewhale-hqcodewhale-hq/codewhale-plugin-marketplace/skills/github/SKILL.md

github

Skill5 starsChanged 16 days agoMITView on GitHub

GitHub via gh — issues, PRs, reviews, search, and CI runs. Use when: user mentions a repo, issue, PR, review, release, workflow run, or anything on github.com.

  • Commits and pushes

166 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use taskflow-inbox-triage, BlueBubbles and 10 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.
  • AtomicBot-aiSkill

    taskflow-inbox-triage

    Also in 6 projects that use this

  • jiulingyunSkill

    BlueBubbles

    为Clawdbot构建或更新BlueBubbles外部通道插件（扩展包，REST发送/探测，webhook入站）。

    Also in 20 projects that use this

  • hkyutongSkill

    node-connect

    Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale, or plugins.entries.device-pair.config.publicUrl.

    Also in 18 projects that use this

  • molt-botSkill

    discord-e2e

    Test Discord with Convex-leased QA bots: check credentials without a Gateway, exercise owned messages, or prove OpenClaw replies, files, threads, reactions, streaming, and typing. Distinguish API and Gateway evidence from manual user interactions.

    Also in 10 projects that use this

  • molt-botSkill

    openclaw-repair-sweep

    Run scoped OpenClaw issue/PR repair campaigns: coordinate workers, prove root causes, and land or close verified work under the requested authority.

    Also in 10 projects that use this

  • clawdbotSkill

    openclaw-performance

    Performance work in OpenClaw: a slow or heavy flow (latency, CPU, memory, SQL, RPC, renders), writing or reviewing a perf PR, or adding a cache. Count the work, delete waste first, cache last.

    Also in 7 projects that use this

  • +2 more from molt-bot

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 151 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    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:

    Never proceed with curl against api.github.com as a silent fallback — gh owns auth, pagination, and output shape.

    line 20
  2. Very specific:

    Read: gh issue view, gh pr view, gh pr diff, gh search, gh run view.

    line 25
  3. Distinctive:

    Do not merge, close, or approve on your own initiative.

    line 31
  4. Distinctive:

    Do not invent issue/PR numbers or check conclusions.

    line 32
  5. Distinctive:

    Do not push, retag, or rewrite history without explicit authorization.

    line 33

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

When to use

Any GitHub work: read or triage issues, open or review PRs, search code, check CI runs, manage releases.

Setup

Requires the gh CLI, authenticated. Fail loud when it is missing:

gh auth status || gh auth login

Never proceed with curl against api.github.com as a silent fallback — gh owns auth, pagination, and output shape.

Workflow

  1. Confirm the repo (owner/name) and, for mutations, the exact target.
  2. Read: gh issue view, gh pr view, gh pr diff, gh search, gh run view.
  3. Mutate only when asked: gh issue create, gh pr create, gh pr review, gh pr merge. Mutations need explicit user intent, not inference.
  4. Quote what gh returned; never summarize a diff or check rollup you did not read.

Non-goals

  • Do not merge, close, or approve on your own initiative.
  • Do not invent issue/PR numbers or check conclusions.
  • Do not push, retag, or rewrite history without explicit authorization.

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