| name | apihub-backend-developer |
| description | Implements and modifies the APIHub Go backend (qubership-apihub-service): controllers, services, repositories, entities, migrations, Service.go wiring, ErrorCodes, and OpenAPI specs. Use when adding or changing backend features, REST endpoints, SQL migrations, repository queries, or Go code in qubership-apihub-backend. |
APIHub Backend Developer
Follow apihub-go-developer first — this skill adds backend-specific rules for qubership-apihub-backend only.
Follow AGENTS.md and project rules. For examples and doc routing, see reference.md.
Backend-specific workflow
- Errors — new API error codes/messages as constants in
exception/ErrorCodes.go.
- Wiring — new repos/services/controllers at the end of their section in
Service.go; log.Fatalf for fatal startup wiring errors.
- Migrations — files in
qubership-apihub-service/resources/migrations/; run validation script (below).
- OpenAPI — update
docs/api/*.yaml per the file list in deployed rules.
- Related repos — before finishing, apply
apihub-deployment-followup and
postman-e2e-followup skills when the change may affect deployment or E2E tests
(installed from sibling repositories via APM).
- End-to-end verification — for changes with observable HTTP behavior, apply the
advanced-verification skill to build, run, and verify the change locally with a
Postman/Newman collection under tests/api/ before finishing.
Migration validation
After adding or renaming migration files, from the repository root:
Linux / WSL / Git Bash:
bash .cursor/skills/apihub-backend-developer/scripts/check_migration_numbers.sh
Windows PowerShell (native):
powershell -File .cursor/skills/apihub-backend-developer/scripts/check_migration_numbers.ps1
Fix any reported duplicate numbers before finishing.
Completion checklist (backend additions)
In addition to the apihub-go-developer checklist:
Suggest invoking apihub-backend-self-review in a new chat or with a different model for an independent pass over the diff.
