dep-refs
Skill247 starsChanged 10 days agoMITView on GitHub
Use when the agent needs to inspect TypeScript export references in the z-code workspace, list exports from a file, verify whether an export is unused before deletion, investigate who imports a symbol during refactors, or combine pnpm knip unused-export results with pnpm dep:refs symbol-level reference tracing.
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 2 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Use the repository's pnpm dep:refs CLI to answer symbol-level questions before changing or deleting TypeScript exports.
- Distinctive: line 13
Start broad when deleting code:
- Very specific: line 19
Use knip to find likely unused exports, then inspect any risky or unclear export with dep:refs:
- Distinctive: line 31
Use scoped scans for fast exploration only when the scope is intentionally limited:
- Very specific: line 37
Before claiming an export is safe to delete, prefer an unscoped dep:refs run so cross-package callers are not missed.
- Very specific: line 41
Use silent pnpm mode for machine-readable output, because normal pnpm output includes extra banner lines:
- Very specific: line 47
Use JSON when summarizing many symbols, feeding results to jq, or comparing references and reExports counts programmatically.
- Very specific: line 51
Treat References (0) and Re-exports (0) as "no static references found", not as proof that no dynamic usage exists.
- Very specific: line 53
If a symbol only appears under Re-exports, trace the outward barrel path before deleting.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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
Dep Refs
Use the repository's pnpm dep:refs CLI to answer symbol-level questions before changing or deleting TypeScript exports. Run commands from the z-code repository root.
Workflow
Start broad when deleting code:
pnpm knipUse knip to find likely unused exports, then inspect any risky or unclear export with dep:refs:
pnpm dep:refs packages/services/src/bots/botsService.ts:createBotsServiceList all exports in a file when the exact symbol name is unknown:
pnpm dep:refs --list-exports packages/services/src/bots/botsService.tsUse scoped scans for fast exploration only when the scope is intentionally limited:
pnpm dep:refs --scope packages/services packages/services/src/bots/botsService.ts:createBotsServiceBefore claiming an export is safe to delete, prefer an unscoped dep:refs run so cross-package callers are not missed.
JSON Mode
Use silent pnpm mode for machine-readable output, because normal pnpm output includes extra banner lines:
pnpm -s dep:refs packages/services/src/bots/botsService.ts:createBotsService --json | jq .Use JSON when summarizing many symbols, feeding results to jq, or comparing references and reExports counts programmatically.
Interpreting Results
Treat References (0) and Re-exports (0) as "no static references found", not as proof that no dynamic usage exists. The script does not detect dynamic import() paths or string-based references.
If a symbol only appears under Re-exports, trace the outward barrel path before deleting. A re-export can still be part of the public surface even when there are no direct internal imports.
For refactors, report concrete callers with file and line from the CLI output, then decide whether to update callers, preserve the export, or delete it.
Trending
Steady: 2 new projects took it in the last 4 weeks, 1× the 4 weeks before.thin data
Other versions4 projects use a version of this.
Word for word · 2
- zai-org/ZCode★ 8.4k100% same
- skillpie/ZCodeOnline★ 3100% same
Edited · 2
- ccbud/CCBuddy★ 897% same
- betacatsling/Open-ZCode★ 090% same
Wrote their own version · 0
None found.
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 repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/react-best-practices/AGENTS.mdAGENTS.md
- agent-browserSkill
- ai-elementsSkill
- architecture-governanceSkill
- docxSkill
- dogfoodSkill
- e2e-case-lifecycleSkill
- electronSkill
- feature-boundary-plannerSkill
- vercel-react-best-practicesSkill
- session-managementSkill
- xlsxSkill
- zcode-large-task-fixtureSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.