agentleFS
talayashtalayash/spring-fleet/skills/impact/SKILL.md

impact

Skill2 starsChanged 44 days agoMITView on GitHub

Find every consumer of a shared-lib symbol, file, or API across the fleet's service repos. Outputs an impact list with file:line citations.

16 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use docs.

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.
  • Microsoft AzureSkill

    docs

    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 16 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 (impact is the inverse of trace: you start from a shared symbol and fan *outward* through every …

    line 20
  2. Very specific:

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

    line 33

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

Compute the cross-fleet blast radius of a change.

Input: $ARGUMENTS: one of:

  • a symbol (class, method, function, constant) from a shared lib (e.g. OrderEntity, core-lib.util.RetryPolicy.retry)
  • a file path in a shared lib (e.g. core-lib/src/main/java/.../RetryPolicy.java)
  • a published API endpoint owned by a service (e.g. POST /payment-v1/charge)

Steps:

  1. Locate spring-fleet.config.json (cwd, else suggest /fleet-init). Read reposRoot, services, sharedLibs, and proxyLib; these constrain where consumers can live.
  2. Use the tracing-across-services skill (impact is the inverse of trace: you start from a shared symbol and fan outward through every consumer).
  3. Dispatch the impact-analyzer agent with the config path and $ARGUMENTS. It searches every service repo (and the proxy-lib, if any) for usages and returns a grouped impact list.
  4. Present a per-service consumer count plus the citation list. Highlight any service that calls the symbol in a hot path (controller, scheduler, event handler) and any consumer that touches a public API or persisted data shape; those carry the highest change cost.

Outside Claude Code

  • $ARGUMENTS is the text the user supplied with the request.
  • No plugin subagents (Codex): read agents/impact-analyzer.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.