scan

Parse source paths and generate or update CAIDE wiki pages for modules, dependencies, and components.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/ImLp/claude-caide --skill scan-imlp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scan
Source: https://github.com/ImLp/claude-caide/tree/main/.claude/skills/scan
Command: npx skills add https://github.com/ImLp/claude-caide --skill scan-imlp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the synchronization of wiki pages with the actual source code by scanning a given path and updating module, dependency, and component entries. It reduces manual maintenance and ensures architectural knowledge stays current.

Core Features & Use Cases

  • Generates or updates wiki pages for modules, dependencies, and components by inspecting the codebase.
  • Detects changes, additions, and removals to keep wiki in sync after code changes.
  • Useful for onboarding, architectural queries, and impact analysis across large repos.

Quick Start

Run a scan on your codebase to refresh the wiki from the root src directory.

Frequently Asked Questions about scan

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

FAQPage Schema
How do I keep wiki documentation in sync with my codebase automatically?

To keep wiki documentation in sync with your codebase, this Skill scans a source path and generates or updates module, dependency, and component entries. It detects structural changes to ensure architectural knowledge stays current without manual maintenance.

Can I generate wiki pages for a specific subdirectory instead of the full codebase?

Yes, you can generate wiki pages for a subdirectory. The scan supports applying to full codebases or specific source paths like src/rendering/, updating only the module and dependency pages found within that targeted scope.

How does change detection work when updating wiki pages for code modules?

Change detection for wiki pages works by parsing the source path and comparing current modules, dependencies, and components against existing entries. It logs additions, updates, and removals, applying deterministic page creation with frontmatter scaffolding to stay synchronized.

What is the best way to document codebase dependencies and components for onboarding?

The best way to document codebase dependencies for onboarding is running an automated scan. It inspects modules and components to generate or update wiki pages, providing current architectural knowledge and impact analysis across large repositories.

Does generating module pages require any external dependencies or components?

No, generating module pages requires no external dependencies or components. The scan runs independently to inspect the source path and output synchronized CAIDE wiki pages with frontmatter scaffolding directly from the parsed codebase.