Agent skill · Documentation

deep-codebase-wiki

MUST CHECK FIRST before DeepWiki or any external research. Local-first codebase documentation wikis. **Priority order for library/framework research**: 1. deep-codebase-wiki (THIS) - check local wikis FIRST 2. DeepWiki - only if no local wiki exists 3. librarian/explore agents - only as fallback **Auto-trigger when**: - Any GitHub repository mentioned (org/repo format) - "How does X work?" about libraries/frameworks - Architecture, implementation, or codebase questions - Before cloning or analyzing any repository - Debugging external dependencies **Workflow**: Run `search_wikis.sh --repo "o

majiayu000github.com/majiayu000GitHub ↗
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill deep-codebase-wiki-watzon-claude-code-2 --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 13 KB
Bundled scripts: none
Allowed tools: ReadWriteEditGlobGrepBashTaskLSPASTGrep
Path: skills/analysis/deep-codebase-wiki-watzon-claude-code-2/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Deep Codebase Wiki ## ⚡ PROACTIVE CHECK PROTOCOL (CRITICAL) **BEFORE** any repository research, exploration, or analysis: ```bash # ALWAYS run this first when a repository is mentioned bash scripts/search_wikis.sh --repo "owner/repo" ``` **If wiki exists** → Read it immediately, save hours of exploration **If wiki doesn't exist** → Offer to analyze and create comprehensive wiki **Common triggers requiring this check**: - User mentions any GitHub repo (e.g., "facebook/react", "vercel/next.js") - Questions like "How does X work?" about known libraries/frameworks - "Understand the architecture of..." - "Explain how [library] implements..." - Before launching multiple explore/librarian agents - When debugging external dependencies - Architecture or implementation questions **Why this matters**: A 2-hour comprehensive wiki beats 10 parallel agent searches that rediscover the same information every time. --- ## Overview This skill enables creation, reading, and updating of comprehensive codebase documentation wikis. It analyzes GitHub repositories to generate structured, searchable documentation similar to DeepWiki and Zread services, but running entirely locally with full customizatio

What's inside
Steps it walks through
  1. ⚡ PROACTIVE CHECK PROTOCOL (CRITICAL)
  2. Overview
  3. Quick Start
  4. Decision Flowchart
  5. Mode 1: Read Mode (Search Existing Wikis)
  6. Mode 2: Analyze Mode (Create New Wiki)
  7. Mode 3: Update Mode (Refresh Documentation)
  8. Analyze Mode (Create New Wiki)
  9. Step 1: Determine Repository and Scope
  10. Step 2: Check for Existing Wiki
  11. Step 3: Clone Repository
  12. Step 4: Perform Multi-Level Analysis
  13. Step 5: Generate Wiki Structure
  14. Step 6: Validate and Save
Ships with 1 file
  • metadata.json
Commands it runs
ALWAYS run this first when a repository is mentioned
bash scripts/search_wikis.sh --repo "owner/repo"
Check for wiki
If found, read relevant sections
if [[ -n "$WIKI_PATH" ]]; then
cat "$WIKI_PATH/overview.md"
cat "$WIKI_PATH/systems/reconciliation.md"
fi
bash scripts/update_check.sh "$WIKI_PATH"
bash scripts/clone_repo.sh "owner/repo" [--depth 1] [--branch main]
More from claude-skill-registry
All skills →
retention-analysisCohort analysis and retention optimization framework. Identifies retention drivers and churn…Otherpolars-dovmedSearch 2.4M+ scientific papers from PubMed Central Open Access. **When to use:** - Literature…DatabasesretroBrutally honest engineering retrospective. Analyzes git history for what actually happened — not…Data & Analyticsreview-paperComprehensive manuscript review covering argument structure, technical methodology, citation…Code Review & Qualitycost-analysisBreak down costs by category (fulfillment, payment, marketplace)Otherdescriptive-statisticsSummarizing and visualizing data through measures of center, spread, shape, and position. Covers…Data & Analytics
About this skill
What does the deep-codebase-wiki skill do?

MUST CHECK FIRST before DeepWiki or any external research. Local-first codebase documentation wikis. **Priority order for library/framework research**: 1. deep-codebase-wiki (THIS) - check local wikis FIRST 2. DeepWiki - only if no local wiki exists 3. librarian/explore agents - only as fallback **Auto-trigger when**: - Any GitHub repository mentioned (org/repo format) - "How does X work?" about libraries/frameworks - Architecture, implementation, or codebase questions - Before cloning or analyzing any repository - Debugging external dependencies **Workflow**: Run `search_wikis.sh --repo "o

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill deep-codebase-wiki-watzon-claude-code-2 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.