reflect

Audit CLAUDE.md, memory files, and settings for inconsistencies and stale artifacts.

17|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/alexiolan/craft-skills --skill reflect-alexiolan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reflect
Source: https://github.com/alexiolan/craft-skills/tree/main/skills/reflect
Command: npx skills add https://github.com/alexiolan/craft-skills --skill reflect-alexiolan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when auditing, improving, or maintaining project health — CLAUDE.md accuracy, memory hygiene, settings, plans, and pattern discovery. Invoke periodically or when the user asks to audit or improve their project configuration.

Core Features & Use Cases

  • Health and configuration audits for CLAUDE.md, memory, and settings
  • Pattern discovery and documentation improvement for project governance
  • Guidance to align project artifacts with reality and coding standards
  • Use Case: Regularly audit a repository to surface misconfigurations and opportunities for improvement

Quick Start

Run a health audit to compare CLAUDE.md and memory state against the codebase and surface actionable improvements.

Frequently Asked Questions about reflect

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

FAQPage Schema
How do I audit my Claude project configuration and memory files for inconsistencies?

To audit your Claude project configuration, run a health audit that compares CLAUDE.md and memory state against your codebase to surface misconfigurations, detect stale artifacts, and provide actionable improvement reports.

What is the best way to discover and document coding patterns in my repository?

The best way to discover coding patterns is through a pattern evolution phase that analyzes your repository artifacts, detects existing patterns, and generates documentation improvements to align project artifacts with reality and coding standards.

How do I clean up stale artifacts across my project health phases?

You can clean up stale artifacts by executing a Phase 3 cleanup process that identifies outdated files and configurations across your project, generating suggested fixes to maintain accurate project governance and memory hygiene.

Does the project audit work without external dependencies?

Yes, the project audit works without external dependencies, requiring only your existing Claude-based project configurations including CLAUDE.md, memory files, and settings to detect inconsistencies and suggest fixes.

When should I run a project health audit on my codebase?

You should run a project health audit periodically or when you need to verify CLAUDE.md accuracy, perform memory hygiene, review settings, or surface opportunities to align project artifacts with your current coding standards.

Why does my CLAUDE.md configuration drift from the actual codebase over time?

Your CLAUDE.md configuration drifts as the codebase evolves without corresponding updates to memory files and settings, creating stale artifacts that a health audit can detect by comparing configuration state against reality.