memory-lint
Skill0 starsChanged 3 months agoApache-2.0View on GitHub
Lint Markdown memory and documentation corpora with the deterministic memory-lint CLI. Use when validating frontmatter, links, indexes, managed markers, staleness, structure, or revision changes without modifying the corpus.
- Installs packages
5 other projects use a version of this.
Adopted by
Most recently taken up by
- MrHashMe/efficiency-playbooktheir own version, first seen Nov 8, 2026
- KerberosClaw/kc_ai_skillstheir own version, first seen Oct 15, 2026
- GlassOnTin/claude-memory-skillstheir own version, first seen Oct 14, 2026
- GvHildebrand/claude-code-skillstheir own version, first seen Oct 1, 2026
- yangwhale/CloseCrabtheir own version, first seen Aug 18, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- KerberosClaw/kc_ai_skills★ 79same name
- yangwhale/CloseCrab★ 5same name
- GlassOnTin/claude-memory-skills★ 1same name
- GvHildebrand/claude-code-skills★ 0same name
- MrHashMe/efficiency-playbook★ 0same 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 repository5 other files it gives its agents.
- dispatch-briefSkill
- proof-before-doneSkill
- render-checkSkill
- usage-costSkill
- verify-numbersSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 2 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Use the version-pinned adapter to run memory-lint as a read-only diagnostic.
- Distinctive: line 30
Prefer JSON for machine parsing and table output for a person reading the command directly.
- Very specific: line 32
Use --now YYYY-MM-DD when results must be reproducible across runs.
- Distinctive: line 33
Run the adapter from this skill directory:
- Very specific: line 54
Use --corpus-root <path> to override corpus_root from the configuration without editing the file.
- Very specific: line 56
Use --against <git-ref> only when the corpus is inside a Git repository and the ref is available locally.
- Very specific: line 60
Run python scripts/memory_lint_wrapper.py --help for the complete flag surface.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Memory Lint
Use the version-pinned adapter to run memory-lint as a read-only diagnostic.
It preserves the CLI's output and exit status and never installs dependencies
while running.
Install
Install the exact supported release into the Python environment that will run the adapter:
python -m pip install memory-lint==0.1.0Workflow
- Locate the corpus configuration file. Every input is a named flag; do not pass a positional corpus path.
- Prefer JSON for machine parsing and table output for a person reading the command directly.
- Use
--now YYYY-MM-DDwhen results must be reproducible across runs. Run the adapter from this skill directory:
python scripts/memory_lint_wrapper.py \ --config path/to/config.yaml \ --format json \ --now YYYY-MM-DDInterpret the exit status before reporting results:
0: clean corpus1: one or more findings2: usage, configuration, filesystem, Git, dependency, or abnormal delegated-process error
An exit status of 1 is a successful lint run with findings, not an execution
failure. Parse JSON only when the command produced valid JSON.
Corpus and Revision Options
- Use
--corpus-root <path>to overridecorpus_rootfrom the configuration without editing the file. - Use
--against <git-ref>only when the corpus is inside a Git repository and the ref is available locally. The CLI performs read-only Git operations. - Supply
--compare-beforeand--compare-aftertogether to detect identical or whitespace-only revisions. - Run
python scripts/memory_lint_wrapper.py --helpfor the complete flag surface.
Report
Include the executed command, configuration and corpus paths, exit status, finding count, and findings grouped by severity and code. Report exit-2 errors verbatim enough to make the next action clear. Do not edit or auto-fix corpus files on the strength of lint output alone.
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.

