agentleFS
D-SheyD-Shey/autoharness/.agents/skills/github-update-checker/SKILL.md

github-update-checker

Skill10 starsChanged todayMITView on GitHub

Check latest available release or commits from GitHub repository using standard library urllib

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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 when checking whether a local Python CLI or package installation has newer releases or commits published to GitHub without third-party …

    line 9
  2. Distinctive:

    Run unit test with mocked HTTP response: verify semver comparison detects both newer and equal versions.

    line 27
  3. Distinctive:

    Run test with network error/timeout: verify graceful error handling without crashing the CLI.

    line 28

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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-update-checker

When to use

Use when checking whether a local Python CLI or package installation has newer releases or commits published to GitHub without third-party network dependencies.

Steps

  1. Determine repository coordinates (owner and repo name, e.g. D-Shey/autoharness).
  2. Construct request URL:
    • Primary: GitHub Releases API (https://api.github.com/repos/{owner}/{repo}/releases/latest).
    • Fallback: Raw file content (https://raw.githubusercontent.com/{owner}/{repo}/main/pyproject.toml).
  3. Set mandatory HTTP headers:
    • User-Agent: identification header (e.g. autoharness/{version}) required by GitHub API.
    • Accept: application/vnd.github.v3+json or application/json.
  4. Perform HTTP request via urllib.request.urlopen with a strict timeout (e.g. 5.0 seconds).
  5. Parse version from response:
    • From release tag: strip leading v (e.g. v1.0.0 -> 1.0.0).
    • From raw pyproject.toml: extract version = "..." via regular expression.
  6. Compare with local __version__ using tuple-based semver parsing tuple(int(x) for x in re.findall(r'\d+', v)).
  7. Return structured status: {"update_available": bool, "current_version": str, "latest_version": str, "release_url": str}.

How to verify

  1. Run unit test with mocked HTTP response: verify semver comparison detects both newer and equal versions.
  2. Run test with network error/timeout: verify graceful error handling without crashing the CLI.

Facts found here

  • GitHub API enforces a User-Agent header; missing User-Agent results in HTTP 403 Forbidden.

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.