opencode-reconstituter

Index OpenCode sessions into a Chroma store and generate reconstruction notes.

6|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/open-hax/opencode-skills --skill opencode-reconstituter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opencode-reconstituter
Source: https://github.com/open-hax/opencode-skills/tree/main/.opencode/skills/opencode-reconstituter
Command: npx skills add https://github.com/open-hax/opencode-skills --skill opencode-reconstituter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reconstitutes project context by indexing OpenCode sessions, enabling fast retrieval of relevant context and generation of reconstruction notes for a target path.

Core Features & Use Cases

  • Index OpenCode sessions into a searchable store (Chroma) to build context.
  • Query and assemble relevant context for a project reconstruction.
  • Produce markdown reconstruction notes under .reconstitute/output for sharing and archival use.

Quick Start

Run the reconstitute workflow to index sessions, search context, and generate reconstruction notes for a target path.

Frequently Asked Questions about opencode-reconstituter

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

FAQPage Schema
How do I reconstruct project context from previous OpenCode sessions?

You can search indexed OpenCode sessions by applying the reconstitute workflow, which queries the Chroma embedding store. This process retrieves relevant historical context and assembles it into structured markdown reconstruction notes for your target path.

What is needed to index and search OpenCode sessions for context reconstruction?

Context reconstruction notes are saved as markdown files within the .reconstitute/output directory. This format allows developers to easily share, review, and archive the retrieved project context generated from the indexed OpenCode sessions.

Can I retrieve specific context from old OpenCode sessions using Chroma?

Context reconstruction is best used when you need to rebuild project context from prior OpenCode sessions. It allows you to query a Chroma embedding store for relevant historical data and generate markdown reconstruction notes for sharing and archival use.

Does context reconstruction with OpenCode require a specific embedding store?

The main limitation is the dependency on OpenCode, a Chroma embedding store, and the reconstitute tooling. Without these components properly configured, the tool cannot index sessions, search context, or generate the .reconstitute/output artifacts.

How do I generate reconstruction notes for a specific target path in OpenCode?

After indexing OpenCode sessions into Chroma, the next step is to query the store to assemble relevant context. This retrieved context is then used to generate markdown reconstruction notes under .reconstitute/output for sharing and archival.

When should I rebuild project context using session indexing?

The reconstitute workflow differs from manual context recovery by automating the indexing of OpenCode sessions into a Chroma embedding store. This enables fast, retrievable context search and produces structured markdown reconstruction notes under .reconstitute/output.