一键导入
audit
Use when EC memories need cleanup — deduping, pruning stale entries, hygiene — or the user says "audit memories", "clean up EC", or "review what's stored"
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when EC memories need cleanup — deduping, pruning stale entries, hygiene — or the user says "audit memories", "clean up EC", or "review what's stored"
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when changing cogitation project settings (test/build/lint commands, branching conventions, graphify/codex toggles), or the user says "change config", "update settings", or "set test command"
Use when setting up a project for cogitation for the first time, or the user says "set up cogitation", "init", or "configure this project"
Use at the start of any conversation — establishes the cogitation workflow and requires invoking the right skill before responding, including before clarifying questions
Use for MEDIUM-sized work — new but contained behavior (one component, no architecture/data/API change) that deserves rigor without the design-doc + plan-doc ceremony of brainstorming
Use when the user wants to tailor the cogitation workflow — says "customise", "recustomise", "change the workflow", "make TDD less strict", "turn off finishing-branch", or wants a skill looser or disabled
Use before any feature work or new feature — interviews you about the feature one question at a time, pushes back on gaps, and saves a design doc with a decisions log
| name | audit |
| description | Use when EC memories need cleanup — deduping, pruning stale entries, hygiene — or the user says "audit memories", "clean up EC", or "review what's stored" |
Review, clean, and organize stored memories.
Announce: "I'm using the audit skill to review EC memories."
List All → Analyze → Present → Clean → Verify
Pull everything by type:
ec_list:
limit: 100
type: decision
ec_list:
limit: 100
type: learning
ec_list:
limit: 100
type: pattern
ec_list:
limit: 100
type: config
Also check for invalidated entries:
ec_list:
limit: 50
include_invalid: true
Organize memories by their area tag to see coverage:
## EC Memory Audit
**Total Memories:** N (D decisions, L learnings, P patterns, C config)
**Invalidated:** N
### By Area
| Area | Decisions | Learnings | Patterns |
|------|-----------|-----------|----------|
| auth | 3 | 2 | 1 |
| api | 1 | 4 | 2 |
| ... | ... | ... | ... |
### Issues Found
- **Duplicates (N):** [list IDs]
- **Potentially stale (N):** [list with reason]
- **Vague entries (N):** [list IDs]
Use AskUserQuestion for each category:
{
"questions": [{
"question": "How should I handle the N duplicate memories?",
"header": "Duplicates",
"options": [
{ "label": "Merge", "description": "Keep best version, invalidate others" },
{ "label": "Keep all", "description": "They might have nuance" },
{ "label": "Review each", "description": "Show me one by one" }
],
"multiSelect": false
}]
}
When removing a memory, use ec_invalidate with optional superseding:
ec_invalidate:
id: <old_memory_id>
superseded_by: <new_memory_id> # Optional: link to replacement
ec_addec_invalidate, pointing to new IDAfter cleanup, show the delta:
## Cleanup Complete
**Before:** N memories
**After:** M memories
**Invalidated:** X entries
### Changes
- Merged N duplicates
- Invalidated M stale entries
- Recategorized P entries
| Check | Action |
|---|---|
| Duplicate content | Merge or invalidate |
| References deleted code | Invalidate |
| Too vague to act on | Rewrite or invalidate |
| Wrong type | Create new with correct type, invalidate old |
| Missing area tag | Update via new entry |
Stop and ask if: