agentsclimarketplace

Code recon

Skill HexBen123/skills/skills/code-recon/shells/.cursor/skills/code-recon

This skill should be used whenever a task requires locating, tracing, or understanding code in an existing codebase before reading or editing it — any time the instinct is to Grep / Glob / open files at random to find "where" something is or "how" it flows. Trigger on requests like "这个功能在哪里实现的", "这段逻辑/这个流程是怎么走的", "谁调用了这个方法", "改这个函数会影响哪些地方", "这个事件/回调是谁触发的", "帮我理解这个项目", "where is X implemented", "how does X work", "what calls X / what breaks if I change X", or "find the code that handles X". Activate for any non-trivial or unfamiliar codebase where the fast-context (semantic) and/or codegraph (structural) MCP tools are available — this skill is when to reach for those MCP tools instead of hand-searching, and how to combine them.From its SKILL.md

Install
npx -y skills add HexBen123/skills --skill code-recon

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.9 KB, 273 tokens by cl100k_base, as published. Nobody here has run it

code-recon (Cursor Entry)

Formal skill content lives at skills/code-recon/SKILL.md. Read that file immediately, then follow its Always Read list and Common Tasks routing.

Quick Routing (survives context truncation)

All paths under skills/code-recon/.

TaskReadWorkflow
Explore / "where is X" / no symbol name yetrules/using-the-tools.mdworkflows/recon-playbook.md §A
Trace flow / "how does X work" / who triggers eventrules/using-the-tools.mdworkflows/recon-playbook.md §B
Callers / impact / "what breaks if I change X"rules/using-the-tools.mdworkflows/recon-playbook.md §C
Known-symbol lookup / source of Xrules/using-the-tools.mdworkflows/recon-playbook.md §D
Other / unlistedrules/using-the-tools.mdmatch the closest workflows/recon-playbook.md section

Conflicts between loaded project instructions → formal docs in skills/code-recon/ win. This does not override harness-native skill name precedence.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,422. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.