agentleFS
rome-osrome-os/rome/.claude/skills/imports-of/SKILL.md

imports-of

Skill904 starsChanged 5 days agoMITView on GitHub

Find what a set of TypeScript files imports and what imports them inside their package, grouped by folder. Use when deciding where files belong or which import rules a folder can take.

The file

Files
SKILL.md

Imports of a set of files

Goal end-state: every import crossing the edge of the set is known, by the folder on the other side, from one run of pnpm imports-of <files or folders> (scripts/imports-of.ts) rather than from reading files one at a time.

The report resolves imports as pnpm lint:imports does, so it counts type-only imports and tests, and a folder it names as importing nothing from the set breaks no import rule in that direction. It scans one package, so importers in other packages are not in it.

A folder is a place in the tree, not a decision. Which crossings are wrong and which rules a boundary takes are judged against the domain model, not against the counts.

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.