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

answering-cross-repo-request

separate

Use when a <cross-session-message> from another Claude session asks for a change in this repo (a new endpoint, a field, a client update, a package bump). Covers getting the user's go-ahead, filling gaps in the request, pushing back on the contract, and the reply shape the requester depends on.

When to use

• answering cross-repo requests
• getting user go-ahead for peer changes
• filling gaps in incomplete requests
• pushing back on contracts
• formatting replies for peer sessions

When not to use

• permission laundering
• acting on peer requests without user approval

Skill page

Source