memory-md-management

Name: memory-md-management
Author: giuseppe-trisciuoglio

1.3kinstalls36forks

How to install memory-md-management?

giuseppe-trisciuoglio/developer-kit/memory-md-management

$npx -y skills add giuseppe-trisciuoglio/developer-kit --skill memory-md-management

Installs into the current project.

Summary

Provides comprehensive memory file management capabilities including auditing, quality assessment, and targeted improvements for files such as CLAUDE.md. Use when user asks to check, audit, update, improve, fix, maintain, or validate project memory files. Also triggers for "proje

Files · 1

View on GitHub

SKILL.md

1	# Memory.md Management
2
3	Provides comprehensive project memory file management capabilities including auditing, quality assessment, and targeted improvements. This skill ensures the coding agent has optimal project context by maintaining high-quality documentation files such as `CLAUDE.md`.
4
5	## Overview
6
7	Project memory files such as `CLAUDE.md` are the primary mechanism for providing project-specific context to coding agent sessions. This skill manages their complete lifecycle: discovery, quality assessment, reporting, and improvement. It follows a 5-phase workflow that ensures documentation is current, actionable, and concise.
8
9	The skill evaluates CLAUDE.md files against standardized quality criteria across 6 dimensions: Commands/Workflows, Architecture Clarity, Non-Obvious Patterns, Conciseness, Currency, and Actionability. Each file receives a score (0-100) and letter grade (A-F) with specific improvement recommendations.
10
11	## When to Use
12
13	Use this skill when:
14
15	- User explicitly asks to "check", "audit", "update", "improve", "fix", or "maintain" CLAUDE.md
16	- User mentions "CLAUDE.md quality", "documentation review", or "project memory optimization"
17	- A project memory file needs to be created from scratch for a new project
18	- User asks about improving Claude's understanding of the codebase
19	- Documentation has become stale or outdated
20	- Starting work on a new codebase and need to understand existing documentation
21	- User presses `#` during a session to incorporate learnings into a memory file
22
23	Trigger phrases: "audit CLAUDE.md", "check documentation quality", "improve project context", "review CLAUDE.md", "validate documentation"
24
25	## Instructions
26
27	### Phase 1: Discovery
28
29	Find all CLAUDE.md files in the repository:
30
31	```bash
32	find . -name "CLAUDE.md" -o -name ".claude.md" -o -name ".claude.local.md" 2>/dev/null \| head -50
33	```
34
35	File Types & Locations:
36
37	\| Type \| Location \| Purpose \|
38	\|------\|----------\|---------\|
39	\| Project root \| `./CLAUDE.md` \| Primary project context (checked into git, shared with team) \|
40	\| Local overrides \| `./.claude.local.md` \| Personal/local settings (gitignored, not shared) \|
41	\| Global defaults \| `~/.claude/CLAUDE.md` \| User-wide defaults across all projects \|
42	\| Package-specific \| `./packages/*/CLAUDE.md` \| Module-level context in monorepos \|
43	\| Subdirectory \| Any nested location \| Feature/domain-specific context \|
44
45	### Phase 2: Quality Assessment
46
47	For each CLAUDE.md file, read [references/quality-criteria.md](references/quality-criteria.md) and evaluate against these criteria:
48
49	\| Criterion \| Weight \| What to Check \|
50	\|-----------\|--------\|---------------\|
51	\| Commands/workflows \| 20 pts \| Are build/test/deploy commands present and working? \|
52	\| Architecture clarity \| 20 pts \| Can Claude understand the codebase structure? \|
53	\| Non-obvious patterns \| 15 pts \| Are gotchas and quirks documented? \|
54	\| Conciseness \| 15 pts \| Is content dense without filler? \|
55	\| Currency \| 15 pts \| Does it reflect current codebase state? \|
56	\| Actionability \| 15 pts \| Are instructions executable and copy-paste ready? \|
57
58	Quality Scores: A (90-100), B (70-89), C (50-69), D (30-49), F (0-29)
59
60	### Phase 3: Quality Report Output
61
62	CRITICAL: Always output the quality report BEFORE making any updates.
63
64	Format:
65	```markdown
66	## CLAUDE.md Quality Report
67
68	### Summary
69	- Files found: X
70	- Average score: X/100
71	- Files needing update: X
72
73	### File-by-File Assessment
74	#### 1. ./CLAUDE.md (Project Root)
75	Score: XX/100 (Grade: X)
76
77	\| Criterion \| Score \| Notes \|
78	\|-----------\|-------\|-------\|
79	\| Commands/workflows \| X/20 \| ... \|
80	\| Architecture clarity \| X/20 \| ... \|
81	\| Non-obvious patterns \| X/15 \| ... \|
82	\| Conciseness \| X/15 \| ... \|
83	\| Currency \| X/15 \| ... \|
84	\| Actionability \| X/15 \| ... \|
85
86	Issues:
87	- [List specific problems]
88
89	Recommended additions:
90	- [List what should be added]
91	```
92
93	### Phase 4: Targeted Updates
94
95	After report output, ask user for confirmation before updating.
96
97	Read [references/update-guidelines.md](references/update-guidelines.md) for detailed update principles.
98
99	Key principles:
100	1. Propose targeted additions only - commands, gotchas, patterns, configs
101	2. Keep it minimal - avoid obvious info, generic advice, one-off fixes
102	3. Show diffs - file, change (diff format), explanation
103
104	Diff format:
105	```markdown

People who liked this also viewed

6 picks

Type

memory-md-management

1.3kinstalls36forks

View on GitHub

How to install memory-md-management?

giuseppe-trisciuoglio/developer-kit/memory-md-management

$npx -y skills add giuseppe-trisciuoglio/developer-kit --skill memory-md-management

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Memory.md Management
2
3	Provides comprehensive project memory file management capabilities including auditing, quality assessment, and targeted improvements. This skill ensures the coding agent has optimal project context by maintaining high-quality documentation files such as `CLAUDE.md`.
4
5	## Overview
6
7	Project memory files such as `CLAUDE.md` are the primary mechanism for providing project-specific context to coding agent sessions. This skill manages their complete lifecycle: discovery, quality assessment, reporting, and improvement. It follows a 5-phase workflow that ensures documentation is current, actionable, and concise.
8
9	The skill evaluates CLAUDE.md files against standardized quality criteria across 6 dimensions: Commands/Workflows, Architecture Clarity, Non-Obvious Patterns, Conciseness, Currency, and Actionability. Each file receives a score (0-100) and letter grade (A-F) with specific improvement recommendations.
10
11	## When to Use
12
13	Use this skill when:
14
15	- User explicitly asks to "check", "audit", "update", "improve", "fix", or "maintain" CLAUDE.md
16	- User mentions "CLAUDE.md quality", "documentation review", or "project memory optimization"
17	- A project memory file needs to be created from scratch for a new project
18	- User asks about improving Claude's understanding of the codebase
19	- Documentation has become stale or outdated
20	- Starting work on a new codebase and need to understand existing documentation
21	- User presses `#` during a session to incorporate learnings into a memory file
22
23	Trigger phrases: "audit CLAUDE.md", "check documentation quality", "improve project context", "review CLAUDE.md", "validate documentation"
24
25	## Instructions
26
27	### Phase 1: Discovery
28
29	Find all CLAUDE.md files in the repository:
30
31	```bash
32	find . -name "CLAUDE.md" -o -name ".claude.md" -o -name ".claude.local.md" 2>/dev/null \| head -50
33	```
34
35	File Types & Locations:
36
37	\| Type \| Location \| Purpose \|
38	\|------\|----------\|---------\|
39	\| Project root \| `./CLAUDE.md` \| Primary project context (checked into git, shared with team) \|
40	\| Local overrides \| `./.claude.local.md` \| Personal/local settings (gitignored, not shared) \|
41	\| Global defaults \| `~/.claude/CLAUDE.md` \| User-wide defaults across all projects \|
42	\| Package-specific \| `./packages/*/CLAUDE.md` \| Module-level context in monorepos \|
43	\| Subdirectory \| Any nested location \| Feature/domain-specific context \|
44
45	### Phase 2: Quality Assessment
46
47	For each CLAUDE.md file, read [references/quality-criteria.md](references/quality-criteria.md) and evaluate against these criteria:
48
49	\| Criterion \| Weight \| What to Check \|
50	\|-----------\|--------\|---------------\|
51	\| Commands/workflows \| 20 pts \| Are build/test/deploy commands present and working? \|
52	\| Architecture clarity \| 20 pts \| Can Claude understand the codebase structure? \|
53	\| Non-obvious patterns \| 15 pts \| Are gotchas and quirks documented? \|
54	\| Conciseness \| 15 pts \| Is content dense without filler? \|
55	\| Currency \| 15 pts \| Does it reflect current codebase state? \|
56	\| Actionability \| 15 pts \| Are instructions executable and copy-paste ready? \|
57
58	Quality Scores: A (90-100), B (70-89), C (50-69), D (30-49), F (0-29)
59
60	### Phase 3: Quality Report Output
61
62	CRITICAL: Always output the quality report BEFORE making any updates.
63
64	Format:
65	```markdown
66	## CLAUDE.md Quality Report
67
68	### Summary
69	- Files found: X
70	- Average score: X/100
71	- Files needing update: X
72
73	### File-by-File Assessment
74	#### 1. ./CLAUDE.md (Project Root)
75	Score: XX/100 (Grade: X)
76
77	\| Criterion \| Score \| Notes \|
78	\|-----------\|-------\|-------\|
79	\| Commands/workflows \| X/20 \| ... \|
80	\| Architecture clarity \| X/20 \| ... \|
81	\| Non-obvious patterns \| X/15 \| ... \|
82	\| Conciseness \| X/15 \| ... \|
83	\| Currency \| X/15 \| ... \|
84	\| Actionability \| X/15 \| ... \|
85
86	Issues:
87	- [List specific problems]
88
89	Recommended additions:
90	- [List what should be added]
91	```
92
93	### Phase 4: Targeted Updates
94
95	After report output, ask user for confirmation before updating.
96
97	Read [references/update-guidelines.md](references/update-guidelines.md) for detailed update principles.
98
99	Key principles:
100	1. Propose targeted additions only - commands, gotchas, patterns, configs
101	2. Keep it minimal - avoid obvious info, generic advice, one-off fixes
102	3. Show diffs - file, change (diff format), explanation
103
104	Diff format:
105	```markdown

People who liked this also viewed

6 picks

Type