type-lineage
Skill0 starsChanged 4 months agoNo licenceView on GitHub
AST-based relationship (lineage) extraction for a central data type in AgentVillage. Given a type name (e.g. `LogEvent`) and a Python source root, it enumerates — as an objective, verifiable artifact — where that type is produced, consumed, persisted, transformed, and which fields are read/written. Use this whenever you need to find every producer/consumer of a schema/contract type without relying on brittle grep (the #344 blind spot). Invoked by `idd` 事前調査 "producer/consumer の全列挙" and by #425 (smell evaluation). Output is a language-neutral adjacency list (JSON) plus a derived Mermaid view.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- backlogSkill
- iddSkill
- idd-teamSkill
- issueSkill
- pr-reviewSkill
- self-reflection-reviewSkill
- ventSkill
- wisdom-captureSkill
The file
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.