before-backend-dev

To ensure backend development guidelines are reviewed before coding, you can use a pre-commit check skill that provides a checklist for coding standards and patterns. It directs developers to relevant guideline files based on the specific backend task type.

Backend tasks requiring a development guidelines review include database work, error handling, logging, and type safety. Reviewing these areas before coding ensures adherence to established coding standards and enhances overall code consistency.

To check coding standards for a specific backend task, run the guideline review process which directs you to relevant guideline files based on task type. This ensures targeted compliance with your team's development patterns.

You need a pre-commit check for backend code quality to promote consistency across your development team. It reviews essential development guidelines before coding begins, preventing standard violations early in the task lifecycle.

Yes, you can use this for database work and error handling guidelines. The skill is applicable to various backend tasks, directing developers to relevant guideline files to ensure proper type safety and logging standards.