Individual skill
octocode-research
Use when code must be checked, not assumed: trace connections (callers, imports, cross-repo wiring, what breaks if I change it), locate behavior, map a system, diagnose a failure, RCA. Also for external repositories, npm packages, upstream/prior art, and general research. Plan a coding flow before writing, validate it after. Triggers on 'research this' or 'use octocode'. Gives exact file:line/PR/commit evidence with confidence. Skip trivial edits whose blast radius is already known. Not for authoring or copyediting the docs themselves, or for building skill folders: docs deliverable → octocode-documentation; SKILL.md folders → octocode-skills.
skills/octocode-research/SKILL.md
Source commit c265e3f9413161c900cbf4aa70d451b8e6b3920a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 957
- Repository last updated
- Nov 6, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai Repository topic
- claude-ai Repository topic
- cursor-ai Repository topic
- development Repository topic
- mcp Repository topic
- modelcontextprotocol Repository topic
- octocode Repository topic
- ai-agents Repository topic
- ai-tools Repository topic
- code-intelligence Repository topic
- docs Derived category
- engineering Derived category
- writing Derived category
- research Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
README.mddoc · 3,633 bytesSKILL.mdcore · 5,943 bytesSKILL.mdcore · 5,943 bytesagents/openai.yamlasset · 295 bytesreferences/algorithm.mddoc · 3,057 bytesreferences/code-research.mddoc · 3,361 bytesreferences/github-landscape.mddoc · 2,363 bytesreferences/improve-loop.mddoc · 2,017 bytesreferences/long-research.mddoc · 2,501 bytesreferences/loop-mode.mddoc · 2,326 bytesreferences/octocode.mddoc · 4,734 bytesreferences/problem-framing.mddoc · 2,396 bytesreferences/research-flow.mddoc · 3,162 bytesreferences/researcher-mindset.mddoc · 4,511 bytesreferences/workflow-change.mddoc · 1,860 bytesreferences/workflow-combination.mddoc · 2,250 bytesreferences/workflow-debug.mddoc · 1,964 bytesreferences/workflow-external.mddoc · 1,832 bytesreferences/workflow-local.mddoc · 1,371 bytesreferences/workflow-pr-review-analysis.mddoc · 2,918 bytesreferences/workflow-pr-review-report.mddoc · 2,127 bytesreferences/workflow-pr-review.mddoc · 2,985 bytesreferences/workflow-refactor.mddoc · 2,733 bytesreferences/workflows.mddoc · 3,987 bytesscripts/check-description.mjsruns · 1,825 bytes
Read excerpt
# Octocode Research
Evidence before assertion. Find the anchor, read the exact bytes, prove the claim, then answer or patch.
```text
FRAME → CLASSIFY → MODEL → SEARCH → READ EXACT → PROVE → DECIDE/PATCH → VERIFY
```
That's the full shape, not a checklist to march through. Scale it to the claim: a small lookup gets a cheap read and an honest confidence label; a delete, a merge verdict, or a root cause earns the whole ladder. Skip stages you can already answer — but say which ones you skipped.
## The rules
1. Open with one line: corpus, actual vs desired, task class, mode, surfaces used and skipped.
2. Call it a bug only when evidence shows a supported contract was violated.