domains / families / software-engineering / cross-repo-request

cross-repo-request

separate

Use when work in this repo depends on a change in a different repo that has its own running Claude session (frontend needing a backend endpoint, backend needing a client change, a shared package bump). Covers finding the peer session, what to put in the request so it needs no follow-ups, and how to handle the reply.

When to use

• frontend needing a backend endpoint
• backend needing a client change
• shared package bump
• finding the peer session
• structuring cross-repo requests
• handling peer replies

When not to use

• guessing the contract
• stubbing silently
• polling ListAgents in a loop
• sending 'are you done?'
• accepting or rejecting contract changes on the user's behalf
• asking a peer to run blocked actions

Skill page

Source