AgentSkillsCN

cross-repo-impact

了解当一个 Phoenix 仓库发生变更时，其他相关仓库是否也需要相应调整。适用于用户询问跨仓库依赖关系、需要更新哪些其他仓库、进行影响分析，或在对 Engine-Backend-Interface 边界产生影响的变更时使用。

SKILL.md
--- frontmatter
name: cross-repo-impact
description: 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

RepoRoleVisibility
EngineThe Body — Godot fork, UI shell, local tool executorsPublic
Interface (this repo)The Nervous System — versioned API contracts, typed SDKPublic
BackendThe Brain — orchestration, prompts, model routingPrivate

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

Changes in THIS repo (Interface)

What changed in InterfaceEngine impactBackend impact
Updated fixture JSONUpdate adapter to match new shapeUpdate golden test expectations
Added new SDK methodEngine can now call new endpointNone (Backend already has it)
New transport error typeHandle in MCP clientNone
Breaking change (v2 namespace)Update SDK integration for v2Implement v2 route handler
Validator schema changeNone (Engine uses SDK types)Verify response still validates

Changes in Engine that affect Interface

What changed in EngineInterface response needed
Shadow Tree format changeUpdate delta contract types/fixtures if needed
New data sent to backendMay need new contract fixture

Changes in Backend that affect Interface

What changed in BackendInterface response needed
New API response fieldUpdate fixture JSON + SDK types + validators
New endpointAdd fixture + SDK method + types + tests
Breaking schema changeCreate 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

  1. •Identify affected repos using the impact matrix
  2. •Get the canonical schema from Backend's api/schemas/
  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 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