wiki-quick-chat-capture

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Wiki Quick Chat Capture

Wiki快速对话捕获

Extract reusable technical findings from the current conversation and stage them in

_raw/

for later promotion. The goal is zero-friction capture of discoveries that would otherwise be lost when the session ends.

Speed contract: Inline only. No subagents. No QMD. No manifest writes. Target: <60 seconds.

从当前对话中提取可复用的技术发现，并将其暂存到

_raw/

目录中，以便后续升级。目标是无摩擦地捕获那些若不保存就会在会话结束后丢失的发现。

**速度约定：**仅在线运行。无需子Agent。无需QMD。无需写入清单。目标耗时：<60秒。

When to Use This Skill

何时使用此技能

Right tool when:

The user just hit a non-obvious bug or confirmed a framework gotcha mid-session
There's a concrete finding worth keeping but a full
```
/wiki-ingest
```
run would be too disruptive
The user wants to offload the knowledge now and defer promotion to end-of-day

NOT a replacement for

wiki-capture

(promotes directly to a final wiki page) or

wiki-ingest

(full document ingestion with cross-links and manifest tracking).

适用场景：

用户在会话中途遇到了非显而易见的bug，或确认了某个框架的gotcha
存在值得保留的具体发现，但完整运行
```
/wiki-ingest
```
会过于干扰当前会话
用户希望立即留存知识，将升级操作推迟到当日结束时

不能替代

wiki-capture

（直接升级为最终wiki页面）或

wiki-ingest

（带交叉链接和清单跟踪的完整文档导入）。

Before You Start

开始前准备

Resolve config — follow the Config Resolution Protocol in
```
llm-wiki/SKILL.md
```
(walk up CWD for
```
.env
```
→
```
~/.obsidian-wiki/config
```
→ prompt setup). Extract:
- ```
OBSIDIAN_VAULT_PATH
```
- ```
OBSIDIAN_RAW_DIR
```
  (default:
```
$OBSIDIAN_VAULT_PATH/_raw
```
  )
Ensure
```
$OBSIDIAN_RAW_DIR
```
exists. If not, create it.

解析配置 — 遵循
```
llm-wiki/SKILL.md
```
中的配置解析协议（从当前工作目录向上查找
```
.env
```
→
```
~/.obsidian-wiki/config
```
→ 提示设置）。提取以下内容：
- ```
OBSIDIAN_VAULT_PATH
```
- ```
OBSIDIAN_RAW_DIR
```
  （默认值：
```
$OBSIDIAN_VAULT_PATH/_raw
```
  ）
确保
```
$OBSIDIAN_RAW_DIR
```
目录存在。若不存在则创建。

Step 1: Scan the Conversation for Findings

步骤1：扫描对话提取发现

Extract reusable technical knowledge — things worth having in 3 months with no memory of this session.

Capture:

Non-obvious bugs and their root causes
Framework or library gotchas (undocumented behavior, edge cases)
API behavior that surprised the user
Workarounds or fixes that required investigation
Environment/toolchain quirks
Patterns that emerged from debugging or testing

Skip:

Project management updates, roadmap changes, config already in CLAUDE.md
Exploratory back-and-forth where no conclusion was reached
Things obvious from the docs or boilerplate any developer finds on first read
Pleasantries, meta-conversation, status updates

If nothing material emerged, tell the user and stop.

提取可复用技术知识——那些即使3个月后忘记本次会话内容仍有价值的信息。

需捕获内容：

非显而易见的bug及其根本原因
框架或库的gotcha（未记录的行为、边缘情况）
令用户意外的API行为
需经调研得出的变通方案或修复方法
环境/工具链的特殊问题
调试或测试过程中发现的模式

需跳过内容：

项目管理更新、路线图变更、已在CLAUDE.md中记录的配置
未得出结论的探索性来回讨论
文档中已明确说明或任何开发者首次阅读样板代码就能发现的内容
寒暄语、元对话、状态更新

若未发现有价值的内容，告知用户并终止操作。

Step 2: Cluster by Topic

步骤2：按主题聚类

Group related findings — one raw file per topic cluster, not per individual finding.

Examples: "Swift 6 concurrency gotchas", "Next.js hydration edge cases", "Postgres advisory locks".

Name each cluster as a kebab-case slug:

swift-actor-reentrancy

nextjs-hydration-mismatch

