Status

Status

Memory health dashboard showing line counts, topic files, capacity, stale entries, and recommendations

Category: development Source: alirezarezvani/claude-skills

What Is Status?

The Status skill is a diagnostic tool for developers using the Claude codebase. It provides a comprehensive memory health dashboard, enabling users to assess and monitor the state of their project's memory systems. With a single command, Status analyzes line counts, topic file proliferation, memory capacity, stale references, and offers actionable recommendations. This empowers teams to maintain memory hygiene, preventing bottlenecks and confusion as projects scale. Status is particularly useful for those leveraging Claude’s self-improving agent workflows, where persistent project memory is critical to performance and accuracy.

Why Use Status?

As projects grow, memory files such as MEMORY.md, topic-related Markdown files, and configuration documents like CLAUDE.md can become bloated or outdated. Excessive line counts, obsolete file references, and unmanaged topic sprawl degrade the efficiency of automated agents and developers alike. Status addresses these challenges by:

  • Providing instant visibility into key memory health metrics.
  • Highlighting potential capacity issues before they impact performance.
  • Detecting and reporting stale entries, reducing confusion from broken links or references.
  • Offering recommendations to keep project memory well-structured and actionable.

By integrating Status into your development workflow, you ensure that your project’s memory is always in an optimal state, reducing technical debt and improving productivity.

How to Get Started

To use the Status skill, first ensure it is installed in your Claude skillset. The core interface is a simple command-line invocation:

/si:status

This produces a full dashboard of your project’s memory health. For a concise summary, use the brief option:

/si:status --brief

Status automatically locates and analyzes all relevant memory files, including:

  • The main MEMORY.md in your project’s auto-memory directory.
  • All topic Markdown files in the same directory.
  • Primary and global CLAUDE.md files.
  • Rule files in .claude/rules/.

No manual configuration is required, and Status adapts to the current working directory.

Key Features

1. Memory File Discovery

Status scans your project’s auto-memory directory, identifying all major memory-related files. For example:

MEMORY_DIR="$HOME/.claude/projects/$(pwd | sed 's|/|%2F|g; s|%2F|/|; s|^/||')/memory"
ls "$MEMORY_DIR/"*.md 2>/dev/null

It distinguishes between the main MEMORY.md and additional topic files, ensuring a holistic overview.

2. Line Count and Capacity Analysis

Status evaluates line counts in critical files, flagging them based on predefined thresholds:

Metric Healthy Warning Critical
MEMORY.md lines < 120 120-180 > 180
CLAUDE.md lines < 150 150-200 > 200
Topic files 0-3 4-6 > 6
Stale entries 0 1-3 > 3

For example, to count lines:

wc -l "$MEMORY_DIR/MEMORY.md" 2>/dev/null || echo "0"

3. Stale Entry Detection

Status checks for file references in MEMORY.md that no longer exist in the file system, reducing the risk of broken context for agents and contributors. Example:

grep -oE '[a-zA-Z0-9_/.-]+\.(ts|js|py|md|json|yaml|yml)' "$MEMORY_DIR/MEMORY.md" | while read f; do
  [ ! -f "$f" ] && echo "STALE: $f"
done

4. Actionable Recommendations

Based on its findings, Status suggests actions such as pruning old topics, splitting large files, or removing stale references, keeping your memory resources healthy and effective.

Best Practices

  • Run /si:status regularly, especially after major project changes or memory updates.
  • Address warnings and critical alerts promptly to avoid memory overload.
  • Limit the number of topic files; consolidate related topics to reduce fragmentation.
  • Routinely review and update file references in MEMORY.md to prevent staleness.
  • Use the brief output in automated CI pipelines for lightweight monitoring.

Important Notes

  • Status assumes a standard Claude project directory layout. Custom setups may require adaptation.
  • The thresholds for healthy, warning, and critical states are configurable in the underlying scripts if your project has unique needs.
  • Status does not modify any files; it is strictly diagnostic. All changes must be performed manually based on its recommendations.
  • Ensure your shell environment supports the necessary commands (e.g., wc, grep, ls) for Status to function correctly.
  • For further customization or troubleshooting, consult the official repository.