/stats — Knowledge Base Health

Read-only dashboard showing the current state of the knowledge repository.

Runtime Gate (per ADR-094)

Canonical resolution: This is the Claude Code variant. When both plugin-claude-code and plugin-claude-cowork are loaded in the same session (most common in Claude Desktop), bare /stats resolves to this skill — aria-knowledge (Code) is the canonical owner of all 24 dual-port skills per ADR-094 §Part 1. The Cowork variant is namespaced-only: /aria-cowork:stats.

Before Step 0: Check that the Bash tool is available in this session. If Bash is NOT available (you are running in Claude Cowork or another non-Code runtime), surface the following notification and wait for explicit user confirmation:

⚠️ Runtime mismatch — you invoked aria-knowledge's /stats from a non-Code runtime.

Behavior is largely the same in both runtimes; for the Cowork-native variant (reads from the attached knowledge folder), use /aria-cowork:stats.

Use /aria-cowork:stats instead? (y / n)

Wait for an explicit reply:

• y / yes — Use the Skill tool to invoke aria-cowork:stats with the same arguments the user provided to this invocation. Do not proceed with this skill's steps; the cowork variant takes over and runs to completion. This is the default-yes path — auto-redirect is the helpful action.
• n / no — Proceed with this (aria-knowledge) variant anyway despite the runtime mismatch. The user has explicitly opted in.
• No response / any other reply — Treat as "do not proceed" and exit cleanly without running either variant.

This gate applies even when mode = auto per ADR-094 §Part 3. Auto mode's "implicit-yes on all gates" rule is suspended for the runtime-mismatch check — auto trusts that the user invoked the correct variant, and this gate enforces that precondition. All other auto-mode gates remain bypassed. The friction cost is now low: on y, the auto-redirect runs the correct variant with the original args.

If Bash is available, proceed to Step 0.

Step 0: Resolve Config

Read ~/.claude/aria-knowledge.local.md and extract knowledge_folder. If the file doesn't exist, stop: "aria-knowledge is not configured. Run /setup to get started."

Use {knowledge_folder} as the base path for all operations.

Step 1: Count Promoted Files

Count .md files (excluding README.md) in each promoted folder:

• {knowledge_folder}/rules/*.md
• {knowledge_folder}/approaches/*.md
• {knowledge_folder}/decisions/*.md
• {knowledge_folder}/guides/**/*.md (recursive — guides may have subdirectories)
• {knowledge_folder}/references/*.md
• {knowledge_folder}/archive/*.md

Record counts per category and total.

Step 2: Count Backlog Items

For each backlog file, count the number of ### (h3) entries below the --- separator:

• {knowledge_folder}/intake/insights-backlog.md
• {knowledge_folder}/intake/decisions-backlog.md
• {knowledge_folder}/intake/extraction-backlog.md
• {knowledge_folder}/intake/rules-backlog.md

Also count .md files in {knowledge_folder}/intake/pre-compact-captures/.

Also count .md files in {knowledge_folder}/intake/clippings/ (unreviewed clippings).

Step 3: Read Audit Dates

Extract the **Date:** from:

• {knowledge_folder}/logs/knowledge-audit-log.md
• {knowledge_folder}/logs/config-audit-log.md
• The /setup on date from ~/.claude/aria-knowledge.local.md

Calculate days since each. If a date is "(no audits yet)" or missing, note "never."

Step 3a: Check Codemap Dates

Use Glob to find CODEMAP.md files under cwd (up to 2 levels deep). Try these patterns:

• CODEMAP.md (depth 0)
• */CODEMAP.md (depth 1)
• */*/CODEMAP.md (depth 2)

For each file found:

1. Read the first 10 lines
2. Parse the Last updated date from the header. Expected pattern: > Last updated: YYYY-MM-DD | Sections: N | Features: M
3. Calculate days-since from today's date

If the header is missing or unparseable, show (no date) for that entry.

If no CODEMAP.md files are found under cwd, the section still renders with a single line noting absence.

Presentation-only. This step does not classify stale/current or run git-activity checks. Staleness classification with file-change detection belongs to /audit-knowledge Step 5d — /stats just surfaces the raw date so the user can decide whether to run the audit.

Step 3b: Cross-Project Tracked Artifacts (added v2.16.1)

In addition to the cwd-scoped Glob in Step 3a, iterate KT_PROJECTS_LIST (from config) to surface CODEMAP + STITCH dates across ALL configured projects — a dashboard view, not just the current working directory.

Skip this step entirely if KT_PROJECTS_ENABLED != true or KT_PROJECTS_LIST is empty.

For each tag:path entry in projects_list:

1. Resolve project_root = $HOME/Projects/<path>. If directory doesn't exist, note "(configured but missing)" and continue.
2. Stat {project_root}/CODEMAP.md:
   • If exists, parse > Last updated: YYYY-MM-DD from the header (or fall back to mtime). Compute days-since.
   • If missing, note "(no CODEMAP)".
3. Stat {project_root}/STITCH.md:
   • If exists, days-since via mtime (STITCH files don't carry a header date in v2.16.x).
   • If missing, note as single-repo (suppress this row entirely if user prefers terseness — or render "(single-repo, no STITCH)").
4. Classify against thresholds: codemap_staleness_threshold_days (default 14) and stitch_staleness_threshold_days (default 30). Status = fresh / STALE (>threshold) / REFUSAL-ZONE (>2× threshold).

Presentation-only. Same discipline as Step 3a — surfaces dates + status without auto-acting. Pairs with /audit-config Step 5a, which produces actionable findings.

Step 4: Index Health (if index.md exists)

If {knowledge_folder}/index.md exists, read it and extract:

• Known tags count: count lines in ## Known Tags section
• Top tags: from ## Tag Index, count files listed under each ### tag header, sort by count, show top 5
• Stale files: read ## Stale Files section, count entries
• Untagged files: read ## Untagged Files section, count entries
• Semantic-hints coverage (added 2.16.0): count files declaring semantic-hints: frontmatter / total promoted files; report as N of M (P%). Always emit (zero coverage = "0 of M (0%)") to track adoption over time. Source: scan promoted-folder files (same set as Step 1) for the semantic-hints: field; matches /index's Semantic Hints Index input.

If index.md doesn't exist, note: "No index — run /index to build."

Step 5: Coverage Gaps

Check which promoted folders have zero .md files (excluding README.md):

• If approaches/ is empty: note it
• If decisions/ is empty: note it
• If guides/ is empty: note it
• If references/ is empty: note it

These suggest areas where knowledge capture hasn't started yet.

Step 6: Present

Output in this format:

Output policy: emit every section defined in the format below with all fields, even when counts are zero. Zero counts are meaningful data points — "Pending insights: 0" confirms the backlog is clear, "Stale files: 0" confirms the index is current. Do not collapse the dashboard into prose or shorten sections for brevity — the structured format is the skill's value, enabling trend comparison across runs. The Index Health and Coverage Gaps sections have explicit conditional branches embedded in the template; all other sections are always-emit.

## Knowledge Stats

### Repository
- Promoted files: N total
  - Rules: N
  - Approaches: N
  - Decisions: N
  - Guides: N
  - References: N
- Archived: N

### Intake
- Pending insights: N
- Pending decisions: N
- Pending extractions: N
- Pending rules: N
- Unreviewed clippings: N
- Pre-compact captures: N

### Audit Status
- Knowledge audit: [YYYY-MM-DD (N days ago) | never]
- Config audit: [YYYY-MM-DD (N days ago) | never]
- Last /setup: [YYYY-MM-DD (N days ago)]

### Codema