agent-memorylisted
Install: claude install-skill hudrazine/velkross
# Agent Memory
A persistent memory space for storing knowledge that survives across conversations.
## Memory Root
Store memories in `<repository root>/.memories/`.
- If `.memories/` does not exist, treat it as empty.
- Create `.memories/` only when saving a memory.
- Memory files are project-local and intentionally gitignored.
## Workflow
1. Check relevant memories before related work, especially when investigating a familiar area or resuming interrupted work.
2. Save durable project context after useful discoveries, non-obvious fixes, architectural decisions, gotchas, or handoff-worthy in-progress work.
3. Maintain existing memories when facts change, work completes, or scattered notes should be consolidated.
## Find Memories
Use a summary-first approach. The `summary` frontmatter is the decision point for whether to read the full memory.
If `rg` is available, include `--no-ignore --hidden` when searching `.memories/`, because memory files are normally gitignored.
```bash
rg --no-ignore --hidden "^summary:" .memories/
rg --no-ignore --hidden -i "^summary:.*keyword" .memories/
rg --no-ignore --hidden -i "^tags:.*keyword" .memories/
rg --no-ignore --hidden -i "keyword" .memories/
```
Read the relevant files after the summary or tag search identifies likely matches.
## Write Memories
Before saving a new memory, search existing summaries to avoid duplicates. Update or consolidate an existing memory when it already covers the same topic.
Use category folders when th