agentleFS
Sign inStart free
wundercorpwundercorp/loki/skills/software-development/github/SKILL.md

github

Skill28 starsChanged 2 months agoMITView on GitHub

GitHub via gh CLI: PRs, issues, reviews, repos, auth.

166 other projects use a version of this, 6 of them edited.

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

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

  • 0

    Common

    Most of the 151 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Prefer gh over raw REST; drop to gh api only for endpoints the porcelain lacks (the cheatsheet lists them).

    line 43
  2. Very specific:

    Never report CI green without checking gh pr checks yourself.

    line 45
  3. Very specific:

    Read full context before writing: gh issue view --comments / gh pr view --comments — decisions live in threads, not titles.

    line 47

“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

Work GitHub end to end with the gh CLI (REST fallback where noted): auth, issues, the PR lifecycle, issue-to-PR delivery, code review, and repo management. This skill consolidates six former skills; each workflow lives complete in its reference file — ALWAYS read the matching reference before starting that workflow, the body below only routes.

Routing

TaskRead first
Auth broken / new machine / token or SSH setup / gh loginreferences/auth.md
Create, triage, label, assign, close issuesreferences/issues.md
Branch, commit, open PR, watch CI, mergereferences/pr-workflow.md
Carry an ISSUE to a verified PR (full delivery loop)references/issue-to-pr.md
Review someone's PR: diffs, inline comments, verdictreferences/code-review.md
Clone/create/fork repos, remotes, releasesreferences/repo-management.md

Supporting assets: scripts/gh-env.sh + scripts/git-credential-token.py (auth helpers), templates/ (PR bodies, bug report, feature request), references/ci-troubleshooting.md, references/conventional-commits.md, references/github-api-cheatsheet.md, references/review-output-template.md.

Core discipline (applies to every workflow)

  • Preflight once per session: gh auth status — if it fails, go to references/auth.md before anything else.
  • Prefer gh over raw REST; drop to gh api only for endpoints the porcelain lacks (the cheatsheet lists them).
  • Never report CI green without checking gh pr checks yourself; never claim merged without verifying state,mergedAt.
  • Read full context before writing: gh issue view --comments / gh pr view --comments — decisions live in threads, not titles.
  • Sweep for duplicates before creating anything: gh pr list --search / gh issue list --search.

Verification

  • The workflow's own reference file defines done for that task.
  • Cross-cutting: every claim about remote state (CI, merge, release, issue state) is backed by a fresh gh read, never memory.

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