Agent skill · Documentation

investigation

Systematic codebase investigation producing structured Obsidian documentation with DataviewJS auto-indexing

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

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

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

# Skill: investigation ## What I do I conduct systematic codebase investigations using parallel agent exploration, synthesise findings into a structured set of Obsidian documents, and create auto-generated DataviewJS indexes for discovery and navigation. The output is a reproducible, searchable investigation record stored in the user's Obsidian vault. ## When to use me - When conducting a discovery or audit of an application or codebase - When asked to investigate, explore, or assess a project - When producing structured findings for a codebase review - When the user wants a documented record of a project investigation --- ## Investigation Workflow ### Phase 1: Plan 1. Identify project (name, language, entry point) 2. Identify vault (default: `/home/baphled/vaults/baphled/`) 3. Determine folder: `1. Projects/{Project}/Investigations/{YYYY-MM-DD}/` 4. Create todo list to track progress ### Phase 2: Explore (6 Parallel Agents) Launch agents for: structure, architecture, debt, testing, CI/CD, documentation. Each returns metrics, file paths, and assessments. ### Phase 3: Synthesise Documents Create 6 numbered documents: - `00-Executive-Summary.md` — Good/Bad/Ugly, metrics, assessment -

What's inside
Steps it walks through
  1. What I do
  2. When to use me
  3. Investigation Workflow
  4. Phase 1: Plan
  5. Phase 2: Explore (6 Parallel Agents)
  6. Phase 3: Synthesise Documents
  7. Phase 4: Create Auto-Generated Indexes
  8. Phase 5: Store in Memory
  9. Document Conventions
  10. DataviewJS Rules
  11. Folder Structure
  12. Anti-patterns to avoid
  13. KB Reference
  14. Related skills
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the investigation skill do?

Systematic codebase investigation producing structured Obsidian documentation with DataviewJS auto-indexing

How do I install it?

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