agentleFS
JordanCoinJordanCoin/codemap/.claude/skills/hub-safety/SKILL.md

hub-safety

Skill710 starsChanged 8 months agoMITView on GitHub

Safety checks and procedures when modifying hub files (files imported by 3+ others). Activated when editing files with high importer counts.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    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:

    Run codemap --importers <file> to see all dependents

    line 12
  2. Distinctive:

    Check if tests exist for dependents, not just the hub itself

    line 14
  3. Distinctive:

    Prefer additive changes over breaking changes

    line 18
  4. Distinctive:

    If renaming or removing a public symbol, update all importers in the same commit

    line 19
  5. Distinctive:

    If changing a function signature, check all call sites

    line 20
  6. Distinctive:

    Run the full test suite, not just the hub's tests

    line 24
  7. Very specific:

    Run codemap --deps . to verify the dependency graph is intact

    line 25
  8. Distinctive:

    If the hub has 8+ importers, consider a staged rollout (change hub, test, update callers separately)

    line 26

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

Hub Safety Protocol

Hub files are imported by 3+ other files. Changes here ripple across the codebase.

Before editing a hub file

  1. Run codemap --importers <file> to see all dependents
  2. Understand the public API surface: which functions/types are used externally
  3. Check if tests exist for dependents, not just the hub itself

While editing

  • Prefer additive changes over breaking changes
  • If renaming or removing a public symbol, update all importers in the same commit
  • If changing a function signature, check all call sites

After editing

  • Run the full test suite, not just the hub's tests
  • Run codemap --deps . to verify the dependency graph is intact
  • If the hub has 8+ importers, consider a staged rollout (change hub, test, update callers separately)

Risk escalation

ImportersRiskAction
3-5MediumRun package tests + direct importer tests
6-10HighRun full test suite, review all importers
10+CriticalConsider splitting the hub or using an interface

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.