Agent skill · data analytics · wshobson
scan
Scans the codebase to generate project-doc.md and AGENTS.md. Use when bootstrapping a new agent-driven repo, refreshing project documentation after architectural changes, or running a delta scan to detect drift. Runs a full scan on first use and a smart delta scan on subsequent runs. Uses understand-anything + context-mode when available, falls back to native tools otherwise. Only updates AGENTS.md on detected architectural changes with human confirmation.
Why this skill is useful
Adds a comprehensive scanning tool that generates project-specific documentation, enhancing the AI's ability to understand codebases and their architecture.
What it needs
Requires context-mode, understand-anything installed locally. About 5k tokens when loaded. Last updated 2026-08-05. 38,570 stars on the source repository.
What this skill does
Codebase Scanner You are a technical analyst. Your job is to scan the project codebase and produce accurate, project-specific documentation used by all downstream agents. Step 1: Check Optional Plugin Dependencies Check whether the two optional enhancement plugins are available: These plugins are optional. They improve scan quality but are not required: understand-anything (Lum1104/Understand-Anything) — provides deeper semantic code analysis context-mode (mksglu/context-mode) — routes large outputs through a sandbox to protect the context window If both are present, use them in Steps 3–4 as described below. If either or both are missing, proceed with the native fallback approach: use find, grep, cat, and git commands directly, routing large outputs through ctxexecute / ctxexecutefile if context-mode is available, otherwise summarise inline. Note: To install the optional plugins manually: Step 2: Determine Scan Mode Check if .claude/pipeline/project-doc.md exists. Does not exist → FULL SCAN (first run) Exists → DELTA SCAN Step 3A: Full Scan Use understand-anything to analyse the entire codebase. If context-mode is available (verified in Step 1), route ALL output through its tools (ctxbatchexecute / ctxexecutefile) — never dump raw file contents into the main context window. If context-mode is not available, summarise each file's findings inline and avoid printing raw file contents. Produce .claude/pipeline/project-doc.md using the following structure (based on the architecture-blueprint-generator pattern): After writing project-doc.md, proceed to Step 4 to generate AGENTS.md. Step 3B: Delta Scan 1. Run git diff HEAD~1 --name-only to get changed files 2. If no changed files, report "No changes detected — project-doc.md is current" and exit 3. Use understand-anything to re-analyse only the changed files; route output through ctxexecutefile if context-mode is available, otherwise summarise inline 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills wshobson/scan