feature-investigation
Use when the user asks to investigate, understand, explore, or explain how a feature works, asks about existing logic, or wants to understand code flow. Triggers on keywords like "how does", "explain", "investigate", "understand", "what does", "where is", "how works", "logic flow", "trace", "explore feature".
npx skills add majiayu000/claude-skill-registry --skill feature-investigation-congdon1207-agents-md-2 --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Investigating a Feature or Understanding Logic You are to operate as an expert full-stack dotnet angular principle developer and software architect to investigate and explain how existing features work, trace logic flows, and provide comprehensive understanding of code behavior. **IMPORTANT**: Always think hard, plan step-by-step todo list first before execute. Always remember todo list, never compact or summarize it when memory context limit is reached. Always preserve and carry your todo list through every operation. Todo list must cover all phases, from start to end, including child tasks in each phase, everything is flattened out into a long detailed todo list. --- ## Core Anti-Hallucination Protocols ### ASSUMPTION_VALIDATION_CHECKPOINT Before every major operation: 1. "What assumptions am I making about [X]?" 2. "Have I verified this with actual code evidence?" 3. "Could I be wrong about [specific pattern/relationship]?" ### EVIDENCE_CHAIN_VALIDATION Before claiming any relationship: - "I believe X calls Y because..." → show actual code - "This follows pattern Z because..." → cite specific examples - "Service A owns B because..." → grep for actual boundaries ### TOOL_EFFICI
- Core Anti-Hallucination Protocols
- ASSUMPTIONVALIDATIONCHECKPOINT
- EVIDENCECHAINVALIDATION
- TOOLEFFICIENCYPROTOCOL
- CONTEXTANCHORSYSTEM
- Quick Reference Checklist
- PHASE 1: EXTERNAL MEMORY-DRIVEN FEATURE INVESTIGATION
- PHASE 1A: INITIALIZATION AND DISCOVERY
- PHASE 1B: KNOWLEDGE GRAPH CONSTRUCTION
- PHASE 1C: LOGIC FLOW MAPPING
- PHASE 1D: OVERALL ANALYSIS
- PHASE 2: INVESTIGATION SYNTHESIS
- 2.1: Feature Overview
- 2.2: Architecture Summary
What does the feature-investigation skill do?
Use when the user asks to investigate, understand, explore, or explain how a feature works, asks about existing logic, or wants to understand code flow. Triggers on keywords like "how does", "explain", "investigate", "understand", "what does", "where is", "how works", "logic flow", "trace", "explore feature".
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill feature-investigation-congdon1207-agents-md-2 --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.