Back to Skills

dbs-report

把多次 dbs-save 攒下来的诊断状态合并成一份可交付的 markdown 报告。 触发方式:/dbs-report、/出报告、「打包」「整理一份」「给合伙人看的」 Generate a deliverable diagnosis report by merging all dbs-save snapshots. Trigger: /dbs-report, "package this up", "make me a report"

6,305stars821forksUpdated 6/8/2026

Security Assessment

Safe(100/100)
Security Score100/100

About dbs-report

dbs-report is an AI skill for turning multiple saved business diagnosis states into one deliverable Markdown report. It solves the problem of valuable diagnosis conclusions being scattered across chat history by relying only on confirmed saved records created through dbs-save. Instead of summarizing from conversation memory, it reads stored Markdown snapshot files from the project’s session directory, merges them chronologically, removes duplicates, organizes the content, and produces a shareable report that can be archived or sent to partners, consultants, or stakeholders.

dbs-report supports generating reports for the current project, specifying a project with --slug, filtering saved records with --since YYYY-MM-DD, and combining both options. It validates whether enough saved records exist, sorts files by timestamp, parses frontmatter fields and six standard body sections, and writes a new Markdown report under the reports directory without overwriting previous outputs. The generated report includes complaint evolution, confirmed conclusions, rejected directions, unresolved issues, recommended next steps, and an appendix index of source files. It preserves traceability by tying report content back to saved files and avoids unsupported interpretation except for a brief evolution summary.

This skill is designed for users of dbskill who need a formal consulting-style artifact from accumulated diagnosis work. It is useful for business owners, consultants, founders, operators, or advisors who want to package confirmed diagnostic progress into a readable document for review, collaboration, or future reference. Its target use cases include preparing partner-facing summaries, reviewing multi-week diagnostic progress, comparing older and newer diagnosis versions, and creating a stable Markdown deliverable from previously saved diagnostic states.

FAQ

How do I generate a report with dbs-report?

Use /dbs-report to merge all saved records for the current project into a Markdown report. You can also use natural language triggers such as asking to package the work or make a report.

Can I generate a report for a specific project or date range?

Yes. The skill supports /dbs-report --slug <project name>, /dbs-report --since YYYY-MM-DD, and combining both options to target a project and filter saved records by date.

What files does dbs-report read?

It only reads standard Markdown saved records under ~/.dbs/sessions/{project name}/. Files placed outside that sessions directory are ignored.

What output format does dbs-report create?

It creates a Markdown report only. It does not proactively generate PDF, HTML, or other formats.

What happens if there are not enough saved records?

If there are no saved records, it tells the user to save diagnosis results first. If there is only one saved record, it explains that merging is not necessary and asks whether the user still wants to force report generation.

Install dbs-report

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill