agentleFS
Sign inStart free
patricio0312revpatricio0312rev/workspaces/skills/workspace-affected/SKILL.md

workspace-affected

Skill9 starsChanged 10 months agoMITView on GitHub

Show dependency graph for a project - what depends on it and what it depends on. Use when user asks "what depends on X", "affected by changes", or "dependency graph".

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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:

    When the user wants to see affected projects:

    line 18
  2. Distinctive:

    Use the provided project name or detect from current directory.

    line 22
  3. Very specific:

    Read the ## Relationships section from WORKSPACE.md:

    line 26

≈ “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

Skill: Workspace Affected

Description

Show the dependency graph for a project - what depends on it and what it depends on. Useful for understanding the impact of changes.

Arguments

  • [project] - Project to analyze (defaults to current project)

Instructions

When the user wants to see affected projects:

Step 1: Identify Target Project

Use the provided project name or detect from current directory.

Step 2: Parse Relationships

Read the ## Relationships section from WORKSPACE.md:

## Relationships
- admin -> api (REST client, consumes /api/v1/*)
- homepage -> api (product catalog, consumes /api/v1/products)
- mobile -> api (REST client, consumes /api/v1/*)

Format: consumer -> provider (description)

Step 3: Build Dependency Graph

For the target project, identify:

  1. Dependents (what depends on this project)
  2. Dependencies (what this project depends on)

Step 4: Display Graph

🔗 Dependency graph for: api

Projects that depend on api (will be affected by changes):
  ├── admin (REST client, consumes /api/v1/*)
  ├── homepage (product catalog, consumes /api/v1/products)
  └── mobile (REST client, consumes /api/v1/*)

Projects that api depends on:
  └── (none)

Impact summary:
  • Changes to api may affect 3 projects
  • Consider running tests in: admin, homepage, mobile

Use Cases

  • Before making breaking changes: "I'm changing the API response format, what will break?"
  • Planning deployments: "What order should I deploy these changes?"
  • Understanding architecture: "How do these projects connect?"

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