sibling-path-map
Skill17 starsChanged 14 days agoMITView on GitHub
Lists places that probably must obey the same rule as a changed guard, comparison or normalization. Use when writing adversarial tests or reviewing a change that adds or fixes a rule.
In this repository32 other files it gives its agents.
- AGENTS.mdAGENTS.md
- aboutSkill
- answerSkill
- attack-testsSkill
- audit-experimentSkill
- bugSkill
- ci-watchSkill
- commitSkill
- contextSkill
- delegateSkill
- documentSkill
- evalSkill
- featureSkill
- impact-mapSkill
- implement-workSkill
- mrSkill
- mutation-checkSkill
- perfSkill
- previewSkill
- refactorSkill
- requestSkill
- review-diffSkill
- reviewSkill
- run-experimentSkill
- screen-designSkill
- screen-paritySkill
- setupSkill
- specSkill
- sweepSkill
- test-hardeningSkill
- verify-workSkill
- work-graphSkill
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
- Very specific: line 8
Run node <tools>/sibling-path-map.mjs --base <base> [paths] (the tools folder is in the task's "[haechi] Repo facts" block, or two levels …
≈ “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.
Files
Sibling path map
Run node <tools>/sibling-path-map.mjs --base <base> [paths] (the tools folder is in the task's "[haechi] Repo facts" block, or two levels above this skill's folder). Add --json for machine-readable output.
It takes each changed line that guards, compares, deduplicates or normalizes, and lists other code that touches the same fields or functions. Treat the list as candidates, not findings. For each candidate decide whether it is a sibling path — display versus save, existing versus incoming, add versus move or remove, common versus edge format — and whether it applies the same rule. Attack the siblings that do not.
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.