document-evolution-tracker
Skill10 starsChanged 6 days agoMITView on GitHub
Tracks how a family of document versions evolved: discovers the version files, aligns them block by block, and reports paragraph-level changes plus the lineage of named concepts across versions. Fires when a set of drafts must be compared over time rather than one pair of files.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- JiamingShi-JsPhys/agent-skillstheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- JiamingShi-JsPhys/agent-skills★ 4same name
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 repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/chelate-shell.mdcCursor rule
- 3d-modelerSkill
- ai-trace-removerSkill
- bibtex-normalizerSkill
- capstone-labmateSkill
- conflict-detectorSkill
- data-profilerSkill
- formula-validatorSkill
- fulltext-extractorSkill
- latex-exporterSkill
- literature-retrieverSkill
- longitudinal-analysisSkill
- ml-auditorSkill
- multi-dim-managerSkill
- quantitative-validatorSkill
- reference-auditorSkill
- sci-visualizerSkill
- security-guardSkill
- task-organizerSkill
- video-trackerSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
Run this exact form — do not read the source tree:
- Distinctive: line 45
Only two files need a diff — any diff tool is cheaper.
- Very specific: line 75
Only sequential and timestamp naming schemes are recognised.
≈ “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
document-evolution-tracker
Diffs a whole family of document versions and traces named concepts through
them. It reports structural change — block alignment via difflib — not
semantic meaning.
- Stage:
workspace· Sandbox: no · Dependencies: stdlib only (PyYAMLonly for.yamlconfigs)
Quick Execution
Run this exact form — do not read the source tree:
python run.py --root <WS> --action versions -- --config config/examples/family.jsonvalidatefirst: it reports config errors and the discovered version files.--concepts "a,b"names the concepts to trace; unnamed ones are not followed.- The gate lands in
<WS>/process/gates/document-evolution-tracker_<ts>.json.
When to use
- A family of versions (timestamped or sequentially named) must be compared as a whole.
- A named concept — a term, a heading, a definition — must be traced across versions.
- The evolution of a draft must be reported as a timeline, not a single diff.
When NOT to use
- Only two files need a diff — any diff tool is cheaper.
- You need semantic equivalence, not a structural comparison.
Actions
--action | Does | Extra arguments |
validate | Check the config and report the discovered versions | --config <cfg> |
versions | List the discovered version files | --config <cfg> |
run | Compare the family and produce the timeline | --config <cfg> [--concepts "a,b"] |
Hard constraints
- Structural only. A concept counts as present on a literal match, never on a paraphrase.
- Never reformat the sources. Inputs are read, never written.
Outputs
<WS>/process/gates/document-evolution-tracker_<ts>.json— the gate result.- A Markdown timeline plus a JSON change record under
process/.
Failure handling
- An invalid config exits non-zero and names the offending field.
- Fewer than two discovered versions aborts the run.
- A concept that never appears is reported as absent across all versions.
Limitations
- Diffing is structural (block alignment), not semantic.
- Only
sequentialandtimestampnaming schemes are recognised.
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.