extract-glossary

Extract domain terms, repository maps, and Mermaid diagrams from codebases.

320|3|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/mizchi/skills --skill extract-glossary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extract-glossary
Source: https://github.com/mizchi/skills/tree/main/meta/extract-glossary
Command: npx skills add https://github.com/mizchi/skills --skill extract-glossary

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill extracts domain-specific terms, repository mappings, and lightweight Mermaid diagrams from a codebase to support onboarding and AI reference materials.

Core Features & Use Cases

  • Glossary extraction: domain terms, organization terms, and implementation-specific names with classifications.
  • Repository mapping: entry points, main directories, tech stack, data and API boundaries.
  • Mermaid diagrams: small, task-focused diagrams to illustrate repository structure and data flows.
  • Onboarding material: AI-safe knowledge base to minimize repeated questions during project ramp-up.

Quick Start

Generate a glossary, repository map, and lightweight diagrams for the specified repo to bootstrap onboarding materials.

Frequently Asked Questions about extract-glossary

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

FAQPage Schema
How do I extract a domain glossary from a codebase for onboarding?

Extracting domain glossaries from codebases involves identifying domain-specific terms, organizational vocabulary, and implementation names, then classifying them to build a structured, AI-safe knowledge base that minimizes repeated onboarding questions.

Can I generate architecture maps and Mermaid diagrams across multiple repositories?

Generating repository maps and Mermaid diagrams works across single repos, multiple repos, or GitHub organizations, detailing entry points, main directories, tech stacks, and data API boundaries to illustrate architecture.

What is the best way to create onboarding documentation from an existing codebase?

Creating onboarding documentation involves extracting domain terms, repository mappings, and lightweight Mermaid diagrams from source code, producing structured reference materials including definitions, architecture notes, and data flows.

Does this approach work for mapping API boundaries and tech stacks in a GitHub organization?

Mapping API boundaries and tech stacks applies to single repos, multiple repos, or GitHub organizations, producing structured repository maps that detail entry points, data flows, and technology stacks.

What are the limitations of using automated glossary extraction for project ramp-up?

Limitations of automated glossary extraction include producing only lightweight, task-focused Mermaid diagrams and architectural notes, serving to bootstrap onboarding and AI reference materials without replacing exhaustive manual documentation.