将相关发现分组——每个主题集群对应一个raw文件，而非每个单独发现对应一个文件。

示例："Swift 6 concurrency gotchas", "Next.js hydration edge cases", "Postgres advisory locks"

每个集群命名为短横线分隔的小写格式（kebab-case）：

swift-actor-reentrancy

nextjs-hydration-mismatch

。

Step 3: Infer Project Context

步骤3：推断项目上下文

Check the conversation for clues — repo names, file paths, framework mentions, error messages. Use the most specific project name you can reliably infer. If unclear, use

null

检查对话中的线索——仓库名称、文件路径、框架提及、错误信息。使用你能可靠推断出的最具体的项目名称。若无法确定，使用

null

。

Step 4: Write Raw Files

步骤4：写入Raw文件

For each cluster, write

$OBSIDIAN_RAW_DIR/<ISO-date>-<slug>.md

Read

references/RAW-FORMAT.md

for the full frontmatter spec, body structure (finding block format), and the provenance/confidence calibration table.

Quick reference for frontmatter fields that vary per cluster:

```
title
```
— descriptive cluster title
```
tags
```
— 2–4 domain tags matching the vault taxonomy
```
summary
```
— 1–2 sentences, ≤200 chars
```
project
```
— inferred project name or
```
null
```
```
base_confidence
```
— 0.6 (discussed, unconfirmed) → 0.75 (fix applied) → 0.9 (test confirmed)
```
provenance.extracted
```
/
```
provenance.inferred
```
— must sum to 1.0
```
lifecycle_changed
```
— today's ISO date

sources

—

"<project> session (<YYYY-MM-DD>)"

为每个集群写入文件

$OBSIDIAN_RAW_DIR/<ISO-date>-<slug>.md

。

阅读

references/RAW-FORMAT.md

以获取完整的前置元数据规范、正文结构（发现块格式）以及来源/置信度校准表。

各集群不同的前置元数据字段速查：

```
title
```
— 描述性集群标题
```
tags
```
— 2–4个与vault分类匹配的领域标签
```
summary
```
— 1-2句话，≤200字符
```
project
```
— 推断出的项目名称或
```
null
```
```
base_confidence
```
— 0.6（已讨论，未确认）→ 0.75（已应用修复）→ 0.9（已测试确认）
```
provenance.extracted
```
/
```
provenance.inferred
```
— 两者之和必须为1.0
```
lifecycle_changed
```
— 今日的ISO格式日期

sources

—

"<project> session (<YYYY-MM-DD>)"

Step 5: Confirm to User

步骤5：向用户确认

Staged to _raw/:
  _raw/2026-05-27-swift-actor-reentrancy.md   — "Actor reentrancy causes deadlock in async forEach"
  _raw/2026-05-27-xcode-derived-data-cache.md — "Stale derived data silently breaks incremental builds"

Run /wiki-ingest (or /data-ingest) to promote these to full wiki pages.

If nothing was captured: "Nothing worth capturing found in this session."

Staged to _raw/:
  _raw/2026-05-27-swift-actor-reentrancy.md   — "Actor reentrancy causes deadlock in async forEach"
  _raw/2026-05-27-xcode-derived-data-cache.md — "Stale derived data silently breaks incremental builds"

Run /wiki-ingest (or /data-ingest) to promote these to full wiki pages.

若未捕获到任何内容："本次会话未发现值得捕获的内容。"

What This Skill Does NOT Do

此技能不包含的操作

No manifest writes —
```
_raw/
```
files are not tracked in
```
.manifest.json
```
No
```
index.md
```
,
```
log.md
```
, or
```
hot.md
```
updates — those happen during promotion
No QMD refresh — raw files are drafts, not indexed content
No subagents — everything runs inline in this context window

These constraints are intentional. Speed is the point. Promotion via

/wiki-ingest

handles all of the above when the user is ready.

不写入清单——
```
_raw/
```
文件不会在
```
.manifest.json
```
中被跟踪
不更新
```
index.md
```
、
```
log.md
```
或
```
hot.md
```
——这些操作会在升级过程中执行
不刷新QMD——raw文件是草稿，不属于已索引内容
无需子Agent——所有操作均在当前上下文窗口中在线运行

这些限制是有意设置的。速度是核心目标。当用户准备就绪时，通过

/wiki-ingest

进行升级会处理上述所有操作。