setup-memory ยท diff
git:20261108.36c5a0f to git:20261108.f56f165
2 added, 2 removed. Audit A to A.
What this update changes in the checks
No check changed: every fixed check gives the same answer before and after this update.
A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.
---
name: setup-memory
description: Set up the shared project memory (docs/memory) in this repository and fill it from the code
argument-hint: "[notes about the project]"
disable-model-invocation: true
---
- Use the team-workflow skill to set up the project memory of this repository.
+ Use the team skill to set up the project memory of this repository.
1. If `docs/memory/INDEX.md` already exists, say so, run memcheck and stop.
- 2. Run `python3 <team-workflow skill folder>/scripts/init_memory.py --root <repository root>`.
+ 2. Run `python3 <team skill folder>/scripts/init_memory.py --root <repository root>`.
3. Fill the memory from the real code, facts only:
- `STATE.md`: version and the file that holds it, CI, known limits.
- `PLAYBOOKS.md`: run the detected commands to confirm them; add the release steps.
- `MAP.md`: every module or package in one line, grouped by area.
- One card per area in `areas/`, from `areas/_TEMPLATE.md`: key files, contracts, tests,
known traps.
- `ACCESS.md`: what each folder holds and what must never be touched.
In a large repository, split the reading of the areas between `doc-keeper` agents and
check what they write.
4. Run memcheck and fix what it reports.
5. Report what was created, which commands you confirmed and what the user should check.
Notes from the user: $ARGUMENTS