Octocode Code Research
bgauryy/octocode
Researches code with evidence: traces callers, imports and cross-repo links, diagnoses failures and reports findings with exact file and line references and a confidence label.
Investigate source-code bugs, incidents, regressions, production issues, and failures to root cause with Memtrace symbol search, impact, call graph, and temporal history.
Install Memtrace Incident Investigation
$ npx skills add syncable-dev/memtrace-public --skill memtrace-incident-investigation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install syncable-dev/memtrace-public memtrace-incident-investigation --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/syncable-dev/memtrace-public.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/memtrace-skills/skills/memtrace-incident-investigation .claude/skills/memtrace-incident-investigation && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "memtrace-incident-investigation" agent skill from https://github.com/syncable-dev/memtrace-public/tree/main/plugins/memtrace-skills/skills/memtrace-incident-investigation into .claude/skills/memtrace-incident-investigation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memtrace-incident-investigation", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/syncable-dev/memtrace-public/tree/main/plugins/memtrace-skills/skills/memtrace-incident-investigationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add syncable-dev/memtrace-public --skill memtrace-incident-investigation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install syncable-dev/memtrace-public memtrace-incident-investigation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/syncable-dev/memtrace-public.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/memtrace-skills/skills/memtrace-incident-investigation .agents/skills/memtrace-incident-investigation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "memtrace-incident-investigation" agent skill from https://github.com/syncable-dev/memtrace-public/tree/main/plugins/memtrace-skills/skills/memtrace-incident-investigation into .agents/skills/memtrace-incident-investigation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memtrace-incident-investigation", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add syncable-dev/memtrace-public --skill memtrace-incident-investigation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install syncable-dev/memtrace-public memtrace-incident-investigation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/syncable-dev/memtrace-public.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/memtrace-skills/skills/memtrace-incident-investigation .cursor/skills/memtrace-incident-investigation && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "memtrace-incident-investigation" agent skill from https://github.com/syncable-dev/memtrace-public/tree/main/plugins/memtrace-skills/skills/memtrace-incident-investigation into .cursor/skills/memtrace-incident-investigation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memtrace-incident-investigation", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/syncable-dev/memtrace-public.git --path plugins/memtrace-skills/skills/memtrace-incident-investigation--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add syncable-dev/memtrace-public --skill memtrace-incident-investigation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install syncable-dev/memtrace-public memtrace-incident-investigation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/syncable-dev/memtrace-public.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/memtrace-skills/skills/memtrace-incident-investigation .gemini/skills/memtrace-incident-investigation && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "memtrace-incident-investigation" agent skill from https://github.com/syncable-dev/memtrace-public/tree/main/plugins/memtrace-skills/skills/memtrace-incident-investigation into .gemini/skills/memtrace-incident-investigation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memtrace-incident-investigation", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install syncable-dev/memtrace-public memtrace-incident-investigationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add syncable-dev/memtrace-public --skill memtrace-incident-investigation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/syncable-dev/memtrace-public.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/memtrace-skills/skills/memtrace-incident-investigation .github/skills/memtrace-incident-investigation && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "memtrace-incident-investigation" agent skill from https://github.com/syncable-dev/memtrace-public/tree/main/plugins/memtrace-skills/skills/memtrace-incident-investigation into .github/skills/memtrace-incident-investigation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memtrace-incident-investigation", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add syncable-dev/memtrace-public --skill memtrace-incident-investigation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install syncable-dev/memtrace-public memtrace-incident-investigation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/syncable-dev/memtrace-public.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/memtrace-skills/skills/memtrace-incident-investigation .opencode/skills/memtrace-incident-investigation && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "memtrace-incident-investigation" agent skill from https://github.com/syncable-dev/memtrace-public/tree/main/plugins/memtrace-skills/skills/memtrace-incident-investigation into .opencode/skills/memtrace-incident-investigation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memtrace-incident-investigation", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
memtrace-incident-investigation- GitHub stars
- 487
- Token cost
- ~1.8k tokens
- SKILL.md length
- 805 words
- Files
- 1
- Skills in repo
- 27
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Investigate source-code bugs, incidents, regressions, production issues, and failures to root cause with Memtrace symbol search, impact, call graph, and temporal history.
- Works in 10 steps: Establish the timeline → List changes near the incident → Identify hotspot files and symbols → …
- The user asks about root cause analysis
- SKILL.md covers Overview, Steps, Report: Root Cause Analysis and Tool selection guide for…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Memtrace Incident Investigation is an agent skill from syncable-dev/memtrace-public. Investigate source-code bugs, incidents, regressions, production issues, and failures to root cause with Memtrace symbol search, impact, call graph, and temporal history. Use when the user asks about root cause analysis, what broke, or what changed when debugging a failure. Do not start with Grep, Glob, rg, find, or manual file search for code causes. For plain what-changed questions without a failure, use memtrace-evolution.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Root cause analysis and Codebase onboarding. The repository describes itself as: Structural memory for AI coding agents. Bi-temporal graph, MCP-native, zero LLM calls. Cursor · Claude Code · Codex · DeepSeek Harness · Hermes · VS Code · Windsurf.
When your agent uses it
- The user asks about root cause analysis
- What changed when debugging a failure
Example prompts
- “/memtrace-incident-investigation”
Workflow steps
10 steps, taken from the step headings in SKILL.md.
- Establish the timeline
- List changes near the incident
- Identify hotspot files and symbols
- Check for unexpected changes to stable code
- Assess the blast radius
- Trace execution flows
- Build the full timeline for the suspect
- Correlate adds vs removes per episode
- Check historical coupling (cochange)
- Replay the sub-commit implementation history (if needed)
What it can do on your machine
Read from SKILL.md and the folder at commit 3a3084d. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Memtrace Incident Investigation loads about 1.8k tokens when it runs. Until then it costs about 115 tokens; SKILL.md has 805 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 805 words (~1,849 tokens).
“Root cause investigation workflow for incidents, regressions, and production issues. Uses get_evolution to list changes near the incident time, then traces blast radius and execution flows to identify the likely cause.”
- name
- memtrace-incident-investigation
Files
Just SKILL.md in plugins/memtrace-skills/skills/memtrace-incident-investigation of syncable-dev/memtrace-public.
Open the folder on GitHubat commit 3a3084d
Compare with similar skills
Memtrace Incident Investigation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Memtrace Incident Investigation this skillsyncable-dev/memtrace-public | 487 | — | ~1.8k | Automated safety check: Pass | Custom licence | |
| Octocode Code Researchbgauryy/octocode | 949 | — | ~1.5k | Automated safety check: Pass | MIT | |
| CodeScope Codebase Graph AnalysisQwenLM/qwen-code | 28k | 1 repos | ~9.3k | Automated safety check: Pass | Apache-2.0 | |
| Codegraph QAQwenLM/qwen-code-examples | 143 | — | ~4.3k | Automated safety check: Pass | None | |
| Codebase Knowledge Graph Q&AEgonex-AI/Understand-Anything | 86k | 1 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Code Design Rationale Investigatorcursor/plugins | 10k | 9 repos | ~2.6k | Automated safety check: Pass | None |
Similar skills
CodeScope Codebase Graph Analysis
QwenLM/qwen-code
Answers questions about code structure, history, bugs and PR risk using a CodeScope knowledge graph and semantic index built from the repository.
Codegraph QA
QwenLM/qwen-code-examples
Use CodeScope to analyze any indexed codebase via its graph database (neug) and vector index (zvec).
Codebase Knowledge Graph Q&A
Egonex-AI/Understand-Anything
Answers questions about a codebase by searching a prebuilt knowledge graph of its files, functions, classes and dependencies, not by rereading every source file.
- Official
Code Design Rationale Investigator
cursor/plugins
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
Understand Explain
Egonex-AI/Understand-Anything
Gives an in-depth explanation of one file, function or module by reading the project's knowledge graph and checking that the graph is still fresh.
More from syncable-dev/memtrace-public
All 27 skills in this repoMemtrace Change Impact Analysis
syncable-dev/memtrace-public
Compute what a planned source-code change will break — blast radius, affected processes, cross-repo callers, temporal stability, and Cortex decision-memory constraints — and produce a risk-rated…
Memtrace Cochange
syncable-dev/memtrace-public
Find files that historically co-change with a target symbol or file, ranked by co-occurrence across git episodes.
Memtrace Code Review
syncable-dev/memtrace-public
Review GitHub pull requests with Memtrace's local graph-backed review engine.
Memtrace Codebase Exploration
syncable-dev/memtrace-public
Map an indexed source-code repo into a structured overview — scale, communities, central symbols, execution flows, API surface, recent activity.
Memtrace Continuous Memory
syncable-dev/memtrace-public
Keep the Memtrace index fresh while editing by watching a repo for live, incremental re-indexing.
Memtrace Decision Memory
syncable-dev/memtrace-public
Use Cortex decision memory through the normal Memtrace MCP tools.
Related
Categories
Questions about Memtrace Incident Investigation
What does Memtrace Incident Investigation do?
Investigate source-code bugs, incidents, regressions, production issues, and failures to root cause with Memtrace symbol search, impact, call graph, and temporal history. Memtrace Incident Investigation is an agent skill from syncable-dev/memtrace-public. Investigate source-code bugs, incidents, regressions, production issues, and failures to root cause with Memtrace symbol search, impact, call graph, and temporal history.
When should I use Memtrace Incident Investigation?
Memtrace Incident Investigation fits situations like: the user asks about root cause analysis; what changed when debugging a failure.
How do I install Memtrace Incident Investigation in Claude Code?
Run `npx skills add syncable-dev/memtrace-public --skill memtrace-incident-investigation -a claude-code`. Or copy the skill folder (plugins/memtrace-skills/skills/memtrace-incident-investigation in syncable-dev/memtrace-public) into .claude/skills/memtrace-incident-investigation in your project. Claude Code loads it when a task matches its description.
How do I install Memtrace Incident Investigation in Codex?
Run `npx skills add syncable-dev/memtrace-public --skill memtrace-incident-investigation -a codex`. Or copy the skill folder (plugins/memtrace-skills/skills/memtrace-incident-investigation in syncable-dev/memtrace-public) into .agents/skills/memtrace-incident-investigation in your project. Codex loads it when a task matches its description.
Can I use Memtrace Incident Investigation in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add syncable-dev/memtrace-public --skill memtrace-incident-investigation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/memtrace-incident-investigation, .gemini/skills/memtrace-incident-investigation, .github/skills/memtrace-incident-investigation and .opencode/skills/memtrace-incident-investigation in your project.
What does Memtrace Incident Investigation need to run?
SKILL.md names no scripts, command-line tools or credentials: Memtrace Incident Investigation is instructions for the agent only.
Does Memtrace Incident Investigation access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Memtrace Incident Investigation safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Memtrace Incident Investigation use?
Memtrace Incident Investigation has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Memtrace Incident Investigation use?
About 1.8k tokens (SKILL.md is roughly 7.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Memtrace Incident Investigation?
Skills that share tags, products or a category with Memtrace Incident Investigation: Octocode Code Research (bgauryy/octocode, 949 stars), CodeScope Codebase Graph Analysis (QwenLM/qwen-code, 28k stars), Codegraph QA (QwenLM/qwen-code-examples, 143 stars) and Codebase Knowledge Graph Q&A (Egonex-AI/Understand-Anything, 86k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Memtrace Incident Investigation?
syncable-dev (a GitHub organization) maintains it in syncable-dev/memtrace-public, which has 487 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on October 8, 2026.
Source: syncable-dev/memtrace-public on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.