backend-api-change
Workflow for safe PetSwipe backend/API changes across Express routes, controllers, services, entities, migrations, and API docs.
Source facts
- Repository
- hoangsonww/PetSwipe-Match-App
- Last source activity
- February 28, 2026 at 01:57
- Detected SKILL.md language
- English
- Stars
- 26
- Forks
- 12
Install options
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Review the source files
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
File Explorer
2 filesShowing SKILL.md
SKILL.md
Source instructions · Read-only preview- name
- backend-api-change
- description
- Workflow for safe PetSwipe backend/API changes across Express routes, controllers, services, entities, migrations, and API docs.
Use this skill for backend endpoint changes, auth changes, entity updates, migrations, and service-layer work.
## Workflow
1. Identify the route, controller, service, entity, and migration impact.
2. Keep request/response behavior explicit.
3. Check whether Swagger/OpenAPI exposure needs to change.
4. Check whether health/readiness or startup behavior is affected.
5. Validate with build/tests appropriate to the touched area.
## Repo-Specific Guidance
- `backend/src/app.ts` is the central runtime and docs surface.
- Health endpoints at `/health` and `/ready` matter for deployment.
- Swagger is exposed at `/api-docs.json` and `/docs`.
- Route/controller/service/entity drift is a common source of regressions.
If the task is deep or risky, use the `backend-api-specialist` subagent first.
@references/api-checklist.md
View on GitHub