Menu
Maintain the api/helpers/postgres.js SQL boundary, CRUD helper surface, and safe filter conventions.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Build or change API behavior in api/ using Express routers, middleware, CustomError, model instances, and camelCase JSON responses.
Review backend and frontend template code for real defects, boundary violations, security gaps, and missing tests. Auto-invoke for code reviews or bug investigations. Triggers: "bug review", "review code", "find bugs", "security audit", "check defects".
Implement OOP API entities in api/model/ using the shared Model base class and relation helper.
Update project-local agent guidance when architecture, workflows, commands, or conventions change. Auto-invoke when user or agent output indicates a reusable workflow or durable rule. Triggers: "update docs", "update skill", "create new skill", "update agent instructions", "document recurring pattern", "capture reusable workflow".
Add accurate JSDoc and focused comments when changing template code. Auto-invoke during code writing or refactoring. Triggers: "document code", "jsdoc", "code comments", "add comments", "explain logic".
Keep human docs, agent guidance, and touched code comments aligned with the real web/api implementation, compose workflow, and validation commands. Auto-invoke when auditing docs or after major architectural changes. Triggers: "audit docs", "check context", "documentation maintenance", "audit documentation", "verify docs".
| name | postgres-helper |
| description | Maintain the api/helpers/postgres.js SQL boundary, CRUD helper surface, and safe filter conventions. |
Use this skill when changing api/helpers/postgres.js or model persistence contracts.
api/helpers/postgres.js.find, findOne, get, insert, upsert, update, and delete."table") and $1, $2 parameter binding centralized.like, between, ne, lt, gt, lte, and gte.Run helper unit tests and at least one integration path when query behavior changes.