Doc scanner

Skill bg-szy/TOP-SKILLS/skills/marketplace/doc-scanner

全球最大的 Claude Code 技能聚合库 · 收录 3900+ 来自 12+ 来源的技能，提供在线搜索与趋势分析看板 / The world's largest Claude Code skill aggregation hub — 3900+ skills from 12+ sources with online search and trend dashboard

Install

npx -y skills add bg-szy/TOP-SKILLS --skill doc-scanner

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Scans for project documentation files (AGENTS.md, CLAUDE.md, GEMINI.md, COPILOT.md, CURSOR.md, WARP.md, and 15+ other formats) and synthesizes guidance. Auto-activates when user asks to review, understand, or explore a codebase, when starting work in a new project, when asking about conventions or agents, or when documentation context would help. Can consolidate multiple platform docs into unified AGENTS.md.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.5 KB, as published. Nobody here has run it

Documentation Scanner

Scan for and synthesize project documentation.

When to Activate

User asks to review, understand, or explore a codebase
Starting work in a new/unfamiliar project
User asks about project conventions or workflows
Before making significant architectural decisions

Instructions

Step 1: Scan for Documentation

Use Glob to search project root:

AGENTS.md, CLAUDE.md, AI.md, ASSISTANT.md,
GEMINI.md, COPILOT.md, CHATGPT.md, CODEIUM.md,
CURSOR.md, WINDSURF.md, VSCODE.md, JETBRAINS.md,
WARP.md, FIG.md, DEVCONTAINER.md, GITPOD.md

Step 2: Read All Found Files

Read complete contents of every documentation file found.

Step 3: Synthesize

Combine information into unified summary:

PROJECT DOCUMENTATION

Sources: [list files found]

RECOMMENDED AGENTS
  Primary: [agents for core work]
  Secondary: [agents for specific tasks]

KEY WORKFLOWS
  [consolidated workflows]

CONVENTIONS
  [code style, patterns]

QUICK COMMANDS
  [common commands]

Step 4: Offer Consolidation

If 2+ documentation files exist, offer to consolidate:

Create .doc-archive/ directory
Archive originals with date suffix
Generate unified AGENTS.md
Report what was consolidated

Step 5: No Documentation Found

If none found, offer to generate AGENTS.md based on:

Project structure and tech stack
Patterns observed in codebase

Priority Order

AGENTS.md (platform-agnostic)
CLAUDE.md (Claude-specific)
Other AI docs
IDE docs
Terminal docs

Additional Resources

For detailed patterns, load:

./references/file-patterns.md - Complete list of files to scan
./references/templates.md - AGENTS.md generation templates

When generating a NEW AGENTS.md, follow the entry-doc standard in rules/agentic-quality.md (Landmines section mandatory, ~150-line budget) — skeleton at the repo-doctor skill's assets/AGENTS-template.md. To AUDIT an existing doc set rather than generate one, hand off to repo-doctor.