mcpField
D
decodie-ask

decodie-ask

github.com/owenbushDevelopment1250 installsUpdated 10w ago
Repository

About decodie-ask

decodie-ask is a read-only skill for exploring learning entries in `.decodie/`. It locates an entry by ID, keywords, or the current-session default, then uses the entry, code references, and external documentation to answer questions.

Key features

  1. 01Load global and project rules
  2. 02Resolve entries by ID or keywords
  3. 03Load entries and related context
  4. 04Read data without modifying it

Use cases

  1. 01Ask follow-up questions about a learning entry
  2. 02Check an entry against its referenced source code

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/owenbush/decodie-skill --skill decodie-ask

After installing, type/decodie-askin Claude Code to confirm it loaded.

Details

From the project README

Decodie — Ask Mode

Help the user explore and deepen their understanding of existing learning entries in the .decodie/ directory.

This mode is read-only with respect to .decodie/ data.

Setup

Load rules. Check for ~/.decodie/rules/*.md (global) and .decodie/rules/*.md (project). Read all .md files found. Treat their content as additional instructions controlling documentation output — tone, language, verbosity, format, audience. Project rules override global rules on conflict. If no rules exist, proceed with defaults.

Entry Resolution

Resolve which entry the question targets using this priority:

  1. Explicit entry ID — If the question contains an entry ID (e.g., entry-1711540000-a1b2), load it directly.
  2. Keyword match — Search active entry titles and topics in index.json. Prefer exact substring matches in titles, then topic tag matches.
  3. Current session default — If no match, default to the most recently created entry in the current session.
  4. No match — If no entries exist or match, tell the user and suggest browsing index.json.

Context Loading

Once the target entry is identified, load:

  • Entry content — Full entry from the session file: explanation, code_snippet, alternatives_considered, key_concepts.
  • Live source code — For files listed in the entry's references array, read the referenced sections to provide current-state context.
  • External documentation — URLs from external_docs for reference.

Response Instructions

  • Identify the entry — Begin by naming the entry (title and ID).
  • Answer the specific question — Use entry content and live source code as primary context.
  • Go deeper — Don't repeat the entry. Explain underlying concepts, provide examples, clarify trade-offs.
  • Suggest enrichment — If the question reveals a gap in the entry, suggest re-analysis.
  • Stay conversational — Tone of a knowledgeable colleague at a whiteboard.

Important Notes

  • After answering, the interaction is complete. The user can ask again with another question.
  • This mode only reads existing data — it does not generate entries.

Comments

Markdown supported