dbs-report
Merges multiple dbs-save archives into a deliverable Markdown report. Use when the user requests summarizing diagnoses, compiling reports, or generating shareable materials.
1How It Works & Mechanism
A pure prompt-orchestrated "artifact generator": inputs are archived markdown files saved to disk by dbs-save, and the output is a newly timestamped report markdown file; the entire process only reads, merges, categorizes, and transfers data.
报告内容必须来自 `{存档根目录}/sessions/{项目名}/` 下的存档文件。
Shares the same archive root directory resolution rules with dbs-save/dbs-restore (default/project/custom modes in .dbs/config.json), and all three only read configurations without writing them.
`dbs-report` 只读取配置,不修改配置。
Credibility relies on "traceability" rather than "good summarization": the primary core principle forbids summarizing out of thin air from the conversation; every detail must point back to specific fields in specific archives.
**不从对话凭空总结**。报告内容必须能追溯到具体存档文件的具体字段。这是报告的可信度
Multiple runs never overwrite files, using timestamps to provide "diagnostic snapshot comparison" capabilities.
每次新生成一份,**永不覆盖**。文件名带时间戳,方便对比不同时点的诊断快照。
Does not arbitrate conflicting conclusions: lists both newer and older versions, placing the newer one first and annotating the older one as "(Amended by subsequent diagnosis)".
如果一条结论在后续存档里被推翻或修正,**两条都列出来**,新的在前,旧的在后并加 `(已被后续诊断修正)` 标注。
Deliberately avoids data masking: sensitive figures and customer names in archives appear as-is in the report, pushing sanitization responsibility back to the dbs-save stage.
存档文件里有用户标的「敏感信息」(比如真实收入、客户名字)→ 报告原样保留。不做脱敏。
Strict minimum data threshold: rejects 0 archives directly, advises against 1 archive and asks whether to force merge, and only enters merging with ≥2 archives (the same criteria apply after --since filtering).
0 个文件 → 「`{项目名}` 下还没有可汇总的存档。
Integration with dbs-wechat-html is conditional: only prompts once if the user genuinely needs to publish, remaining unprompted otherwise.
想发公众号或群里,可以用 `/dbs-wechat-html` 把这份 markdown 转成微信后台粘贴版。
2Core Capabilities
4Recommended Governance & Evidence
- 环境变量 / API Key: Read vendor service credentials: Reads .dbs/config.json to resolve the archive root directory (mode=default/project/custom + root) — this is the user's own configuration
- 本地工作目录: File read/write and artifact output: {archive_root}/reports/{project_slug}/{YYYYMMDD-HHMMSS}-{project_slug}.md (new reports, never overwritten; executes mkdir -p if the directory does not exist)
5Second-Pass Verification
- [ok] 外部资源/工具:是否存在未声明的依赖或格式转换器 — 无 URL、无包、无 CLI 调用;PDF/HTML 相关语句只有禁止性的(不主动出 PDF / HTML / 其他格式)。external_deps 空数组成立。
- [ok] 安全结论:写入面是否只有报告文件 — 全文写入只有 mkdir -p 与报告文件生成;明确不修改 .dbs/config.json(「只读取配置,不修改配置」),不删除任何存档,不改写原始 sessions 文件。
- [ok] 实现原理是否成立:报告能否真正做到「每条可追溯」 — 六段中五段规定逐条携带来源(「· 出自 {对应存档的标题} · {对应日期}」)、附录给出文件名索引表,「结论冲突两条都列」避免丢失信息。机制可核查。
- [ok] 功能声明 vs 实际能力是否存在夸大 — description 只说「合并成可交付的 Markdown 报告」,未承诺分析深度或结论质量;SKILL.md 亦把「总结」限制到一段。一致。
- [unlocatable] 证据定位:仓库级元数据(stars/last_push)与 installs — stars=10121、last_push=2026-09-07 来自站点池 data/pool.json(GitHub API 采集),pin 本地副本无法逐字定位;installs 未采集记 null。license 可在仓库根 LICENSE 逐字命中。
6Verdict & Scenarios
1daf478be83e49ea…