Agent skill

feature-investigation

Use when the user asks to investigate, explore, understand, explain, or analyze how an existing feature or logic works. Triggers on keywords like "how does", "explain", "what is the logic", "investigate", "understand", "where is", "trace", "walk through", "show me how".

majiayu000github.com/majiayu000GitHub ↗
claude-coderead-onlyMIT
Install
npx skills add majiayu000/claude-skill-registry --skill feature-investigation-congdon1207-agents-md-4 --agent claude-code

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

Facts
Files in the skill folder: 2
SKILL.md size: 12 KB
Bundled scripts: none
Allowed tools: ReadGrepGlobTaskWebFetchWebSearchTodoWrite
Path: skills/analysis/feature-investigation-congdon1207-agents-md-4/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 Variant:** Use this skill for **investigating and understanding** existing features or logic. This is a READ-ONLY exploration skill - no code changes. For implementing new features, use `feature-implementation`. For debugging, use `bug-diagnosis`. # Feature Investigation & Logic Exploration You are to operate as an expert full-stack dotnet angular principal developer and software architect to investigate and explain how an existing feature or logic works in `[feature-description-or-question]`. **IMPORTANT**: Always thinks hard, plan step by step to-do list first before execute. Always remember to-do list, never compact or summary it when memory context limit reach. Always preserve and carry your to-do list through every operation. Todo list must cover all phases, from start to end, include child tasks in each phases too, everything is flatted out into a long detailed todo list. **KEY DIFFERENCE FROM OTHER SKILLS**: This is a **READ-ONLY investigation skill**. You are NOT implementing or fixing anything - you are building understanding and explaining how things work. --- ## Core Anti-Hallucination Protocols ### ASSUMPTION_VALIDATION_CHECKPOINT Before every major operation:

What's inside
Steps it walks through
  1. Core Anti-Hallucination Protocols
  2. ASSUMPTIONVALIDATIONCHECKPOINT
  3. EVIDENCECHAINVALIDATION
  4. TOOLEFFICIENCYPROTOCOL
  5. CONTEXTANCHORSYSTEM
  6. Quick Reference Checklist
  7. PHASE 1: EXTERNAL MEMORY-DRIVEN FEATURE INVESTIGATION
  8. PHASE 1A: INITIALIZATION AND DISCOVERY
  9. PHASE 1B: KNOWLEDGE GRAPH CONSTRUCTION
  10. PHASE 1C: DATA FLOW MAPPING
  11. PHASE 2: COMPREHENSIVE ANALYSIS
  12. PHASE 2A: WORKFLOW ANALYSIS
  13. PHASE 2B: ARCHITECTURAL ANALYSIS
  14. PHASE 2C: BUSINESS LOGIC EXTRACTION
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the feature-investigation skill do?

Use when the user asks to investigate, explore, understand, explain, or analyze how an existing feature or logic works. Triggers on keywords like "how does", "explain", "what is the logic", "investigate", "understand", "where is", "trace", "walk through", "show me how".

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill feature-investigation-congdon1207-agents-md-4 --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