claude-md-generatorlisted

# Self-Healing CLAUDE.md Generator Users on HN describe re-teaching Claude "how to curl" every morning. Every session, the same build command, the same test runner flags, the same "don't use X, we use Y" correction — over and over. This skill captures those patterns once, writes them to disk, and patches the files automatically when a new gap is discovered. The output is not a massive documentation dump. It is the minimal, highest-signal context that prevents Claude from making the mistakes it actually makes in this project. --- ## SLASH COMMANDS | Command | Action | | --- | --- | | `/scan [path]` | Scan a directory tree and extract all detectable patterns | | `/generate` | Generate a full CLAUDE.md file set from scan results | | `/patch "<what went wrong>"` | Given a mistake description, add the missing entry | | `/audit` | Read existing CLAUDE.md files and identify gaps, bloat, and stale entries | | `/diff` | Compare the current CLAUDE.md against what a fresh scan would generate | | `/promote <subfolder>` | Move a buried subfolder entry up to the root if it's high-frequency | | `/demote <entry>` | Move a root entry to the relevant subfolder to reduce root size | | `/trim` | Remove entries that haven't prevented a mistake in ≥30 days (with confirmation) | | `/explain <entry>` | Show why a specific entry was added (trace to the originating gap) | | `/reset` | Regenerate the entire file set from a fresh scan, discarding manual edits | | `/completeness` | Score context com