agentleFS
sodejmsodejm/portable-agent-repository-kit/.claude/skills/github-state-audit/SKILL.md

github-state-audit

Skill1 starsChanged 2 months agoApache-2.0View on GitHub

Produce a focused, read-only snapshot of GitHub issues, pull requests, reviews, checks, branches, and mergeability when hosted state matters.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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:

    Use only when current GitHub state is relevant and network access is authorized.

    line 8
  2. Distinctive:

    Never expose authentication output or credentials.

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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 state audit

Use only when current GitHub state is relevant and network access is authorized. This workflow is read-only.

  1. Confirm the repository and smallest relevant issue, PR, branch, or workflow.
  2. Query live GitHub state with gh or the GitHub API; do not substitute local or remembered state for current hosted evidence.
  3. Reconcile head/base commits, PR state, review decision, unresolved threads, required checks, mergeability, and branch protection as applicable.
  4. Distinguish missing evidence from a negative result and note the observation timestamp when the state may change.
  5. Report concise evidence and the next decision. Do not comment, rerun, label, close, merge, or otherwise mutate GitHub.

Never expose authentication output or credentials.

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.