upstream-sync
Skill1 starsChanged 14 days agoMITView on GitHub
Checks upstream repos and packages referenced by the skills (github.com/lrstanley first, then other libraries and tools) for new features, changes, and deprecations, and updates skill docs to match. Use when asked to sync, refresh, or audit skills against upstream changes.
9 other projects use a version of this.
Adopted by
Most recently taken up by
- ilien-dev/quirontheir own version, first seen Nov 8, 2026
- Blueforce-Tech-Inc/BlueCortexCEtheir own version, first seen Nov 8, 2026
- shruthis4/claude-skillstheir own version, first seen Oct 20, 2026
- halo-box/strix-llama.cpptheir own version, first seen Oct 17, 2026
- bradcstevens/git-loopy-skillstheir own version, first seen Oct 15, 2026
- chenson42/stackkeeltheir own version, first seen Sep 22, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- microsoft/intelligent-terminal★ 2.2ksame name
- halo-box/strix-llama.cpp★ 259same name
- ilien-dev/quiron★ 65same name
- Blueforce-Tech-Inc/BlueCortexCE★ 4same name
- chenson42/stackkeel★ 1same name
- dris1153/upstream-sync★ 1same name
- steven-pribilinskiy/tabby-claude-status★ 1same name
- bradcstevens/git-loopy-skills★ 0same name
- shruthis4/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- golang-tui-update-examplesSkill
- apply-worktreeSkill
- babysit-prSkill
- documentation-writerSkill
- file-prSkill
- frontend-designSkill
- golang-packagesSkill
- golangSkill
- golang-tuiSkill
- grill-meSkill
- karpathy-guidelinesSkill
- kubernetes-specialistSkill
- kubernetes-upgrade-analysisSkill
- leaving-gh-commentsSkill
- mermaid-diagramsSkill
- modernizeSkill
- nuclear-reviewSkill
- remotion-best-practicesSkill
- reviewSkill
- security-auditSkill
- shadcn-vueSkill
- sharpenSkill
- simplifySkill
- tui-designSkill
- unslopSkill
- writing-for-agentsSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
Read the full diff only for files that matter: exported API, README, docs/, examples/, config, CLI flags.
“Common” is measured: kept by at least 6 in 10 of the 9 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.
Files
Upstream sync
Repo-only (not shipped in the plugin). Keeps skills/ current with the projects it documents.
State: .upstream-sync.json at the repo root (gitignored). Map of <owner/repo> to
{"sha": "<last checked commit>", "tag": "<last release>", "checked": "<ISO date>"}. Missing file
or entry means first run for that repo: use the latest release (or last ~30 commits) as the baseline
instead of reading all history.
Steps
- Collect references: grep
skills/andREADME.mdforgithub.com/<owner>/<repo>and Go import paths (go.dev/pkg.go.devlinks,importblocks). Dedupe to a repo list. Dolrstanley/*first, then the rest. Skiplrstanley/skills, and skip skills synced viaremotes.yaml(usetask upfor those). - Cheap check per repo (parallelize; use
gh api):- Compare HEAD sha and latest release tag to state. Unchanged: skip.
- Changed:
gh api repos/<o>/<r>/compare/<old>...HEAD --jq '.files[].filename'(names only), plus release notes (gh release list/gh release view) andCHANGELOG/READMEdiffs. - Read the full diff only for files that matter: exported API,
README,docs/,examples/, config, CLI flags. Ignore tests, CI, deps bumps, and internal refactors.
- Decide per finding whether it belongs in a skill. Cover new public APIs/features, behavior or best-practice changes, and renames. Fix or remove docs for deprecated or removed APIs. Skip anything already documented or too minor for a skill.
- Edit the owning skill, following
AGENTS.md(progressive disclosure, reference file sizes, ASCII only, README table if scope changes). Verify new APIs against pkg.go.dev or source before documenting. - Save state for every repo checked (including no-change ones) only after its edits are done. Never commit.
Output
Per repo: one line (unchanged, or what was added/changed/removed and in which file). Then list
anything uncertain that needs a human decision.
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.