RE

review-claudemd

Reviews past conversations to identify and implement improvements to CLAUDE.md configuration files.

Install

mkdir -p .claude/skills/review-claudemd && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/3345" && unzip -o skill.zip -d .claude/skills/review-claudemd && rm skill.zip

Installs to .claude/skills/review-claudemd

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Review recent conversations to find improvements for CLAUDE.md files.
69 charsno explicit “when” trigger
Advanced

Key capabilities

  • Parses conversational history from project folders
  • Extracts patterns from JSONL log files
  • Deploys parallel analysis subagents
  • Identifies rule violations in CLAUDE.md
  • Recommends updates for local/global configuration

How it works

It processes conversation history logs using scripts to segment data, then prompts secondary AI agents to audit content against existing rules.

Inputs & outputs

You give it
Request to review project history
You get back
Specific feedback points for CLAUDE.md

When to use review-claudemd

  • Review past project conversations
  • Update local CLAUDE.md rules
  • Refine global assistant guidelines
  • Analyze project interaction history

About this skill

Review CLAUDE.md from conversation history

Analyze recent conversations to improve both global (~/.claude/CLAUDE.md) and local (project) CLAUDE.md files.

Step 1: Find conversation history

The project's conversation history is in ~/.claude/projects/. The folder name is the project path with slashes replaced by dashes.

# Find the project folder (replace / with -)
PROJECT_PATH=$(pwd | sed 's|/|-|g' | sed 's|^-||')
CONVO_DIR=~/.claude/projects/-${PROJECT_PATH}
ls -lt "$CONVO_DIR"/*.jsonl | head -20

Step 2: Extract recent conversations

Extract the 15-20 most recent conversations (excluding the current one) to a temp directory:

SCRATCH=/tmp/claudemd-review-$(date +%s)
mkdir -p "$SCRATCH"

for f in $(ls -t "$CONVO_DIR"/*.jsonl | head -20); do
  basename=$(basename "$f" .jsonl)
  # Skip current conversation if known
  cat "$f" | jq -r '
    if .type == "user" then
      "USER: " + (.message.content // "")
    elif .type == "assistant" then
      "ASSISTANT: " + ((.message.content // []) | map(select(.type == "text") | .text) | join("\n"))
    else
      empty
    end
  ' 2>/dev/null | grep -v "^ASSISTANT: $" > "$SCRATCH/${basename}.txt"
done

ls -lhS "$SCRATCH"

Step 3: Spin up subagents

Launch parallel subagents to analyze conversations. Each agent should read:

  • Global CLAUDE.md: ~/.claude/CLAUDE.md
  • Local CLAUDE.md: ./CLAUDE.md (if exists)
  • Batch of conversation files

Give each agent this prompt template:

Read:
1. Global CLAUDE.md: ~/.claude/CLAUDE.md
2. Local CLAUDE.md: [project]/CLAUDE.md
3. Conversations: [list of files]

Analyze the conversations against BOTH CLAUDE.md files. Find:
1. Instructions that exist but were violated (need reinforcement or rewording)
2. Patterns that should be added to LOCAL CLAUDE.md (project-specific)
3. Patterns that should be added to GLOBAL CLAUDE.md (applies everywhere)
4. Anything in either file that seems outdated or unnecessary

Be specific. Output bullet points only.

Batch conversations by size:

  • Large (>100KB): 1-2 per agent
  • Medium (10-100KB): 3-5 per agent
  • Small (<10KB): 5-10 per agent

Step 4: Aggregate findings

Combine results from all agents into a summary with these sections:

  1. Instructions violated - existing rules that weren't followed (need stronger wording)
  2. Suggested additions - LOCAL - project-specific patterns
  3. Suggested additions - GLOBAL - patterns that apply everywhere
  4. Potentially outdated - items that may no longer be relevant

Present as tables or bullet points. Ask user if they want edits drafted.

When not to use it

  • Projects without conversation logs
  • Simple tasks with very few interactions

Prerequisites

jqProject conversation logs

Limitations

  • Sensitive information might exist in conversation logs
  • Analysis results are only as good as the subagent prompts

How it compares

It turns passive interaction history into active configuration refinement, unlike manual file editing.

Compared to similar skills

review-claudemd side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
review-claudemd (this skill)16moReviewAdvanced
windsurf-custom-prompts12moNo flagsBeginner
documentation-review115moNo flagsBeginner
docs-review107moNo flagsBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

windsurf-custom-prompts

jeremylongshore

Create and manage custom prompt libraries for Cascade. Activate when users mention "custom prompts", "prompt library", "prompt templates", "cascade prompts", or "prompt management". Handles prompt library creation and organization. Use when working with windsurf custom prompts functionality. Trigger with phrases like "windsurf custom prompts", "windsurf prompts", "windsurf".

14

documentation-review

stacklok

Reviews documentation for factual accuracy

1194

docs-review

metabase

Review documentation changes for compliance with the Metabase writing style guide. Use when reviewing pull requests, files, or diffs containing documentation markdown files.

1085

workthrough

bear2u

Automatically document all development work and code modifications in a structured workthrough format. Use this skill after completing any development task, bug fix, feature implementation, or code refactoring to create comprehensive documentation.

1085

claude-md-improver

anthropics

Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project memory optimization".

2167

anti-slop

rand

Comprehensive toolkit for detecting and eliminating "AI slop" - generic, low-quality AI-generated patterns in natural language, code, and design. Use when reviewing or improving content quality, preventing generic AI patterns, cleaning up existing content, or enforcing quality standards in writing, code, or design work.

1244

Search skills

Search the agent skills registry