From research-skill
Use when the user asks to research, investigate, or figure out something about their codebase or a technical topic. Triggers on phrases like "research ...", "investigate ...", "figure out how ...", "look into ...", "dig into ...", "find out how ...", or "understand how ...". Launches the /research-codebase command workflow for thorough, structured research.
How this skill is triggered — by the user, by Claude, or both
Slash command
/research-skill:research-triggerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The user is asking you to research or investigate a topic. You MUST use the `/research-codebase` command to handle this request.
The user is asking you to research or investigate a topic. You MUST use the /research-codebase command to handle this request.
The user said something like:
/research-codebase command using the Skill tool with skill: "research-codebase"./research-codebase command produces a thorough, documented research artifact — that is the expected output.npx claudepluginhub jeremygiberson/research-skill-plugin --plugin research-skillDocuments codebases as-is by spawning parallel sub-agents to research files and synthesize findings into reports. Activates on /research or codebase understanding requests.
Explores codebase topics by searching prior knowledge and conducting multi-angle analysis, outputting structured findings. Supports /research command and optional auto mode.
Gathers prior art and context: scans codebase via explorer subagent, dependencies, docs, git history; synthesizes research.md for think skill on complex features.