doc-db-guide — community 0313temp, community, ide skills

v1.0.0

Sobre este Skill

Perfeito para Agentes de Desenvolvedor que necessitam de gerenciamento eficiente de documentação de projeto por meio de indexação e consulta do SQLite. Guide for the Doc Database VSCode extension. Use when the user asks to modify, extend, debug, or understand the doc-db extension, add new commands or features, change the webview UI, update the database schema, or fix extension bugs. Also use when asked about doc-db, doc database, or doc plugin development.

Albatross679 Albatross679
[0]
[0]
Updated: 3/16/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution
Review Score
7/11
Quality Score
45
Canonical Locale
en
Detected Body Locale
en

Perfeito para Agentes de Desenvolvedor que necessitam de gerenciamento eficiente de documentação de projeto por meio de indexação e consulta do SQLite. Guide for the Doc Database VSCode extension. Use when the user asks to modify, extend, debug, or understand the doc-db extension, add new commands or features, change the webview UI, update the database schema, or fix extension bugs. Also use when asked about doc-db, doc database, or doc plugin development.

Por que usar essa habilidade

Habilita os agentes a gerenciar grandes projetos com vários arquivos de documentação, indexando frontmatter no SQLite, permitindo consulta eficiente, edição e validação usando geração de DDL do SQL e operações CRUD.

Melhor para

Perfeito para Agentes de Desenvolvedor que necessitam de gerenciamento eficiente de documentação de projeto por meio de indexação e consulta do SQLite.

Casos de Uso Práticos for doc-db-guide

Indexação de frontmatter para consulta eficiente
Edição de arquivos de documentação com validação
Sincronização da documentação do projeto entre arquivos

! Segurança e Limitações

  • Requer instalação da extensão do VSCode
  • Dependência do banco de dados SQLite
  • Limitado à indexação de frontmatter

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.
  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is doc-db-guide?

Perfeito para Agentes de Desenvolvedor que necessitam de gerenciamento eficiente de documentação de projeto por meio de indexação e consulta do SQLite. Guide for the Doc Database VSCode extension. Use when the user asks to modify, extend, debug, or understand the doc-db extension, add new commands or features, change the webview UI, update the database schema, or fix extension bugs. Also use when asked about doc-db, doc database, or doc plugin development.

How do I install doc-db-guide?

Run the command: npx killer-skills add Albatross679/0313temp. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for doc-db-guide?

Key use cases include: Indexação de frontmatter para consulta eficiente, Edição de arquivos de documentação com validação, Sincronização da documentação do projeto entre arquivos.

Which IDEs are compatible with doc-db-guide?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for doc-db-guide?

Requer instalação da extensão do VSCode. Dependência do banco de dados SQLite. Limitado à indexação de frontmatter.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add Albatross679/0313temp. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use doc-db-guide immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

doc-db-guide

Install doc-db-guide, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Doc Database - Agent Guide

VSCode extension that indexes project documentation frontmatter into SQLite for querying, editing, and validation.

Source Layout

doc-db/src/
├── extension.ts   - Command registration, message handlers, file watcher
├── schema.ts      - Hardcoded table definitions, SQL DDL generation, frontmatter templates
├── database.ts    - DocDatabase class (sql.js wrapper, CRUD, junction table ops)
├── sync.ts        - SyncEngine (full sync, single file sync, file watching)
├── webview.ts     - HTML renderers (renderTable, renderEditableTable, renderDashboard)
├── parser.ts      - Frontmatter parsing and value extraction
├── types.ts       - TypeScript interfaces (TableDef, FieldDef, etc.)
└── sql.js.d.ts    - Type declarations for sql.js

Key Design

Doc-db uses hardcoded table definitions in schema.ts (getTableDefs()) instead of reading fileClass files. Table type is resolved by:

  1. Frontmatter type field
  2. Frontmatter fileClass field (legacy)
  3. Directory path inference via dirToTableType() (logs/log, etc.)

Commands

CommandIDDescription
Rebuild Databasedoc-db.rebuildDatabaseDrop + recreate all tables, full sync
Run Querydoc-db.runQuerySQL input box, results in editable webview
Validation Errorsdoc-db.showValidationErrorsShow type mismatches from indexing
New Entrydoc-db.newEntryPick table type, create file with frontmatter template
Dashboarddoc-db.showDashboardOverview of all tables with counts and recent files

Architecture

Schema (schema.ts)

Tables are defined in getTableDefs(). Each table has:

  • Main table: {tableName} with _file_path TEXT PRIMARY KEY + scalar columns
  • Junction tables: {tableName}_{fieldName} for Multi fields with (file_path, value) composite PK

