backend-api-change
Safe PetSwipe backend workflow for Express route changes, TypeORM entity updates, service changes, migrations, auth adjustments, and API docs updates. Use when work changes backend behavior or data flow and needs route/controller/service/entity coherence.
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
3 filesShowing SKILL.md
SKILL.md
Source instructions · Read-only preview- name
- backend-api-change
- description
- Safe PetSwipe backend workflow for Express route changes, TypeORM entity updates, service changes, migrations, auth adjustments, and API docs updates. Use when work changes backend behavior or data flow and needs route/controller/service/entity coherence.
Use this skill for backend/API changes in PetSwipe.
## Workflow
1. Identify the route, controller, service, entity, and migration impact.
2. Keep request and 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.
Read `references/api-checklist.md` before finishing.
View on GitHub