context-save

Save conversation context, plans, and findings to a PostgreSQL database.

5|2|Updated Jan 16, 2012
One-click install
npx skills add https://github.com/asonas/dotfiles --skill context-save
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-save
Source: https://github.com/asonas/dotfiles/tree/main/.claude/skills/context-save
Command: npx skills add https://github.com/asonas/dotfiles --skill context-save

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill allows you to save important conversation details, plans, and investigation findings for later reference, preventing loss of context and improving continuity.

Core Features & Use Cases

  • Save Current Context: Capture key decisions, plans, and findings from your ongoing conversation.
  • Automatic Naming: Uses the current directory name if no specific name is provided.
  • Structured Saving: Organizes saved information with clear sections like Background, Key Findings, and Plan.
  • Use Case: While investigating a bug, you've gathered crucial information. Use /context-save bug-investigation to save these details so you can easily pick up where you left off later.

Quick Start

Use the context-save skill to save the current conversation's context using the name 'my-project-notes'.

Frequently Asked Questions about context-save

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

FAQPage Schema
How do I save conversation context and notes for later retrieval?

Save conversation context by summarizing key findings, decisions, and actionable items into a structured format. The context is automatically named from the current working directory or a user-provided name, storing plans and investigation results for later retrieval and continuity.

What's the best way to preserve bug investigation findings from a chat session?

Preserve bug investigation findings by saving the current conversation context with a specific name. This captures background information, key findings, and plans, preventing the loss of crucial details gathered during the session for future reference.

Can I automatically name saved conversation notes based on my project directory?

Automatically name saved conversation notes using the current working directory name. If no specific context name is provided, the system determines one automatically, linking the saved notes to the relevant repository name as metadata.

How are saved conversation notes structured for later retrieval?

Saved conversation notes are structured with clear sections like Background, Key Findings, and Plan. This organization ensures that decisions, investigation results, and actionable items are easily accessible when retrieving the context later.

Do I need a PostgreSQL database to store conversation context and second-brain notes?

A PostgreSQL database is required to store conversation context and second-brain notes. The system uses the `mcp__second-brain__store_memory` tool to save summarized information with specific tags and metadata, including the repository name as a source.

When should I save conversation context instead of continuing a single session?

Save conversation context when you have gathered crucial investigation results, plans, or decisions that span multiple sessions. This prevents context loss, improving continuity when picking up complex tasks or bug investigations at a later time.