agentleFS
kauffjkauffj/agent-config/skills/explore/SKILL.md

explore

Skill8 starsChanged 3 months agoMITView on GitHub

Deep codebase research in isolated context — investigate a question thoroughly without cluttering the main conversation

67 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agent-context-isolation, agentica-infrastructure 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.

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 58 edited versions we read keep these.

  • 1

    Distinctive

    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:

    Treat the text supplied with the invocation as the question.

    line 15

“Common” is measured: kept by at least 6 in 10 of the 58 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.

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

Deep Codebase Exploration

Delegate the investigation to an available exploration subagent so its working context stays isolated. If this skill is already running in such a subagent, continue there. If delegation is unavailable, investigate in the current context and report that limitation.

Be thorough — check multiple files, trace call chains, read tests, and look at git history when relevant.

Treat the text supplied with the invocation as the question.

Approach

  1. Understand the question — what specifically needs to be answered?
  2. Find entry points — search for relevant files, functions, types, routes
  3. Trace the chain — follow imports, function calls, data flow
  4. Check edges — look at tests, error handling, edge cases
  5. Check history — if relevant, look at recent git commits touching these areas

Output

Structure your findings as:

Answer

Direct answer to the question in 2-3 sentences.

Evidence

  • File references with line numbers
  • Code snippets that prove your answer
  • Data flow diagrams if relevant (text-based)

Related

Anything surprising or noteworthy you found along the way that the user should know about, even if they didn't ask.

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.