How do I install the Cross Repo Impact skill?

Run npx skillmds@latest add rivie13-phoenix-agentic-engine-interface/cross-repo-impact in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Cross Repo Impact safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cross Repo Impact?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cross Repo Impact free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Cross Repo Impact?

rivie13 (@rivie13-phoenix-agentic-engine-interface) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cross Repo Impact by rivie13-phoenix-agentic-engine-interface

Name: Cross Repo Impact
Rating: 4.5 (4 reviews)
Author: rivie13

Cross Repo Impact

Understand when a change in one Phoenix repo requires changes in the other repos. Use when user asks about cross-repo dependencies, what other repos need updating, impact analysis, or when making changes that affect the Engine-Backend-Interface boundary.

rivie13 Updated Sep 10, 2026

File contents

Cross-Repo Impact Analysis — Phoenix Agentic Engine Interface

Three-Repo Model

Repo	Role	Visibility
Engine	The Body — Godot fork, UI shell, local tool executors	Public
Interface (this repo)	The Nervous System — versioned API contracts, typed SDK	Public
Backend	The Brain — orchestration, prompts, model routing	Private

Impact matrix: "If I change X, what else needs updating?"

Changes in THIS repo (Interface)

What changed in Interface	Engine impact	Backend impact
Updated fixture JSON	Update adapter to match new shape	Update golden test expectations
Added new SDK method	Engine can now call new endpoint	None (Backend already has it)
New transport error type	Handle in MCP client	None
Breaking change (v2 namespace)	Update SDK integration for v2	Implement v2 route handler
Validator schema change	None (Engine uses SDK types)	Verify response still validates

Changes in Engine that affect Interface

What changed in Engine	Interface response needed
Shadow Tree format change	Update delta contract types/fixtures if needed
New data sent to backend	May need new contract fixture

Changes in Backend that affect Interface

What changed in Backend	Interface response needed
New API response field	Update fixture JSON + SDK types + validators
New endpoint	Add fixture + SDK method + types + tests
Breaking schema change	Create `contracts/v2/` namespace

The Golden Rule

If it makes us money or makes us unique, it lives in the Backend. If it enables the community to contribute, it lives in the Engine. If it defines the contract between them, it lives here (Interface).

Checklist for cross-repo changes

Identify affected repos using the impact matrix
Get the canonical payload mirror from Backend's contracts/fixtures/v1/
Update fixtures in contracts/v1/
Update types in sdk/client/types.ts
Update validators in sdk/validators/
Run npm test and npm run typecheck
Coordinate with Engine and Backend PRs

What must NOT be in this repo

Even during cross-repo changes, never add:

System prompts or prompt templates
Orchestration logic or agent coordination
Model routing or selection intelligence
UI/UX code
Credentials or secrets

---name: cross-repo-impactdescription: Understand when a change in one Phoenix repo requires changes in the other repos. Use when user asks about cross-repo dependencies, what other repos need updating, impact analysis, or when making changes that affect the Engine-Backend-Interface boundary.---# Cross-Repo Impact Analysis — Phoenix Agentic Engine Interface## Three-Repo Model| Repo | Role | Visibility ||------|------|------------|| **Engine** | The Body — Godot fork, UI shell, local tool executors | Public || **Interface** (this repo) | The Nervous System — versioned API contracts, typed SDK | Public || **Backend** | The Brain — orchestration, prompts, model routing | Private |## Impact matrix: "If I change X, what else needs updating?"### Changes in THIS repo (Interface)| What changed in Interface | Engine impact | Backend impact ||--------------------------|--------------|----------------|| Updated fixture JSON | Update adapter to match new shape | Update golden test expectations || Added new SDK method | Engine can now call new endpoint | None (Backend already has it) || New transport error type | Handle in MCP client | None || Breaking change (v2 namespace) | Update SDK integration for v2 | Implement v2 route handler || Validator schema change | None (Engine uses SDK types) | Verify response still validates |### Changes in Engine that affect Interface| What changed in Engine | Interface response needed ||----------------------|--------------------------|| Shadow Tree format change | Update delta contract types/fixtures if needed || New data sent to backend | May need new contract fixture |### Changes in Backend that affect Interface| What changed in Backend | Interface response needed ||------------------------|--------------------------|| New API response field | Update fixture JSON + SDK types + validators || New endpoint | Add fixture + SDK method + types + tests || Breaking schema change | Create `contracts/v2/` namespace |## The Golden Rule> **If it makes us money or makes us unique, it lives in the Backend.**> **If it enables the community to contribute, it lives in the Engine.**> **If it defines the contract between them, it lives here (Interface).**## Checklist for cross-repo changes1. Identify affected repos using the impact matrix2. Get the canonical payload mirror from Backend's `contracts/fixtures/v1/`3. Update fixtures in `contracts/v1/`4. Update types in `sdk/client/types.ts`5. Update validators in `sdk/validators/`6. Run `npm test` and `npm run typecheck`7. Coordinate with Engine and Backend PRs## What must NOT be in this repoEven during cross-repo changes, never add:- System prompts or prompt templates- Orchestration logic or agent coordination- Model routing or selection intelligence- UI/UX code- Credentials or secrets

Frequently asked questions