promote

Convert auto-memory notes into enforceable rules in CLAUDE.md or .claude/rules.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/Patasse97/claude-skills --skill promote-patasse97
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: promote
Source: https://github.com/Patasse97/claude-skills/tree/main/engineering-team/self-improving-agent/skills/promote
Command: npx skills add https://github.com/Patasse97/claude-skills --skill promote-patasse97

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Promote memory patterns into permanent project rules to ensure consistent behavior across CLAUDE.md or .claude/rules.

Core Features & Use Cases

  • Move approved learnings from auto-memory into CLAUDE.md or .claude/rules to enforce patterns.
  • Generate scoped rules with optional path targeting to apply to specific files or directories.
  • Facilitate governance by documenting enforcement guidance and reducing drift.

Quick Start

Describe a memory pattern and run /si:promote to promote it to CLAUDE.md or a scoped rule.

Frequently Asked Questions about promote

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn MEMORY.md learnings into enforceable project rules?

To turn MEMORY.md learnings into enforceable project rules, you can distill approved auto-memory notes into concise rules and write them globally to CLAUDE.md or .claude/rules. This ensures consistent behavior and reduces drift across your project.

Can I scope project rules to specific files or directories in CLAUDE.md?

Yes, you can scope project rules to specific files or directories by generating targeted rules with optional path scoping. This applies enforcement guidance only to the specified paths within .claude/rules rather than applying changes globally.

What is the best way to promote auto-memory patterns into formal guidance?

The best way to promote auto-memory patterns into formal guidance is to distill the notes into concise rules and write them to CLAUDE.md or .claude/rules. This process includes cleanup and validation to ensure ongoing governance and prevent configuration drift.

Does promoting memory notes to CLAUDE.md require manual cleanup and validation?

Yes, promoting memory notes to CLAUDE.md requires manual cleanup and validation to ensure ongoing governance. The process guides you through distilling learnings into concise rules and validating the output to maintain consistent project behavior.

Why should I enforce project rules via .claude/rules instead of keeping notes in MEMORY.md?

You should enforce project rules via .claude/rules instead of keeping notes in MEMORY.md because auto-memory notes are passive records. Promoting them to formal guidance ensures patterns are actively enforced globally, reducing drift and maintaining consistent behavior across the project.