From gir-core
Assess whether the `.gir/` memory bank is stale and recommend what to update.
npx claudepluginhub rivit-studio/gir --plugin gir-coreThis skill uses the workspace's default tool permissions.
Assess whether the `.gir/` memory bank is stale and recommend what to update.
Organizes, extracts, prunes, and verifies Claude Code persistent memory files: MEMORY.md index, topic extraction, staleness detection, accuracy checks. Use near 200-line limit, after insights, or project changes.
Audits Claude Code auto-memory (MEMORY.md, topic files) for promotion candidates to CLAUDE.md, stale entries, duplicates, consolidation opportunities, and health metrics.
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.
Share bugs, ideas, or general feedback.
Assess whether the .gir/ memory bank is stale and recommend what to update.
Follow these steps in order:
.gir/CLAUDE-activeContext.md existsCheck whether .gir/CLAUDE-activeContext.md exists in the current project directory.
If it does not exist, respond with:
No memory bank found.
.gir/CLAUDE-activeContext.md does not exist in this directory.
To set up a memory bank, run:
/gir-core:init-memory-bank
The memory bank helps Claude restore context at the start of each session and track decisions, patterns, and known issues across sessions.
Then stop — do not proceed further.
If it does exist, continue to Step 2.
Check which of the following files exist in .gir/:
CLAUDE-activeContext.mdCLAUDE-decisions.mdCLAUDE-patterns.mdCLAUDE-resources.mdCLAUDE-troubleshooting.mdFor each file that exists, read it.
For each file that exists, determine its freshness:
For CLAUDE-activeContext.md:
[Date/Time]): mark as "never updated"For CLAUDE-decisions.md:
### [YYYY-MM-DD] headings)For CLAUDE-patterns.md:
For CLAUDE-resources.md:
https:// links beyond the template examples)For CLAUDE-troubleshooting.md:
Present a clean summary:
Memory Bank Status
------------------
Files present:
[checkmark or X] CLAUDE-activeContext.md [status: e.g., "updated 3 days ago" | "never updated" | "has placeholder text"]
[checkmark or X] CLAUDE-decisions.md [status: e.g., "2 decisions logged" | "empty (template only)"]
[checkmark or X] CLAUDE-patterns.md [status: e.g., "partially filled" | "empty (template only)"]
[checkmark or X] CLAUDE-resources.md [status: e.g., "3 URLs added" | "empty (template only)"]
[checkmark or X] CLAUDE-troubleshooting.md [status: e.g., "1 issue documented" | "empty (template only)"]
Missing files (if any):
[list any of the 5 files that do not exist]
Based on what you found, suggest specific actions. Prioritize in this order:
Format recommendations as actionable items:
Recommendations
---------------
[Priority 1 — if activeContext is stale or empty]:
CLAUDE-activeContext.md hasn't been updated recently.
Update it now with:
- Your current session goals
- What's in progress
- Any blockers or recent decisions
[Priority 2 — if patterns is empty]:
CLAUDE-patterns.md is empty.
As you develop conventions (naming, component structure, API patterns),
document them here so Claude can follow them consistently.
[Priority 3 — if decisions is empty but the project seems mature]:
No architectural decisions have been logged.
If your project has made choices about state management, API design,
database schema, etc., consider documenting the rationale in CLAUDE-decisions.md.
[If everything looks current]:
Memory bank looks up to date. No urgent action needed.
Consider reviewing CLAUDE-activeContext.md at the start of each new session.