agentleFS
Sign inStart free
sammcjsammcj/agentic-coding/Skills/github/SKILL.md

github

Skill167 starsChanged 10 days agoApache-2.0View on GitHub

You MUST always activate this github skill whenever working with GitHub in any capacity, including but not limited to gh cli, API, Actions, issues, PRs and other routine Github interactions.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 143 edited versions we read keep these.

  • 2

    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
  1. Very specific:

    Use the gh CLI tool for interacting with GitHub (issues, PRs, releases) and perform gh commands outside of the sandbox

    line 10
  2. Very specific:

    When when working with Github Actions, you should always check for and use the latest Actions versions that are at least 7 days old, you …

    line 11
  3. Distinctive:

    When you need to read line-level review comments with their resolved state (e.g.

    line 13
  4. Distinctive:

    When explicitly asked by the user to "close" or "resolve" a review comment, resolve the thread via the GraphQL mutation (do not reply to a …

    line 14

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

  • Use the gh CLI tool for interacting with GitHub (issues, PRs, releases) and perform gh commands outside of the sandbox
  • When when working with Github Actions, you should always check for and use the latest Actions versions that are at least 7 days old, you can use pinact run -update --min-age 7 to achieve this
  • For the general PR conversation timeline (not line-level review comments), use gh pr view --comments or the REST /issues/N/comments endpoint
  • When you need to read line-level review comments with their resolved state (e.g. triaging bot or human review feedback), fetch them via GraphQL in one call: gh api graphql -f query='query { repository(owner: "OWNER", name: "REPO") { pullRequest(number: N) { reviewThreads(first: 100) { nodes { id isResolved path line comments(first: 1) { nodes { author { login } body } } } } } } }' --jq '.data.repository.pullRequest.reviewThreads.nodes[] | select(.isResolved == false)'
  • When explicitly asked by the user to "close" or "resolve" a review comment, resolve the thread via the GraphQL mutation (do not reply to a comment unless instructed): gh api graphql -f query='mutation($id: ID!) { resolveReviewThread(input: { threadId: $id }) { thread { isResolved } } }' -f id="PRRT_..."
  • Thread IDs start with PRRT_. Use unresolveReviewThread to reopen
  • You can audit Github Actions security by running zizmor .

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