القائمة
Backend conventions for NestJS projects: modules, controllers, services, DTOs, migrations, structure. Use when implementing or reviewing code in NestJS backends.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Per-repo commit worker. Analyzes ALL changed files independently, groups them by ticket, and makes MULTIPLE focused commits — one per logical group. Spawned in parallel by /pwf-commit-changes (one instance per repo). Never create branches or push.
Commit uncommitted changes across all workspace repos and tag commits with ticket numbers. Each repo gets its own subagent that analyzes files individually, groups them by ticket, and makes multiple focused commits. Use when the user pastes issue text (with TICKET-XXX) and wants to commit, or says "commit with these tickets" / "commit my changes".
Deploy AWS Lambdas using the guaranteed deploy scripts only. Never deploy via IAC (CDK). Requires AWS SSO login first. Use when deploying any AWS Lambda repo.
Load and enforce mandatory project documentation baseline before implementation work.
Run standardized post-implementation documentation maintenance and quality checks.
Use when implementation is complete to close branch/worktree with a disciplined decision flow (merge, PR, keep, discard) plus cleanup.
استنادا إلى تصنيف SOC المهني
| name | nestjs-conventions |
| description | Backend conventions for NestJS projects: modules, controllers, services, DTOs, migrations, structure. Use when implementing or reviewing code in NestJS backends. |
When working in backend/ (or NestJS app root), follow these conventions:
*.module.ts, *.controller.ts, *.service.ts, entities, dto/. No business logic in controllers.npm run typeorm:generate -- src/database/migrations/DescriptiveName. Entities drive schema.Reference project rules and structure docs for full details.