amp_write
Log coding-agent memory entries—gotchas, decisions, attempts, notes—to git-native JSONL, so future sessions keep context and teammates share it.
Instructions
AMP: log a new entry. Required: type + msg (one sentence). Optional: file, line, tags, detail. Call it without being asked when: the user is stuck ('!!', 'not working', 'same error', 'retry' → type attempt: what was tried and how it failed); the user asks you to remember something (save the fact in your own words); a decision is made (type decision: X over Y because Z); you learn something non-obvious (type gotcha, with file/line). These apply in any language the user writes in. Don't log what can be re-derived from the code. Use 'detail' for a rich multi-paragraph body (repro steps, code, full reasoning, or a session snapshot) — it's stored in a sidecar and loaded on demand, so it never bloats the always-on memory index.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"type": "<type>",
"msg": "<msg>"
},
"name": "amp_write"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| msg | Yes | ||
| file | No | ||
| line | No | ||
| tags | No | ||
| type | Yes | ||
| detail | No | Optional rich body (Tier-2). Stored in the consolidated details store; NOT injected into rule files. Put the long-form context here; keep 'msg' to one summary sentence. |