agentleFS
Sign inStart free
talayashtalayash/spring-fleet/skills/trace/SKILL.md

trace

Skill2 starsChanged 44 days agoMITView on GitHub

Trace how an endpoint or feature flows across the fleet's service repos and shared libraries, with file:line citations.

27 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ai-slop-cleaner, ralplan 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.
  • Jurel89Skill

    ai-slop-cleaner

    Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode

    Also in 4 projects that use this

  • ibahgatSkill

    ralplan

    Create a strict, quality-first execution plan with explicit gates and rollback-ready sequencing.

    Also in 4 projects that use this

  • woosikkimSkill

    deepinit

    Generate hierarchical AGENTS.md codebase maps for agent context

    Also in 3 projects that use this

  • klauswgSkill

    deep-interview

    在明确批准执行之前，通过数学化歧义门控进行苏格拉底式深度访谈

    Also in 4 projects that use this

  • AWSSkill

    map

    Map verified service capabilities against customer-provided control framework and threat model. Produces mapping-results.json, controls-catalog.md, and framework-mapping.md. Supports pluggable frameworks: CCMv4, NIST 800-53, CIS Benchmarks, ISO 27001, etc. Split into 4 focused sub-skills for better accuracy; this skill orchestrates them.

    Also in 4 projects that use this

  • buddyhSkill

    deep-dive

    Deep dive on any topic. Decomposes into subtopics, researches each in parallel with thorough source gathering, then synthesizes into a comprehensive report (4,000-10,000+ words, 40-100+ sources). Scales depth dynamically based on topic complexity. Use when asked for a deep dive, deep research, comprehensive analysis, or thorough investigation of a topic.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 23 edited versions we read keep these.

  • 1

    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
  1. Distinctive:

    Use the tracing-across-services skill.

    line 15
  2. Very specific:

    No plugin subagents (Codex): read agents/fleet-explorer.md under the plugin root (two directories above this SKILL.md) and do that work …

    line 25

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

Trace a flow across the Spring Boot fleet.

Input: $ARGUMENTS: an endpoint (POST /order-v1/reserve), a controller, or a feature name.

Steps:

  1. Locate spring-fleet.config.json (cwd, else suggest /fleet-init).
  2. Use the tracing-across-services skill.
  3. Dispatch the fleet-explorer agent with the config path and $ARGUMENTS to produce the ordered call chain across repos, following proxy-lib hops and noting shared-lib code touched.
  4. Present the chain entry → … → leaf, each step cited repo/File.java:line, plus a short summary of participating services and shared-lib modules.

Outside Claude Code

  • $ARGUMENTS is the text the user supplied with the request.
  • No plugin subagents (Codex): read agents/fleet-explorer.md under the plugin root (two directories above this SKILL.md) and do that work yourself instead of dispatching.

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