agentleFS
Sign inStart free
voyager67voyager67/AgentFieldkit/skills/repo-scout/SKILL.md

repo-scout

Skill0 starsChanged 14 days agoMITView on GitHub

Map an unfamiliar codebase before changing it. Use when joining a repository, debugging an unclear subsystem, or planning work that depends on understanding project structure.

7 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ecosystem-reference, fractal-delegation 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.
  • naman10parikhSkill

    ecosystem-reference

    Quick-access directory of Claude Code ecosystem repos, skills, plugins, MCPs, and patterns. Use when improving the harness.

    Also in 5 projects that use this

  • naman10parikhSkill

    fractal-delegation

    Also in 5 projects that use this

  • KirchliveSkill

    skill-routing

    Decides which of the installed skills a task needs and loads them before the work starts. This skill should be used at the beginning of any multi-step task — build, fix, refactor, migrate, review, plan, release, research, write, design, video — and again at every phase change, after context compaction, and when work moves into a different part of the codebase. Use it for requests like "let's build X", "fix this bug", "refactor Y", "plan the migration", "review this", and also when the user asks which skill applies, why a skill did not fire, or asks to check what is available.

    Also in 5 projects that use this

  • sublimotionSkill

    agent-runtime

    Launch and manage detached agent runs on EKS via the agent-runner CLI. Use when the user says "launch an agent run", "agent runtime", "agent-runner", "run this spec on the cluster", "check run status", "agent run logs", or "stop a run". Do NOT use for writing the agent-runner code itself (edit the sibling ../agent-runner repo), Terraform of the foundation (use terraform-automation), or GPU serving deployments (use infra-deployer).

    Also in 5 projects that use this

  • BenjaminGSkill

    harness-review

    Turn one PR's review comments into harness fixes — classify each cause by the most solid place it can live (codebase, lint, rules, skill), then draft the fixes in a separate PR.

    Also in 5 projects that use this

  • botirkhaltaevSkill

    design-systems

    Build and maintain scalable design systems: design tokens, component libraries, naming conventions, governance, and design-to-code pipelines. Covers Figma variables, token architecture, atomic design, component APIs, versioning, and team workflows. Use when creating a design system, scaling an existing one, or establishing design-engineering alignment. Triggers on: "design system", "design tokens", "component library", "token naming", "Figma variables", "atomic design", "design ops", "design-to-code".

    Also in 5 projects that use this

  • +6 more from naman10parikh

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 4

    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:

    Read the project entry points first: README, package or build manifests, contribution guidance, agent instructions, CI workflows, and test …

    line 13
  2. Distinctive:

    Read-only by default. Do not edit files, install packages, run migrations, or access production systems during reconnaissance.

    line 28
  3. Distinctive:

    Do not print secrets. If a credential file appears, report its path and stop inspecting its contents.

    line 29
  4. Distinctive:

    Keep the map concise enough to be useful in a later session.

    line 30

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

Repo Scout

Outcome

Produce a short, evidence-backed map of the repository that helps the next task start in the right place without making changes.

Procedure

  1. Read the project entry points first: README, package or build manifests, contribution guidance, agent instructions, CI workflows, and test configuration.
  2. Inspect the top-level tree, then follow imports and scripts from the likely application entry point. Avoid dumping huge directories or generated files.
  3. Identify the main runtime, important modules, public interfaces, configuration sources, data stores, test commands, lint/type-check commands, and build/deploy paths.
  4. Trace one representative request or execution path end-to-end. Cite concrete paths and symbols, not guesses.
  5. Note conventions that already exist: error handling, logging, dependency injection, naming, test fixtures, and architectural boundaries.
  6. List unknowns separately from findings. Never infer that a feature exists merely because its name appears in documentation.

Deliverable

Return:

  • System map: entry points and key directories.
  • Change hotspots: likely files for the user's task, with reasons.
  • Verification commands: exact commands discovered in project files.
  • Constraints and unknowns: risks, missing docs, unverified assumptions.

Boundaries

  • Read-only by default. Do not edit files, install packages, run migrations, or access production systems during reconnaissance.
  • Do not print secrets. If a credential file appears, report its path and stop inspecting its contents.
  • Keep the map concise enough to be useful in a later session.

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.

Check your setup, free