kodex-fix-missing

Generates missing dictionary topics and scaffolds them for review.

Updated Jan 12, 2026
One-click install
npx skills add https://github.com/ben-mad-jlp/claude-mermaid-collab --skill kodex-fix-missing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kodex-fix-missing
Source: https://github.com/ben-mad-jlp/claude-mermaid-collab/tree/main/skills/kodex-fix-missing
Command: npx skills add https://github.com/ben-mad-jlp/claude-mermaid-collab --skill kodex-fix-missing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Kodex lacks a streamlined method to generate missing topic documentation; this Skill automates researching, scaffolding, and creating new Kodex topics to fill gaps in the knowledge base.

Core Features & Use Cases

  • Automated topic discovery: Scans the codebase to identify missing Kodex topics based on flags and gaps.
  • Topic scaffolding: Generates the four sections (conceptual, technical, files, related) in a ready-to-publish Kodex topic draft.
  • Topic creation: Uses the Kodex creation API to publish drafts and presents them for user validation.

Quick Start

Invoke kodex-fix-missing when a topic is flagged as missing; the skill will generate a draft with placeholders and request your confirmation to publish.

Frequently Asked Questions about kodex-fix-missing

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

FAQPage Schema
How do I automatically create missing documentation topics from codebase gaps?

You can automatically create missing documentation topics by scanning the codebase to identify gaps and scaffolding complete topic drafts. This process researches the repository, defines topic scope, and generates conceptual, technical, files, and related sections for review.

What is the best way to scaffold new knowledge base topics for review?

Scaffolding new knowledge base topics involves generating the four required sections—conceptual, technical, files, and related—in a ready-to-publish draft format. The system uses built-in tooling to research the codebase and create drafts, requiring only topic naming and user validation to publish.

How does automated topic discovery work for undocumented code?

Automated topic discovery works by scanning the repository to identify missing areas based on flags and knowledge gaps. It targets undocumented code sections to define the topic scope and prepare the content structure needed for a complete knowledge base entry.

Do I need to manually publish drafts created from missing topic gaps?

No, you do not need to manually publish the drafts. The system uses the creation API to publish drafts automatically, but it presents them for your validation and confirmation before finalizing the topic content in the knowledge base.

What sections are included when auto-generating missing topic documentation?

Auto-generating missing topic documentation includes four main sections: conceptual, technical, files, and related. These sections are scaffolded with researched content and placeholders to provide a complete, ready-to-review topic draft.

Can I use codebase research to define the scope of a new documentation topic?

Yes, you can use codebase research to define the scope of a new documentation topic. The system scans the repository to understand the context and automatically determines the boundaries and necessary content for the missing topic.