github-update-checker
Skill10 starsChanged todayMITView on GitHub
Check latest available release or commits from GitHub repository using standard library urllib
In this repository44 other files it gives its agents.
- llms-full.txtllms.txt
- llms.txtllms.txt
- ai-prompt-engineering-safety-reviewSkill
- ast-codemapSkill
- ast-grepSkill
- autoharnessSkill
- autonomous-backlog-driverSkill
- claude-kimi-mcp-normalizationSkill
- cli-self-updaterSkill
- code-frugalitySkill
- codemode-gatewaySkill
- codemode-typesSkill
- consequence-simulationSkill
- context-pruningSkill
- google-agents-cli-evalSkill
- google-agents-cli-scaffoldSkill
- history-searchSkill
- hook-gatingSkill
- hybrid-semantic-searchSkill
- kimi-code-agent-integrationSkill
- kimi-mcp-configurationSkill
- leann-vectorSkill
- log-summarizerSkill
- markdown-vagueSkill
- memory-reconciliationSkill
- mode-classificationSkill
- multiagent-orchestrationSkill
- output-compressionSkill
- prompt-injectionSkill
- python-anti-patternsSkill
- regression-sentinelSkill
- restart-trackingSkill
- rollback-guardSkill
- rust-call-graphSkill
- secrets-managementSkill
- security-best-practicesSkill
- session-compactorSkill
- sqlite-memorySkill
- swarm-barrierSkill
- swarm-dagSkill
- autoharnessSkill
- code-reliability-checksSkill
- skill-threat-rulesSkill
- autoharnessSkill
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
- Distinctive: line 9
Use when checking whether a local Python CLI or package installation has newer releases or commits published to GitHub without third-party …
- Distinctive: line 27
Run unit test with mocked HTTP response: verify semver comparison detects both newer and equal versions.
- Distinctive: line 28
Run test with network error/timeout: verify graceful error handling without crashing the CLI.
≈ “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.
Files
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
- Determine repository coordinates (owner and repo name, e.g.
D-Shey/autoharness). - 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).
- Primary: GitHub Releases API (
- Set mandatory HTTP headers:
User-Agent: identification header (e.g.autoharness/{version}) required by GitHub API.Accept:application/vnd.github.v3+jsonorapplication/json.
- Perform HTTP request via
urllib.request.urlopenwith a strict timeout (e.g. 5.0 seconds). - 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.
- From release tag: strip leading
- Compare with local
__version__using tuple-based semver parsingtuple(int(x) for x in re.findall(r'\d+', v)). - Return structured status:
{"update_available": bool, "current_version": str, "latest_version": str, "release_url": str}.
How to verify
- Run unit test with mocked HTTP response: verify semver comparison detects both newer and equal versions.
- 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.
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
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.

