How do I install the Code Research skill?

Run npx get-skill add quegenx/code-research in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Code Research safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Code Research?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Code Research free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Code Research?

Quegenx (@quegenx) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Code Research by quegenx — Agent Skill

Name: Code Research
Rating: 4.5 (4 reviews)
Author: Quegenx

Code Research

Investigates code questions from exact source, callers, history and observed results, preserving evidence, version identity, confidence and coverage limits. Use when locating an implementation, explaining behavior or historical rationale, tracing dependencies, comparing a change or researching an installed dependency.

Quegenx Updated Nov 12, 2026

File contents

Code research

Find the source that settles the question and report what the evidence supports. Sources: [bgauryy/octocode, octocode-research], [JuliusBrussee/caveman, caveman-explore and cavecrew], and [dzhng/jevgrep, jevgrep]. The debugging skill owns causal diagnosis; agent-harness WORKFLOWS.md owns delegation.

Apply only the routes and checks for the selected job. Read a linked skill's named file from its installed folder when available, or from the linked source. Report an unavailable required reference instead of inventing it. [skill-authoring, DISTRIBUTION.md#composing-skills]

The job	Read
Choose the research boundary and evidence requirements	SKILL.md
Locate source, establish behavior or historical motivation, keep a confidence ledger and explain the observed flow	SOURCE-RESEARCH.md

The rules

Start from the strongest supplied handle. Use the exact path, identifier, code shape or installed revision before repeating discovery. [bgauryy/octocode, octocode-research/references/algorithm.md and researcher-mindset.md]
Match proof to the claim. Cross-check consequential conclusions using exact source and the relevant structure or connections; preserve failed, partial and unavailable searches as coverage limits. [bgauryy/octocode, octocode-research/references/code-research.md]
Record the actual revision and scope. A requested ref can differ from the resolved ref; an inventory and search need matching roots and exclusions. [bgauryy/octocode, octocode-research/references/algorithm.md; dzhng/jevgrep, jevgrep/SKILL.md]
Track alternatives and stop on evidence. Keep the decisive anchors, confidence, unresolved explanation and next check; another call must be able to change the conclusion. [bgauryy/octocode, octocode-research/references/loop-mode.md]
Return locations actually read. Preserve exact paths, ranges and continuation handles, and distinguish localization from a broader architecture proposal. [JuliusBrussee/caveman, caveman-explore/SKILL.md and cavecrew/SKILL.md]

Prove it

Use SOURCE-RESEARCH.md to check each conclusion's anchors, coverage, revision and unresolved alternatives. [bgauryy/octocode, octocode-research/references/code-research.md and loop-mode.md]

---name: code-researchdescription: "Investigates code questions from exact source, callers, history and observed results, preserving evidence, version identity, confidence and coverage limits. Use when locating an implementation, explaining behavior or historical rationale, tracing dependencies, comparing a change or researching an installed dependency."metadata: source: https://skillmd.com/skills/quegenx/code-research---# Code researchFind the source that settles the question and report what the evidence supports. Sources: [bgauryy/octocode, octocode-research], [JuliusBrussee/caveman, caveman-explore and cavecrew], and [dzhng/jevgrep, jevgrep]. The [debugging skill](https://github.com/Quegenx/agent-skills/blob/main/skills/engineering/debugging/SKILL.md) owns causal diagnosis; [agent-harness WORKFLOWS.md](https://github.com/Quegenx/agent-skills/blob/main/skills/ai-agents/agent-harness/WORKFLOWS.md#delegation-packets) owns delegation.Apply only the routes and checks for the selected job. Read a linked skill's named file from its installed folder when available, or from the linked source. Report an unavailable required reference instead of inventing it. [skill-authoring, DISTRIBUTION.md#composing-skills]| The job | Read ||---|---|| Choose the research boundary and evidence requirements | [SKILL.md](SKILL.md) || Locate source, establish behavior or historical motivation, keep a confidence ledger and explain the observed flow | [SOURCE-RESEARCH.md](SOURCE-RESEARCH.md) |## The rules1. **Start from the strongest supplied handle.** Use the exact path, identifier, code shape or installed revision before repeating discovery. [bgauryy/octocode, octocode-research/references/algorithm.md and researcher-mindset.md]2. **Match proof to the claim.** Cross-check consequential conclusions using exact source and the relevant structure or connections; preserve failed, partial and unavailable searches as coverage limits. [bgauryy/octocode, octocode-research/references/code-research.md]3. **Record the actual revision and scope.** A requested ref can differ from the resolved ref; an inventory and search need matching roots and exclusions. [bgauryy/octocode, octocode-research/references/algorithm.md; dzhng/jevgrep, jevgrep/SKILL.md]4. **Track alternatives and stop on evidence.** Keep the decisive anchors, confidence, unresolved explanation and next check; another call must be able to change the conclusion. [bgauryy/octocode, octocode-research/references/loop-mode.md]5. **Return locations actually read.** Preserve exact paths, ranges and continuation handles, and distinguish localization from a broader architecture proposal. [JuliusBrussee/caveman, caveman-explore/SKILL.md and cavecrew/SKILL.md]## Prove itUse [SOURCE-RESEARCH.md](SOURCE-RESEARCH.md#prove-it) to check each conclusion's anchors, coverage, revision and unresolved alternatives. [bgauryy/octocode, octocode-research/references/code-research.md and loop-mode.md]

Frequently asked questions