mirror of
https://github.com/alirezarezvani/claude-skills.git
synced 2026-09-07 08:26:02 +00:00
d928ec95d5
- CHANGELOG.md gains the [2.12.0] entry (first tagged release since v2.9.0):
consolidates the previously documented but untagged v2.10.0-v2.11.2 work,
all post-2.11.2 merges, and the full 17-issue triage sweep; the ten stacked
[Unreleased] sections are demoted into the 2.12.0 body so the Release
workflow tags and publishes the whole span. Verified parseable with
scripts/extract_release_notes.py (version 2.12.0, 554-line body).
- Version markers bumped to 2.12.0: marketplace.json metadata,
CLAUDE.md current-version header + footer.
- Counters trued to the derived values (380 skills / 96 plugins / 20 domains /
706 tools / 823 refs / 114 agents / 138 commands) in README badges + prose,
CLAUDE.md, marketplace.json, and the long-stale mkdocs.yml/docs/index.md
site description (was still claiming 345/78/17).
- Docs site regenerated via scripts/generate-docs.py (568 generated pages;
new pages for the recently merged plugins); codex/gemini mirrors resynced;
mkdocs build verified locally with the same plugin set static.yml uses
(670 HTML pages, no errors).
- Fix: the three hivemind worker personas (assets/agents/{coder,scout,tester}.md,
merged via #979 while Actions was not triggering) lacked the frontmatter
`name:` field and hard-failed the blocking G10 gate — named
hive-coder/hive-scout/hive-tester; 645 files now scan with 0 errors.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Qgc6RYXWJPr5oW9DHU7zR4
107 lines
4.2 KiB
Markdown
107 lines
4.2 KiB
Markdown
---
|
|
title: "/cs-memory — Slash Command for AI Coding Agents"
|
|
description: "Inspect, trace, and adopt the tiered agent-memory store (status | why | contested | adopt | forget). Slash command for Claude Code, Codex CLI, Gemini CLI."
|
|
---
|
|
|
|
# /cs-memory
|
|
|
|
<div class="page-meta" markdown>
|
|
<span class="meta-badge">:material-console: Slash Command</span>
|
|
<span class="meta-badge">:material-github: <a href="https://github.com/alirezarezvani/2-claude-skills/tree/main/engineering/agent-memory/commands/cs-memory.md">Source</a></span>
|
|
</div>
|
|
|
|
|
|
Argument: `$ARGUMENTS` (default: `status`)
|
|
|
|
Scripts live at
|
|
`engineering/agent-memory/skills/agent-memory/scripts/`. All are stdlib-only and
|
|
read-only except where stated.
|
|
|
|
---
|
|
|
|
## `status` (default)
|
|
|
|
1. Run `memory_inspect.py --tier L3`, `--tier L2`, `--tier L1`.
|
|
2. Read `.memory/staged/promotions.json` if it exists.
|
|
3. Read the last 7 days of `.memory/errors.log` if it exists — **surface any
|
|
entry**. That file is where silently dropped writes are recorded, and a log
|
|
nobody is pointed at is the same as no log.
|
|
|
|
Report, in this order: what is always loaded (L3), what this project loads (L2),
|
|
how many candidates are waiting and what is blocking each, what is staged for
|
|
adoption, and any dropped writes.
|
|
|
|
**Do not adopt anything here.** `status` is read-only.
|
|
|
|
---
|
|
|
|
## `why "<claim>"`
|
|
|
|
Run `memory_inspect.py --why "<claim>"`.
|
|
|
|
Report the full provenance: observation count, distinct sessions, distinct
|
|
calendar days, first and latest transcript back-pointers, whether each resolves,
|
|
and the quoted source line when exactly one transcript matched.
|
|
|
|
If the resolution status is **`ambiguous`**, say so plainly and print no source
|
|
line. Two projects can hold a transcript of the same basename; guessing attaches
|
|
a real claim to the wrong session, and a wrong citation is worse than none.
|
|
|
|
---
|
|
|
|
## `contested`
|
|
|
|
Run `memory_inspect.py --contested`.
|
|
|
|
For each pair, present both claims with their dates and sources side by side and
|
|
ask the user which governs. **Do not pick.** Do not merge them. Do not mark one
|
|
resolved on your own judgement — resolution is a human decision by design.
|
|
|
|
---
|
|
|
|
## `adopt`
|
|
|
|
The only command in this file that writes. Six steps, in order, no skipping:
|
|
|
|
1. Run `memory_promote.py --stage` to refresh `.memory/staged/promotions.json`.
|
|
2. **Back up both `CLAUDE.md` files** (project and global) with a timestamped
|
|
copy. Do this before writing anything, every time.
|
|
3. Walk the staged list **one atom at a time**. For each, show the claim, the
|
|
evidence (sessions, days, sources), and the target file. Wait for the user.
|
|
4. **Refuse outright** any atom with `redacted: true` — no amount of evidence
|
|
substitutes for the human reading the original. Explain why and move on.
|
|
5. **Refuse** any atom whose citation does not resolve.
|
|
6. Append accepted atoms to the target `CLAUDE.md` under a clearly marked
|
|
`<!-- agent-memory: adopted -->` section, and log each to `.memory/adopted.log`.
|
|
|
|
Never write to a `CLAUDE.md` outside this flow. Never batch-accept.
|
|
|
|
---
|
|
|
|
## `forget "<claim>"`
|
|
|
|
1. Locate the atom with `memory_inspect.py --why "<claim>"`.
|
|
2. Show the user exactly what will be removed, from which tier, and whether it
|
|
was already adopted into a `CLAUDE.md`.
|
|
3. On confirmation, remove it from `.memory/atoms.jsonl` and, if it was adopted,
|
|
remove the corresponding line from the `CLAUDE.md` — after backing that file
|
|
up.
|
|
|
|
Removing an atom does **not** prevent re-learning. If the marker fires again in
|
|
a future session, it returns. That is correct: forgetting is not a permanent
|
|
veto, and saying so avoids a confusing surprise later. To stop it returning,
|
|
change the underlying fact or state the correction — a correction is itself a
|
|
high-confidence observation.
|
|
|
|
---
|
|
|
|
## Refuse and route
|
|
|
|
- No `.memory/` directory yet → say so. It is created on the first session end
|
|
with the hooks installed; nothing is wrong.
|
|
- User asks to lower a promotion threshold so something passes → refuse. Gates
|
|
are changed in the open, in `DESIGN.md`, not per-claim. Offer to record the
|
|
case as evidence the threshold is wrong.
|
|
- User asks to design or price a memory system generally → route to
|
|
`engineering/memory-engineering`. This skill *is* a memory system; that one
|
|
audits any of them, this one included.
|