AGENT SKILL

gk-data-memory-review

Analyze auto-memory for promotion candidates, stale entries, consolidation opportunities, and health metrics. Use when the user runs /si:memory-review or asks what has been learned and what should be promoted or pruned.

License 许可
Apache-2.0
最近更新
2026-11-08
Stars
★ 0
Forks
0

01 前言 Front Matter

name
gk-data-memory-review
description
Analyze auto-memory for promotion candidates, stale entries, consolidation opportunities, and health metrics. Use when the user runs /si:memory-review or asks what has been learned and what should be promoted or pruned.

03 SKILL.md 正文

memory-review

Performs a comprehensive audit of Claude Code's auto-memory and produces actionable recommendations.

Usage

/si:memory-review                    # Full review
/si:memory-review --quick            # Summary only (counts + top 3 candidates)
/si:memory-review --stale            # Focus on stale/outdated entries
/si:memory-review --candidates       # Show only promotion candidates

What It Does

Step 1: Locate memory directory

# Find the project's auto-memory directory
MEMORY_DIR="$HOME/.claude/projects/$(pwd | sed 's|/|%2F|g; s|%2F|/|; s|^/||')/memory"

# Fallback: check common path patterns
# ~/.claude/projects/<user>/<project>/memory/
# ~/.claude/projects/<absolute-path>/memory/

# List all memory files
ls -la "$MEMORY_DIR"/

If memory directory doesn't exist, report that auto-memory may be disabled. Suggest checking with /memory.

Step 2: Read and analyze MEMORY.md

Read the full MEMORY.md file. Count lines and check against the 200-line startup limit.

Analyze each entry for:

  1. Recurrence indicators

    • Same concept appears multiple times (different wording)
    • References to "again" or "still" or "keeps happening"
    • Similar entries across topic files
  2. Staleness indicators

    • References files that no longer exist (find to verify)
    • Mentions outdated tools, versions, or commands
    • Contradicts current CLAUDE.md rules
  3. Consolidation opportunities

    • Multiple entries about the same topic (e.g., three lines about testing)
    • Entries that could merge into one concise rule
  4. Promotion candidates — entries that meet ALL criteria:

    • Appeared in 2+ sessions (check wording patterns)
    • Not project-specific trivia (broadly useful)
    • Actionable (can be written as a concrete rule)
    • Not already in CLAUDE.md or .claude/rules/

Step 3: Read topic files

If MEMORY.md references or the directory contains additional files (debugging.md, patterns.md, etc.):

  • Read each one
  • Cross-reference with MEMORY.md for duplicates
  • Check for entries that belong in the main file (high value) vs. topic files (details)

Step 4: Cross-reference with CLAUDE.md

Read the project's CLAUDE.md (if it exists) and compare:

Also check .claude/rules/ directory for existing scoped rules.

Step 5: Generate report

Output format:

📊 Auto-Memory Review

Memory Health:
  MEMORY.md:        {{lines}}/200 lines ({{percent}}%)
  Topic files:      {{count}} ({{names}})
  CLAUDE.md:        {{lines}} lines
  Rules:            {{count}} files in .claude/rules/

🎯 Promotion Candidates ({{count}}):
  1. "{{pattern}}" — seen {{n}}x, applies broadly
     → Suggest: {{target}} (CLAUDE.md / .claude/rules/{{name}}.md)
  2. ...

🗑️ Stale Entries ({{count}}):
  1. Line {{n}}: "{{entry}}" — {{reason}}
  2. ...

🔄 Consolidation ({{count}} groups):
  1. Lines {{a}}, {{b}}, {{c}} all about {{topic}} → merge into 1 entry
  2. ...

⚠️ Conflicts ({{count}}):
  1. MEMORY.md line {{n}} contradicts CLAUDE.md: {{detail}}

💡 Recommendations:
  - {{actionable suggestion}}
  - {{actionable suggestion}}

When to Use

  • After completing a major feature or debugging session
  • When /si:memory-status shows MEMORY.md is over 150 lines
  • Weekly during active development
  • Before starting a new project phase
  • After onboarding a new team member (review what Claude learned)

Tips

  • Run /si:memory-review --quick frequently (low overhead)
  • Full review is most valuable when MEMORY.md is getting crowded
  • Act on promotion candidates promptly — they're proven patterns
  • Don't hesitate to delete stale entries — auto-memory will re-learn if needed

04 同仓库更多 Skills

makeyzhang-cpu
makeyzhang-cpu/geekclaw

drive-geekclaw

Use to connect to and drive a GeekClaw instance from an external agent (Claude Code / Cursor / any MCP client). Drive its browser / computer / knowledge base / files and manage the platform over MCP or REST, with a per-companion access token (you run AS the bound companion). Use this whenever the user asks to control, automate, or hand work off to "GeekClaw", "their GeekClaw", "the desktop companion", or a running GeekClaw server.

★ 0
makeyzhang-cpu
makeyzhang-cpu/geekclaw

example-skill

Fixture skill used by startup_materialize integration tests.

★ 0
makeyzhang-cpu
makeyzhang-cpu/geekclaw

ui-ux-pro-max

Professional UI/UX design research skill with a bundled searchable database for product patterns, visual styles, color palettes, typography, landing-page structure, dashboard charts, UX practices, and stack guidance. Use when designing, building, reviewing, or improving interfaces.

★ 0
makeyzhang-cpu
makeyzhang-cpu/geekclaw

planning-with-files

Maintain durable task plans, findings, and progress logs in workspace files for long-running or research-heavy work. Use when a task spans many steps or sessions, needs an auditable evidence trail, or risks losing important decisions to context limits. Do not use for short tasks that fit comfortably in the active conversation.

★ 0
makeyzhang-cpu
makeyzhang-cpu/geekclaw

officecli

Create, analyze, proofread, and modify Office documents (.docx, .xlsx, .pptx) using the officecli CLI tool. Use when the user wants to create, inspect, check formatting, find issues, add charts, or modify Office documents.

★ 0
makeyzhang-cpu
makeyzhang-cpu/geekclaw

officecli-xlsx

Use this skill any time a .xlsx file is involved -- as input, output, or both. This includes: creating spreadsheets, financial models, dashboards, or trackers; reading, parsing, or extracting data from any .xlsx file; editing, modifying, or updating existing workbooks; working with formulas, charts, pivot tables, or templates; importing CSV/TSV data into Excel format. Trigger whenever the user mentions 'spreadsheet', 'workbook', 'Excel', 'financial model', 'tracker', 'dashboard', or references a .xlsx/.csv filename.

★ 0