researching-codebase
This skill should be used when the user asks to "research the codebase", "understand how X works", "explore the code", "gather context", "investigate the implementation", "analyze the architecture", or invokes the rpikit:research command. Provides methodology for thorough interrogation and codebase exploration before planning or implementation.
npx skills add majiayu000/claude-skill-registry --skill researching-codebase-bostonaholic-rpikit-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.
# Research Methodology Research topic: **$ARGUMENTS** ## Overview Help turn research requests into thorough codebase understanding through natural collaborative dialogue. Start by understanding what the user needs to learn, then ask questions one at a time to refine the scope. Once you understand what you're researching, explore the codebase systematically, presenting findings in digestible sections and validating as you go. ## The Iron Law **Ask questions BEFORE exploring code.** Do not touch the codebase until the problem is understood. Resist the urge to immediately search for files or read code. ## Phase 1: Understanding the Request **Your first action must be asking a clarifying question.** Do NOT: - Read any files - Search the codebase - Use Glob or Grep - Explore anything - Make assumptions about what the user wants **Ask questions one at a time using AskUserQuestion:** - Prefer multiple choice questions when possible, but open-ended is fine too - Only one question per message - If a topic needs more exploration, break it into multiple questions **Focus on understanding:** - **Purpose**: What are they trying to accomplish? (build, change, fix, learn) - **Specifics**: What ex
- Overview
- The Iron Law
- Phase 1: Understanding the Request
- Phase 2: Exploration
- Locate Relevant Files
- Explore the Discovered Files
- Research External Context (When Needed)
- Phase 3: Document Findings
- Phase 4: Transition
- Questioning Techniques
- Anti-Patterns
- Key Principles
- Markdown Validation
What does the researching-codebase skill do?
This skill should be used when the user asks to "research the codebase", "understand how X works", "explore the code", "gather context", "investigate the implementation", "analyze the architecture", or invokes the rpikit:research command. Provides methodology for thorough interrogation and codebase exploration before planning or implementation.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill researching-codebase-bostonaholic-rpikit-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.