Common fields on all tables: id, name, description, created, updated Common junction tables: {table}_tags, {table}_aliases

Field type mapping:

  • Input → TEXT
  • Select → TEXT with CHECK constraint
  • Number → REAL
  • Boolean → INTEGER CHECK(0,1)
  • Date → TEXT CHECK GLOB YYYY-MM-DD
  • Multi → junction table

Key functions: getTableDefs(), generateSchema(), generateDropStatements(), generateFrontmatterTemplate(td), getScalarFields(td), getJunctionFields(td), dirToTableType(relDir)

Database (database.ts)

DocDatabase wraps sql.js (in-memory SQLite compiled to WASM).

  • open() loads from disk, save() writes back, close() saves + closes
  • upsertFile() deletes then re-inserts (cascades to junction tables)
  • updateField() validates against allowed columns before UPDATE
  • addJunctionValue() / removeJunctionValue() for multi-field edits
  • query(sql) accepts SELECT/PRAGMA/EXPLAIN (read-only) or write ops
  • getTableType(filePath) returns which table a file belongs to

Sync Engine (sync.ts)

  • fullSync() walks each table folder, indexes .md files into matching tables
  • syncSingleFile() indexes one file (parse frontmatter, resolve table type, upsert, log errors)
  • resolveTableType(data, relPath) determines table by frontmatter type/fileClass or directory
  • File watchers auto-sync on create/change/delete within each table folder (logs/**/*.md, experiments/**/*.md, etc.)
  • Periodic save every 30 seconds if dirty

Webview (webview.ts)

Three renderers:

  1. renderTable() - Read-only HTML table (validation errors)
  2. renderEditableTable() - Full editing: contenteditable cells, chip UI for multi fields, file path links, CSV export
  3. renderDashboard() - Card grid showing table counts and recent files

All edits flow: webview postMessage → extension handler → updateField()/addJunctionValue()/removeJunctionValue()db.save() → update markdown file on disk

Frontmatter Editing (in extension.ts)

  • Scalar fields: regex ^(fieldName:\s*).*$ replacement
  • YAML quoting: auto-quotes values containing ,:[]{} etc.
  • Array add: addYamlArrayItem() finds field, inserts - value after last item
  • Array remove: removeYamlArrayItem() finds and splices matching - value line

Configuration

SettingDefaultDescription
doc-db.databasePath.doc-db/doc-db.sqliteDatabase file location
doc-db.autoWatchtrueAuto-watch for file changes

Build & Install

bash
1cd <project-root>/doc-db 2npx tsc -p ./ # TypeScript → out/ 3npx @vscode/vsce package --allow-missing-repository # → doc-db-0.1.0.vsix 4code --install-extension doc-db-0.1.0.vsix --force # Install

After install, reload VSCode window to activate.

IMPORTANT: After modifying source code, you MUST run all three steps (compile, package, install) for changes to take effect.

Adding a New Table

  1. Add a new entry to the array in getTableDefs() in schema.ts with name, folder, and fields
  2. Add the folder→type mapping in dirToTableType() in schema.ts
  3. Recompile, repackage, reinstall
  4. Run Doc DB: Rebuild Database
  5. Update references/schema.md in the doc-db-query skill

Adding a New Command

  1. Add to contributes.commands in package.json
  2. Register handler in extension.ts activate() with vscode.commands.registerCommand()
  3. Use ensureInitialized() to get db and syncEngine
  4. For webview output: use renderTable() (read-only) or renderEditableTable() (editable)
  5. For editable webviews: add message handlers in panel.webview.onDidReceiveMessage()

Common Patterns

Query with junction tables (use correlated subqueries)

sql
1SELECT l._file_path, l.name, l.created, 2 (SELECT GROUP_CONCAT(value, ' | ') FROM log_tags WHERE file_path = l._file_path) AS tags 3FROM log l 4ORDER BY l.created DESC

Opening files from webview

typescript
1vscode.postMessage({ type: 'openFile', filePath: link.dataset.file }); 2// In extension: opens via vscode.workspace.openTextDocument()

Habilidades Relacionadas

Looking for an alternative to doc-db-guide or another community skill for your workflow? Explore these related open-source skills.

Ver tudo

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

widget-generator

Logo of f
f

Gerar plugins de widgets personalizáveis para o sistema de feed do prompts.chat

flags

Logo of vercel
vercel

O Framework React

138.4k
0
Navegador

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

98.6k
0
Desenvolvedor