Agent skill

dive

Dives deep into project questions using layered investigation (docs → code → analysis) to provide evidence-based answers with file:line citations. Use when asking "how does X work", "what is Y", "where is Z", or investigating features, APIs, configuration, codebase structure, or technical decisions.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill dive --agent claude-code

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

Facts
Files in the skill folder: 2
SKILL.md size: 5 KB
Bundled scripts: none
Path: skills/analysis/dive/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

# Dive Dives deep into your project to investigate any question, from business logic to technical implementation. Uses layered search strategy to find evidence-based answers backed by documentation and code. ## Philosophy ### Why Dive? Dive exists because **assumptions are dangerous**. The core question isn't "how do I find the answer?" but "how do I know my answer is true?" ``` The Fundamental Problem: ├── Memory is unreliable (yours and the codebase's docs) ├── Code evolves faster than documentation ├── "I think it works like..." is not evidence └── Only the current codebase tells the current truth ``` ### Evidence Over Intuition ``` Intuition: "This probably uses X pattern" Dive: "render.ts:273 shows reconcileKeyedChildren() implementation" ``` Intuition is a starting point, not an answer. Dive converts intuition into verified knowledge through evidence gathering. ### Layered Search: Why This Order? ``` Layer 1: Documentation → What the project CLAIMS to do Layer 2: Code → What the project ACTUALLY does Layer 3: Deep Analysis → HOW it all connects ``` Why documentation first? - It's faster to read - It gives you vocabulary for code search - Discrepancies between docs and code ar

What's inside
Steps it walks through
  1. Philosophy
  2. Why Dive?
  3. Evidence Over Intuition
  4. Layered Search: Why This Order?
  5. Cross-Referencing Reveals Truth
  6. Core Concepts
  7. Evidence Has Hierarchy
  8. The Question Shapes the Search
  9. Uncertainty is Information
  10. The Dive Loop
  11. When Layers Conflict
  12. Reference
  13. Understanding, Not Rules
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the dive skill do?

Dives deep into project questions using layered investigation (docs → code → analysis) to provide evidence-based answers with file:line citations. Use when asking "how does X work", "what is Y", "where is Z", or investigating features, APIs, configuration, codebase structure, or technical decisions.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill dive --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