promote
Graduate a proven pattern from auto-memory (MEMORY.md) to CLAUDE.md or .claude/rules/ for permanent enforcement. Use when the user runs /si:promote or asks to make a learned behavior permanent.
Security Assessment
About promote
promote (invoked as /si:promote) is a Claude Code skill that graduates a proven pattern from Claude's auto-memory (MEMORY.md) into the project's persistent rule system — either the repository's CLAUDE.md, the user's global ~/.claude/CLAUDE.md, or a scoped file under .claude/rules/. It solves the problem of useful learned behaviors staying as background notes that Claude may not consistently enforce, by turning them into explicit, prescriptive instructions that apply in all future sessions.
The skill defines a seven-step workflow: understand the pattern, locate the matching entry in MEMORY.md via a grep over the project's memory directory, determine the right target based on scope, distill the descriptive note into a concise imperative rule, write it to the chosen target (appending under a heading in CLAUDE.md or creating a scoped rule file with optional YAML path frontmatter), clean up the original auto-memory entry after confirmation, and report the result. It includes a decision guide for when to promote (patterns seen three or more times, recurring corrections, project conventions) versus when not to (one-time notes, session-specific context, soon-to-change details), and guidance on keeping CLAUDE.md concise by overflowing into rules/.
It targets Claude Code users and teams who want their agent to reliably follow established conventions — package-manager choices, validation requirements, error-handling patterns — without repeating corrections. It is a lightweight meta/workflow helper operating only on local project and configuration files.
FAQ
How do I use it?
Run /si:promote with a pattern description, optionally adding --target (e.g. claude.md or rules/testing.md) and --paths to scope a rule to specific file globs. If no target is given, the skill recommends one based on the pattern's scope.
Where does the rule get written?
To the project CLAUDE.md for global project rules, to a scoped file under .claude/rules/ for file-type-specific patterns, or to ~/.claude/CLAUDE.md for rules that apply across all your projects.
When should I not promote a learning?
Avoid promoting one-time debugging notes, session-specific context, things likely to change soon (such as during a migration), or patterns already covered by existing rules.
Does it modify my memory files?
Yes — after promoting, it asks you to confirm removing the original entry from MEMORY.md to free space for new learnings. It searches memory with grep and edits the file only after your confirmation.
Install promote
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
alirezarezvani/claude-skills