agentleFS
bamlabbamlab/flashlight/.claude/skills/eol-check/SKILL.md

eol-check

Skill1.6k starsChanged 3 days agoMITView on GitHub

Compare the versions of the platform dependencies this repo runs on (Node, React, React Native, Expo, Next.js, Docusaurus, TypeScript, Firebase Functions runtime) against endoflife.date and npm, and say what to upgrade. Use for an EOL / maintenance / "are we up to date" check, or from the factory's weekly run.

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

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

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

    Read the resolved version from yarn.lock when a range is given.

    line 23

≈ “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

EOL check

Goal: upgrade to a new stable release as soon as it's proven (out for at least 14 days), and never run on something past its end of life.

1. Collect what this repo uses

Find the version actually in use, and every place that pins it:

ProductWhere to look
Node.js.nvmrc, engines, CI node-version, netlify.toml NODE_VERSION, Dockerfile FROM, server/firebase.json runtime, pkg targets
React / React DOMpackage.json of each workspace
React Native / Expopackage.json of examples and test apps, peer ranges of published packages
Next.jsfrontend/package.json
Docusauruswebsite/package.json
TypeScriptroot package.json

Read the resolved version from yarn.lock when a range is given.

2. Compare with upstream

  • Lifecycle: curl -s https://endoflife.date/api/<product>.json (nodejs, react, react-native, expo, nextjs, docusaurus, typescript). Each cycle has cycle, releaseDate, eol, support, latest, latestReleaseDate.
  • Latest stable: npm view <package> time --json for release dates when endoflife.date lacks the product.

3. Decide

For each product:

  • EOL — our cycle's eol date is past → severity high.
  • EOL soon — eol within 90 days → medium.
  • Upgrade available — a newer stable cycle or patch whose release is ≥ 14 days old → low (patch/minor) or medium (major).
  • Ignore releases younger than 14 days, pre-releases and release candidates.
  • Note known blockers (e.g. a major that a dependency doesn't support yet — check the ADRs and open issues before proposing it).

4. Output

A table: product · in use · latest stable (date) · our cycle EOL · status · action, then for each action one line saying patch/minor (safe to upgrade automatically, ends in a draft PR) or major (needs a human go: describe blockers and the files to change). Don't upgrade anything in the same run unless asked.

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.