Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
patricio0312rev avatar

Workspace Affected

  • 1 installs
  • 9 repo stars
  • Updated January 25, 2026
  • patricio0312rev/workspaces

Shows the dependency graph for a workspace project - what depends on it and what it depends on - by parsing WORKSPACE.md relationships.

About

Builds a dependency graph for a project in the workspace, showing dependents and dependencies from the WORKSPACE.md Relationships section. A developer uses it when assessing the impact of changes across a multi-repo workspace.

  • Parses consumer -> provider relationships from WORKSPACE.md
  • Reports dependents and dependencies for a target project

Workspace Affected by the numbers

  • 1 all-time installs (skills.sh)
  • Ranked #2,476 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/patricio0312rev/workspaces --skill workspace-affected

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1
repo stars9
Last updatedJanuary 25, 2026
Repositorypatricio0312rev/workspaces

What it does

Shows the dependency graph for a workspace project - what depends on it and what it depends on - by parsing WORKSPACE.md relationships.

Files

SKILL.mdMarkdownGitHub ↗

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?"

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.