agentleFS
lza6lza6/claw-code-tingfeng/skills/deepsearch/SKILL.md

deepsearch

Skill5 starsChanged 12 days agoMITView on GitHub

Thorough codebase search

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Search for exact matches

    line 17
  2. Distinctive:

    Search for related terms and variations

    line 18
  3. Distinctive:

    Check common locations (components, utils, services, hooks)

    line 19
  4. Distinctive:

    Read files with matches

    line 22
  5. Distinctive:

    Check imports/exports to find connections

    line 23
  6. Distinctive:

    Follow the trail (what imports this?

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Deep Search Mode

[DEEPSEARCH MODE ACTIVATED]

Objective

Perform thorough search of the codebase for the specified query, pattern, or concept.

Search Strategy

  1. Broad Search
    • Search for exact matches
    • Search for related terms and variations
    • Check common locations (components, utils, services, hooks)
  2. Deep Dive
    • Read files with matches
    • Check imports/exports to find connections
    • Follow the trail (what imports this? what does this import?)
  3. Synthesize
    • Map out where the concept is used
    • Identify the main implementation
    • Note related functionality

Output Format

  • Primary Locations (main implementations)
  • Related Files (dependencies, consumers)
  • Usage Patterns (how it's used across the codebase)
  • Key Insights (patterns, conventions, gotchas)

Focus on being comprehensive but concise. Cite file paths and line numbers.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.