- Home
- Skills
- APIs & Backend
- Cross-Repo Change Coordinator
More screenshots
Works with the AI Agents you already use
Cross-Repo Change Coordinator
Take one feature request and apply across the backend, web, and mobile repos
Free
Cross-Repo Change Coordinator
Example session with this skill installed
Add an optional phone number to the user profile
- Read your context and instructions
- Compiled the cross-repo change coordinator
Added an optional phone number to the profile across the backend, web, and mobile apps. The field accepts up to 30 characters; empty input clears it. Existing profiles are migrated to an empty value, and clients handle responses where the field is absent.
The backend OpenAPI contract and both generated client types are updated. The plan, including the contract checksum and release order, is in CHANGE_PLAN.md.
Classification
Class: additive optional Breaking for old clients: no; reads gain an optional response property and updates continue to accept requests that omit it.
Assumptions
API and storage property is phoneNumber, a free-form string capped at 30 characters; no format validation is imposed so international formats remain acceptable.
Existing rows are backfilled to an empty string; clients still handle an absent value for compatibility with older API responses and persisted mobile data.
Per repo guidance, use a feature branch in each repo. Existing untracked yarn.lock files are user data and remain untouched.
Repos
Role Path Branch
Backend demo-backend feat/profile-phone-number
Web demo-web feat/profile-phone-number
Mobile demo-mobile feat/profile-phone-number
Connects securely to your tools. The creator never sees your data.
About this skill
Take one feature request (for example, "add a new field to the user profile") and plan and apply the matching changes across the backend, web, and mobile repos. The skill:
- Read each repo's conventions before making changes.
- Generate the API contract once (DTOs and OpenAPI spec).
- Update the typed clients for web and mobile from that contract.
- Produce a checklist of migrations and the release order.
The skill infers conventions from the code and the most similar existing feature.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for APIs & Backend.
Requires local environment access to run build/test scripts. Does not perform git commits or deployments. Limited to repos present in the workspace.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
1 use
Times used to date
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed 26 days ago
- Free with an Agensi account
- Software
Git
Node.js
Permissions
File Scopes
This Skill needs access to the implementations to update the requirements