dbs-report

Merge dbs-save snapshots into a consolidated Markdown diagnostic report.

Updated May 19, 2026
One-click install
npx skills add https://github.com/Mengbooo/BemoSkills --skill dbs-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dbs-report
Source: https://github.com/Mengbooo/BemoSkills/tree/main/skills/productivity/dbs-report
Command: npx skills add https://github.com/Mengbooo/BemoSkills --skill dbs-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill merges multiple dbs-save snapshots into a readable, shareable, and archival Markdown diagnosis report. It reads saved sessions from ~/.dbs/sessions/{project}/, merges them in chronological order, deduplicates, and compiles the insights into a structured deliverable suitable for partners and stakeholders.

Core Features & Use Cases

  • Consolidates multiple snapshots into a single Markdown report with dates and an index.
  • Deduplicates and organizes conclusions, rejected directions, hypotheses, and next steps based on stored fields in the archives.
  • Produces a report under ~/.dbs/reports/{project}/{YYYYMMDD-HHMMSS}-{project}.md for archival sharing and review.

Quick Start

Run /dbs-report to merge all snapshots for the current project into a Markdown report.

Frequently Asked Questions about dbs-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I consolidate multiple markdown session snapshots into a single diagnostic report?

To consolidate markdown session snapshots into a diagnostic report, you can merge multiple saved conversations chronologically, deduplicate the insights, and compile them into a structured Markdown file suitable for archival sharing.

What's the best way to merge diagnostic session archives into a shareable Markdown document?

Merging diagnostic session archives into a shareable Markdown document involves reading saved project files, sorting them by timestamp, and outputting a consolidated report with deduplicated conclusions, hypotheses, and next steps.

How does deduplication work when consolidating multiple saved diagnostic conversations?

Deduplication during consolidation works by reading stored fields in session archives, then organizing and removing duplicate conclusions, rejected directions, hypotheses, and next steps to produce a clean Markdown report.

Do I need existing session snapshots saved in a specific directory to generate a consolidation report?

Yes, you need existing session snapshots saved in the ~/.dbs/sessions/{project}/ directory. The report generation reads these saved conversations, sorts them by timestamp, and merges them into the final Markdown file.

Can I generate a chronological diagnostic report from scattered project conversation snapshots?

Yes, you can generate a chronological diagnostic report by reading scattered conversation snapshots from a project directory, sorting them by their timestamp, and merging them into a single Markdown document.

What limitations exist when merging multiple markdown snapshots into an archival report?

A limitation is that the report generation relies solely on snapshots stored under the ~/.dbs/sessions/{project}/ path, meaning any conversations not previously saved there cannot be included in the consolidated Markdown output.