xiaoshuai
a64ea2acb3
A durable memory layer for OpenCode. Structure:
ROOT.md total plan: goals, hard rules, directory registry,
and a scenario -> file routing table
<category>/
index.md one line per file, COMPILED from frontmatter
<slug>.md the memory itself
Two roots, same shape: <config>/memory/ (global) and
<project canonical>/.memory/ (project). Project wins on conflict; global
hard rules stay resident everywhere.
Why a plugin rather than a skill that tells the model to read a folder:
model-driven retrieval is unreliable — the model forgets, reads half the
files, or reads the wrong ones. Markdown is the human-facing format; the
plugin is the engine that parses, scores, and injects.
Measured, not assumed: FTS5's two built-in tokenizers both fail on this
corpus. On SQLite 3.53.4 with "部署脚本用 pnpm 而不是 npm...": unicode61
emits 7 terms for the whole sentence and matches 0 hits for "部署";
trigram needs >= 3 characters and also returns 0 for that two-character
word. So tokenization happens in the plugin (CJK bigrams, latin words)
and no SQL index is used — a thousand memories are fine to scan.
index.md and ROOT's two tables are compiled, never hand-edited: a
hand-maintained index drifts, a generated one cannot. Hit counters live
in .state.json so cross-device sync does not conflict on every recall.
Tools are named recall/remember/forget/inspect rather than
write/read/status: generic names were observed shadowing the harness's
own built-in tools.
18 lines
795 B
Markdown
18 lines
795 B
Markdown
---
|
||
id: rules/plugin-push-on-change.md
|
||
kind: rule
|
||
summary: 改动这两个目录后立即 commit 并 push，不询问。
|
||
highlight: ~/.config/opencode 本身就是 git 仓库，.gitignore 只放行 skills/ 和 plugins/
|
||
created: 1791512032262
|
||
updated: 1791512246723
|
||
pinned: true
|
||
---
|
||
|
||
`~/.config/opencode` 自身是 git 仓库，`.gitignore` 只放行 `skills/` 和 `plugins/`（外加 .gitignore、pwsh.cmd、package.json）。
|
||
|
||
在这两个目录下创建、修改、删除任何文件后，**提交并推送后再回复用户**，不要问是否要 push。
|
||
|
||
推送用 SSH（origin 已是 SSH 地址）。HTTPS 推送会提示密码且无 TTY，必然失败。
|
||
|
||
推送失败就报错并停下，不要静默重试，也不要 `git reset`。提交信息要写清楚改了什么、为什么改。
|