agentleFS
Sign inStart free
metagit-aimetagit-ai/metagit-cli/skills/metagit-repo-impact/SKILL.md

metagit-repo-impact

Skill4 starsChanged 14 days agoMITView on GitHub

Plan repository change impact before edits by combining metagit workspace context and graph-based dependency analysis. Use when a change may affect multiple repositories.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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:

    Use this skill before risky or cross-repo modifications.

    line 8
  2. Distinctive:

    Use metagit workspace context to bound repository scope.

    line 13
  3. Distinctive:

    Use graph impact tooling to estimate blast radius.

    line 14
  4. Distinctive:

    Do not execute mutating steps in this planning phase.

    line 35

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

Planning Repo Impact

Use this skill before risky or cross-repo modifications.

Workflow

  1. Identify target symbols/files for change.
  2. Use metagit workspace context to bound repository scope.
  3. Use graph impact tooling to estimate blast radius.
  4. Produce a change plan with test and rollback focus.

Commands

  • metagit workspace select --project <name>
  • MCP metagit_cross_project_dependencies with source_project and dependency_types before large cross-project edits
  • MCP metagit_project_context_switch to bound scope to one workspace project
  • npx gitnexus analyze on affected repos when graph_status is stale or missing
  • metagit gitnexus group sync -c .metagit.yml when cross-repo symbol impact is needed (after per-repo analyze)
  • npx gitnexus query / gitnexus impact for single-repo symbol analysis; gitnexus group impact for cross-index

Output Contract

Return:

  • impacted repositories and interfaces
  • highest-risk change points
  • minimum validation plan

Safety

  • Do not execute mutating steps in this planning phase.

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