Neat-Freak Knowledge Closeout
KKKKhazix/khazix-skills
Brings project docs, agent rule files, authorized memory and leftover workspace files back in line with what the code and runtime actually do at the end of a work session.
Process file changes and update CLAUDE.md memory sections. An agent skill from severity1/claude-code-auto-memory.
Install Memory Processor
$ npx skills add severity1/claude-code-auto-memory --skill memory-processor -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install severity1/claude-code-auto-memory memory-processor --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/severity1/claude-code-auto-memory.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/memory-processor .claude/skills/memory-processor && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "memory-processor" agent skill from https://github.com/severity1/claude-code-auto-memory/tree/main/skills/memory-processor into .claude/skills/memory-processor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memory-processor", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/severity1/claude-code-auto-memory/tree/main/skills/memory-processorType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add severity1/claude-code-auto-memory --skill memory-processor -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install severity1/claude-code-auto-memory memory-processor --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/severity1/claude-code-auto-memory.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/memory-processor .agents/skills/memory-processor && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "memory-processor" agent skill from https://github.com/severity1/claude-code-auto-memory/tree/main/skills/memory-processor into .agents/skills/memory-processor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memory-processor", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add severity1/claude-code-auto-memory --skill memory-processor -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install severity1/claude-code-auto-memory memory-processor --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/severity1/claude-code-auto-memory.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/memory-processor .cursor/skills/memory-processor && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "memory-processor" agent skill from https://github.com/severity1/claude-code-auto-memory/tree/main/skills/memory-processor into .cursor/skills/memory-processor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memory-processor", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/severity1/claude-code-auto-memory.git --path skills/memory-processor--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add severity1/claude-code-auto-memory --skill memory-processor -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install severity1/claude-code-auto-memory memory-processor --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/severity1/claude-code-auto-memory.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/memory-processor .gemini/skills/memory-processor && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "memory-processor" agent skill from https://github.com/severity1/claude-code-auto-memory/tree/main/skills/memory-processor into .gemini/skills/memory-processor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memory-processor", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install severity1/claude-code-auto-memory memory-processorInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add severity1/claude-code-auto-memory --skill memory-processor -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/severity1/claude-code-auto-memory.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/memory-processor .github/skills/memory-processor && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "memory-processor" agent skill from https://github.com/severity1/claude-code-auto-memory/tree/main/skills/memory-processor into .github/skills/memory-processor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memory-processor", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add severity1/claude-code-auto-memory --skill memory-processor -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install severity1/claude-code-auto-memory memory-processor --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/severity1/claude-code-auto-memory.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/memory-processor .opencode/skills/memory-processor && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "memory-processor" agent skill from https://github.com/severity1/claude-code-auto-memory/tree/main/skills/memory-processor into .opencode/skills/memory-processor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memory-processor", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
memory-processor- GitHub stars
- 159
- Token cost
- ~1.3k tokens
- SKILL.md length
- 534 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
Process file changes and update CLAUDE.md memory sections. An agent skill from severity1/claude-code-auto-memory.
- Works in 6 steps: Parse context: Read context provided by… → Categorize changes: Map files to… → Analyze impact: Determine what needs… → …
- The memory-updater agent needs to analyze dirty files
- SKILL.md covers Guidelines, Algorithm, Marker Syntax and Section Names, plus 2 more sections
- Calls npm, python and pytest
What it does
Memory Processor is an agent skill from severity1/claude-code-auto-memory. Process file changes and update CLAUDE.md memory sections. Use when the memory-updater agent needs to analyze dirty files, update AUTO-MANAGED sections, verify content removal, or detect stale commands. Invoked after file edits to keep project memory in sync.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Agent instruction files and Agent memory. The repository describes itself as: Claude Code plugin that automatically maintains CLAUDE.md files. The licence is MIT.
When your agent uses it
- The memory-updater agent needs to analyze dirty files
- Update AUTO-MANAGED sections
- Verify content removal
- Detect stale commands
Example prompts
- “/memory-processor”
Requirements
- Python 3
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Parse context: Read context provided by memory-updater agent
- Categorize changes: Map files to CLAUDE.md sections using the tables in "Section Names" below. Match changed files to their update triggers.
- Analyze impact: Determine what needs updating
- Verify and update content: Before modifying documented content, verify accuracy
- Update memory file: Modify relevant sections in the active memory file
- Validate: Ensure updates follow guidelines
What it can do on your machine
Read from SKILL.md and the folder at commit d8254a8. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npmpythonpytestuv
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm and uv, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Memory Processor loads about 1.3k tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 534 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from severity1/claude-code-auto-memory at commit d8254a8, republished under its MIT licence (© severity1). 534 words, ~1,288 tokens.
Download SKILL.mdSave it as
.claude/skills/memory-processor/SKILL.md (or your agent's skills folder).- name
- memory-processor
- description
- Process file changes and update CLAUDE.md memory sections. Use when the memory-updater agent needs to analyze dirty files, update AUTO-MANAGED sections, verify content removal, or detect stale commands. Invoked after file edits to keep project memory in sync.
Memory Processor
Process changed files and update relevant memory file sections (CLAUDE.md or AGENTS.md, whichever is the active file per project config) following official guidelines.
Guidelines
MANDATORY: All rules below must be followed exactly. Violations produce incorrect CLAUDE.md content.
@../shared/references/guidelines.md
Algorithm
Parse context: Read context provided by memory-updater agent:
- Changed files with categories
- File content summaries
- Detected dependencies
- Git context (commits, diffs)
- Target memory files (CLAUDE.md or AGENTS.md per project config)
Categorize changes: Map files to CLAUDE.md sections using the tables in "Section Names" below. Match changed files to their update triggers.
Analyze impact: Determine what needs updating:
- New build commands added?
- Architecture changed (new dirs, renamed components)?
- New coding patterns detected?
- Dependencies added/removed?
Verify and update content: Before modifying documented content, verify accuracy:
Key distinction - conventions vs patterns:
conventions: Explicit rules humans decided (naming, imports, formatting)patterns: Implicit patterns AI detected from recurring code structures
Removal verification:
- Read the relevant CLAUDE.md section to get currently documented items
- For each item that appears missing from changed files:
- Use Grep to search the codebase for that item
- Search in relevant directories excluding node_modules, vendor, .git
- If item exists elsewhere: keep it documented
- If item is not found anywhere: mark for removal
Stale command detection:
- Compare documented commands against commands that actually executed successfully
- If documented command differs from successful execution, update to match what worked
- Examples:
- Documented:
python pytest| Actually worked:python -m pytest→ Update - Documented:
npm test| Actually worked:npm run test→ Update - Documented:
pytest tests/| Actually worked:uv run pytest→ Update
- Documented:
- Source: Successful Bash tool executions from session context or git commit history
Examples:
- Pattern:
@decoratorremoved → searchgrep -r "@decorator" src/ - Convention:
async/awaitstyle removed → search forasync functionorawait - Architecture:
utils/directory deleted → verify noutils/references remain - Build command:
npm run devremoved from package.json → verify script is gone
Update memory file: Modify relevant sections in the active memory file:
- Preserve AUTO-MANAGED markers
- Never touch MANUAL sections
- Apply content rules (specific, concise, structured)
- Do not modify CLAUDE.md redirect files (files containing only "Read AGENTS.md...")
Validate: Ensure updates follow guidelines:
- No generic instructions added
- Specific and actionable content
- Proper markdown formatting
Show full SKILL.md (173 more words)Show less
Marker Syntax
CLAUDE.md uses HTML comment markers for selective updates:
<!-- AUTO-MANAGED: section-name -->
Content that will be automatically updated
<!-- END AUTO-MANAGED -->
<!-- MANUAL -->
Content that will never be touched
<!-- END MANUAL -->Section Names
Root CLAUDE.md Sections
| Section | Purpose | Update Triggers |
|---|---|---|
project-description | Project overview | README changes, major refactors |
build-commands | Build, test, lint commands | package.json, Makefile, pyproject.toml |
architecture | Directory structure, components | New dirs, renamed files, structural changes |
conventions | Naming, imports, code standards | Pattern changes in source files |
patterns | AI-detected coding patterns | Repeated patterns across files |
git-insights | Decisions from git history | Significant commits |
best-practices | From official Claude Code docs | Manual updates only |
Subtree CLAUDE.md Sections
| Section | Purpose | Update Triggers |
|---|---|---|
module-description | Module purpose | Module README, major changes |
architecture | Module structure | File changes within module |
conventions | Module-specific conventions | Pattern changes in module |
dependencies | Key module dependencies | Import changes, package updates |
Token Efficiency
- Keep sections concise - bullet points, not paragraphs
- Use imports (
@path/to/file) for detailed specs - Follow Content Rules above (< 500 lines, stay current)
Output
Return a brief summary:
- "Updated [section names] in [memory file path] based on changes to [file names]"
- "Removed [pattern] from [section] - no longer used in codebase"
- "No updates needed - changes do not affect documented sections"
© severity1, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/memory-processor of severity1/claude-code-auto-memory.
Open the folder on GitHubat commit d8254a8
Compare with similar skills
Memory Processor next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Memory Processor this skillseverity1/claude-code-auto-memory | 159 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Neat-Freak Knowledge CloseoutKKKKhazix/khazix-skills | 21k | — | ~1.9k | Automated safety check: Pass | MIT | |
| SkillOpt Sleep Cyclemicrosoft/SkillOpt | 18k | — | ~2.3k | Automated safety check: Pass | MIT | |
| CLAUDE.md Improveranthropics/claude-plugins-official | 37k | 5 repos | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Harness Engineering10xChengTu/harness-engineering | 102 | 1 repos | ~1k | Automated safety check: Pass | None | |
| Self Improving For CodexGODGOD126/self-improving-for-codex | 130 | — | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
- Official
SkillOpt Sleep Cycle
microsoft/SkillOpt
Runs an on-demand or nightly sleep cycle that reviews past Claude Code sessions and proposes validated updates to CLAUDE.md and skills.
- Official
CLAUDE.md Improver
anthropics/claude-plugins-official
Finds every CLAUDE.md file in a repository, scores each against quality criteria, shows a report, then makes targeted updates after you approve.
Harness Engineering
10xChengTu/harness-engineering
Set up and improve harness engineering (AGENTS.md, docs/, lint rules, eval systems, project-level prompt engineering) for AI-agent-friendly codebases.
Self Improving For Codex
GODGOD126/self-improving-for-codex
Build or maintain a Codex-native self-improving memory loop using global AGENTS.md, a persistent memories directory, and optional nightly refinement automation.
CLAUDE.md Preserve
EliaAlberti/cpr-compress-preserve-resume
Writes this session's durable learnings into the project's CLAUDE.md and keeps the file short by archiving stale sections.
More from severity1/claude-code-auto-memory
Codebase Analyzer
severity1/claude-code-auto-memory
This skill should be used when the user asks to "initialize auto-memory", "create CLAUDE.md", "set up project memory", or runs the /auto-memory:init command.
Related
Categories
Questions about Memory Processor
What does Memory Processor do?
Process file changes and update CLAUDE.md memory sections. An agent skill from severity1/claude-code-auto-memory. Memory Processor is an agent skill from severity1/claude-code-auto-memory.md memory sections.
When should I use Memory Processor?
Memory Processor fits situations like: the memory-updater agent needs to analyze dirty files; update AUTO-MANAGED sections; verify content removal; detect stale commands.
How do I install Memory Processor in Claude Code?
Run `npx skills add severity1/claude-code-auto-memory --skill memory-processor -a claude-code`. Or copy the skill folder (skills/memory-processor in severity1/claude-code-auto-memory) into .claude/skills/memory-processor in your project. Claude Code loads it when a task matches its description.
How do I install Memory Processor in Codex?
Run `npx skills add severity1/claude-code-auto-memory --skill memory-processor -a codex`. Or copy the skill folder (skills/memory-processor in severity1/claude-code-auto-memory) into .agents/skills/memory-processor in your project. Codex loads it when a task matches its description.
Can I use Memory Processor in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add severity1/claude-code-auto-memory --skill memory-processor -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/memory-processor, .gemini/skills/memory-processor, .github/skills/memory-processor and .opencode/skills/memory-processor in your project.
What does Memory Processor need to run?
Going by SKILL.md and its folder, Memory Processor needs the command-line tools its instructions call (npm, python, pytest and uv). Our summary lists: Python 3.
Does Memory Processor access the network?
SKILL.md contains no URLs. Its commands use npm and uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Memory Processor safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Memory Processor use?
Memory Processor is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Memory Processor use?
About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Memory Processor?
Skills that share tags, products or a category with Memory Processor: Neat-Freak Knowledge Closeout (KKKKhazix/khazix-skills, 21k stars), SkillOpt Sleep Cycle (microsoft/SkillOpt, 18k stars), CLAUDE.md Improver (anthropics/claude-plugins-official, 37k stars) and Harness Engineering (10xChengTu/harness-engineering, 102 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Memory Processor?
severity1 (a GitHub user) maintains it in severity1/claude-code-auto-memory, which has 159 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on April 18, 2026.
Source: severity1/claude-code-auto-memory on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.