strata-audit-config

name	strata:audit-config
disable-model-invocation	true
description	Check the project's Claude Code config (CLAUDE.md, .claude/settings.json, skills, agents) for staleness. Read-only. Use when the user says "review our Claude config", "is our CLAUDE.md stale", "audit the setup", or after upgrading to a new model. Command-only — run it explicitly as /strata:audit-config.

strata:audit-config

Anthropic's 2026 guidance on Claude Code in large codebases:

Teams should expect to do a meaningful configuration review every three to six months, but it's also worth doing one whenever performance feels like it's plateaued after major model releases.

Instructions optimized for older models can work against a future one.

This skill is the operational reminder. It walks your project's Claude Code Config and reports items that haven't been touched in --stale-days (180 by Default), so you can revisit them deliberately.

When to run

• Every 3–6 months as a scheduled habit
• After a major Claude model release (Anthropic-recommended)
• Before onboarding a new team to the codebase
• When Claude's behaviour starts feeling sluggish or off

How

# Default: 180-day staleness threshold
"${CLAUDE_PLUGIN_ROOT}/bin/strata" audit-config

# Tighter cadence
"${CLAUDE_PLUGIN_ROOT}/bin/strata" audit-config --stale-days 90

What it covers

File / dir	Why it matters
CLAUDE.md	Loaded every session; conventions drift
.claude/settings.json	Team config; check enabled plugins are still relevant
.claudeignore	Exclusion rules go stale as the repo evolves
.claude/skills/	Project-local skills — same drift risk
.claude/agents/	Sub-agent definitions — same

Read-only, never modifies. Output is a markdown report you can paste into a Review meeting.

Pairs well with

• /strata:review — audits the vault (decisions, lessons, domain notes)
• /strata:audit-config — audits the project's Claude Code setup

Different surfaces. Run both on the same cadence.