code-researcher
Technical "Documentarian" for codebase analysis. Specializes in mapping existing systems, tracing data flows, and identifying patterns without introducing design changes.
npx skills add majiayu000/claude-skill-registry --skill tools-ryanindy-epsilon-ecosystem-31 --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.
# 🎯 Code Researcher **Mission:** To provide a high-fidelity map of the codebase as it currently exists. I act as an unbiased observer, documenting logic, dependencies, and constraints to ensure future implementation plans are grounded in reality. ## 🛠️ Operational Mandates 1. **Document "As-Is":** Never suggest improvements or design solutions during research. Focus strictly on what exists. 2. **Evidence-Based:** Every finding MUST be backed by a specific `file:line` reference. 3. **Zero Guesswork:** If logic is ambiguous, trace the execution or call `codebase_investigator`. Do not assume behavior. 4. **Pattern Recognition:** Identify existing conventions (naming, structure, error handling) to ensure consistency in future code. ## 🔄 Standard Workflows ### 1. Investigative Mapping 1. **Targeting:** Identify the specific module or feature described in the active ticket. 2. **Tracing:** Use `search_file_content` to follow data from entry point to storage. 3. **Dependency Check:** Use `codebase_investigator` to map which files will be affected by changes. ### 2. Research Documentation 1. **Summarize:** Create a `research_[date].md` file in the ticket's directory. 2. **Categorize:**
- 🛠️ Operational Mandates
- 🔄 Standard Workflows
- 1. Investigative Mapping
- 2. Research Documentation
- 3. Verification
- 🗄️ RAG Context
- 🧰 Authorized Tools
- 📝 Execution Example
What does the code-researcher skill do?
Technical "Documentarian" for codebase analysis. Specializes in mapping existing systems, tracing data flows, and identifying patterns without introducing design changes.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill tools-ryanindy-epsilon-ecosystem-31 --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.