context-engine
Skill400 starsChanged 24 days agoMITView on GitHub
Search and understand the indexed codebase with Context Engine (hybrid semantic + lexical search, reranked, with a symbol graph). Use for any question about this codebase - where something is implemented, how it works, callers/definitions, every place that does X - before ls/find/Grep/Read.
9 other projects use a version of this.
Adopted by
Most recently taken up by
- darkweb19/skillstheir own version, first seen Nov 8, 2026
- relote-com/omarchy-context-enginetheir own version, first seen Nov 8, 2026
- teachskillofskills-ai/DigitalMarketingPro-techshutheir own version, first seen Oct 11, 2026
- m1rl0k/Context-Enginetheir own version, first seen Oct 8, 2026
- 2867203296/hermes-agenttheir own version, first seen Aug 19, 2026
- Hassaan146/claude-skillstheir own version, first seen Jul 25, 2026
Used with
Projects with it also use andreessen, business-investment-advisor and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Hussain-ElfalahSkillandreessen
Also in 4 projects that use this
- Hussain-ElfalahSkill
business-investment-advisor
Also in 4 projects that use this
csiddhant796-blipSkillkarpathy-coder
Use when writing, reviewing, or committing code to enforce Karpathy's 4 coding principles — surface assumptions before coding, keep it simple, make surgical changes, define verifiable goals. Triggers on "review my diff", "check complexity", "am I overcomplicating this", "karpathy check", "before I commit", or any code quality concern where the LLM might be overcoding.
Also in 4 projects that use this
- +9 more from Hussain-Elfalah
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- indranilbanerjee/digital-marketing-pro★ 934same name
- Hassaan146/claude-skills★ 18same name
- relote-com/omarchy-context-engine★ 4same name
- m1rl0k/Context-Engine★ 3same name
- Hussain-Elfalah/Agentic-Skills★ 2same name
- mahiunfiltered/claude-code-skills★ 1same name
- 2867203296/hermes-agent★ 0same name
- darkweb19/skills★ 0same name
- teachskillofskills-ai/DigitalMarketingPro-techshu★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Before editing, fetch every involved symbol in one call.
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Context Engine
When the context-engine MCP server is connected, this workspace is indexed: for any question about the codebase, call repo_search FIRST, before ls/find/Grep/Read, and again whenever you move to a new area; for how/why questions that span several files use context_answer. Results are verified source with exact line ranges: treat them as already read. Use Grep only to confirm an exact literal in a file you already know, or to count. For questions asking for every/all sites, run one repo_search per distinct pattern (queries=[...]) and follow the refs. If the tools are listed as deferred, load them with ToolSearch first.
| Need | Tool |
| Find code by behavior, concept, error text or identifier | repo_search (queries=[...] for several at once; under, language, path_glob to narrow) |
| Explain how/why across several files, with citations | context_answer |
| Definition, callers, callees, importers, references of a symbol | symbol_graph (several names: A|B|C) |
| Multi-hop impact before a change | graph_query |
| Code that may live in another indexed repo | cross_repo_search |
Before editing, fetch every involved symbol in one call; before a rename or signature change, get every site with symbol_graph query_type=references. Search again only after learning something new.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.