corpus-fileback

name: corpus-fileback description: 用于显式配置目标 corpus 后，在用户明确确认时把可复用结论、决策、综合判断或选定候选写回该 LoreKit corpus 的知识库。

Optional fileback gateway for a configured Lorekit corpus. It writes only confirmed long-term knowledge, using target corpus rules.

If the current working directory is already the intended corpus, prefer its local wiki-fileback route directly. Use this skill when the request starts outside the target corpus and needs configured cross-project routing.

Confirmation Gate

Only write to 知识库/ when the user explicitly says one of:

"确认写入知识库"
"确认第 1、3 条 fileback"
"把这个沉淀到知识库"
"写回 corpus"
"注入知识库"

Notifications, candidate lists, or Feishu/Lark messages are reminders only. They are not confirmation unless the user copies the confirmation back into this Codex conversation.

Config

Read ~/.config/lorekit/global-corpus.json.

Required:

default_corpus
lorekit_bin or <default_corpus>/bin/lorekit
knowledge_dir (default 知识库)

Use the configured corpus-local wrapper for writes.

Before Writing

Read:

<default_corpus>/AGENTS.md
<default_corpus>/CLAUDE.md
<default_corpus>/系统/filing-rules.md
<default_corpus>/系统/frontmatter-spec.md
<default_corpus>/index.md
<default_corpus>/skills/wiki-fileback/SKILL.md when present

What To Write

Write reusable conclusions, decisions, and stable synthesis.

Do not write:

ordinary todo items
one-off emotions
temporary complaints
unverified guesses
private content unless explicitly approved
full diary prose

When fileback comes from wiki-daily candidates, preserve backlinks to the source daily page and candidate report.

Action

Identify exactly which candidate or conclusion the user confirmed.
Resolve the subject using corpus filing rules.
Search existing pages with <lorekit_bin> search "<subject>".
Append to existing pages or create new pages according to local rules.
Preserve source backlinks.
Run the local verification required by wiki-fileback, usually <lorekit_bin> sync and <lorekit_bin> lint --quick.
Report changed paths and verification.

Safety

Do not auto-fileback from automation.

Do not let GBrain write canonical pages.

If confirmation is ambiguous, ask which candidate numbers or conclusion should be written.