dbs-restore

Restore the most recent diagnosis snapshot from local storage.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Retrieve the most recent diagnosis snapshot saved locally and present it so you can continue analysis without starting from scratch.

Core Features & Use Cases

  • Retrieve the latest stored diagnosis state for the current project.
  • Support multi-session workflows by resuming across conversations.
  • Integrate with dbs-save to ensure persistence and seamless continuation.

Quick Start

Load the latest diagnosis snapshot with /dbs-restore to continue from where you left off.

Frequently Asked Questions about dbs-restore

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

FAQPage Schema
How do I restore a diagnosis snapshot to continue analysis in a new session?

To restore a diagnosis snapshot, you can load the most recent locally saved state to continue analysis without starting over. It reads project frontmatter metadata to identify the latest snapshot and formats a concise status summary for resumption.

What is the best way to resume a multi-session workflow after closing a conversation?

Resuming a multi-session workflow involves retrieving the latest diagnosis snapshot from local storage. By reading the current project frontmatter, the system identifies the last saved state and presents a status summary to seamlessly continue cross-conversation.

Does restoring a project state require any specific dependencies or external components?

Restoring a project state requires no external dependencies or components. It operates entirely on local storage and reads project frontmatter metadata directly to locate and restore the most recent diagnosis snapshot.

Can I use cross-conversation continuation to pick up a diagnosis exactly where I left off?

Yes, cross-conversation continuation allows you to pick up a diagnosis exactly where you left off. It targets multi-session workflows by retrieving the locally stored snapshot and formatting a concise status summary for the current project.

Why does my diagnosis snapshot not restore correctly when starting a new session?

A diagnosis snapshot might not restore correctly if the local storage is empty or the project frontmatter metadata is missing. The restoration process relies on reading this frontmatter to identify the latest snapshot and format the status summary accurately.