check-backend

Backend code review checks your `git status` changes against predefined documentation in `.trellis/spec/backend/`. It enforces development standards for database management, error handling, logging, and type safety to ensure maintainability.

To check database schema changes, execute `git status` to capture the modifications and review them against the project's backend database guidelines. This verifies that your new schema implementation complies with established standards.

Backend code review enforces development standards covering database management, error handling, logging, and type safety. It validates modifications by comparing `git status` output against guideline documents in `.trellis/spec/backend/`.

Yes, you need git to review backend code quality because the process requires analyzing `git status` output to identify recent changes. These changes are then compared against predefined backend development guidelines for validation.

You need to run a backend code quality check after implementing new features or modifying existing code, such as adding a database schema. It verifies that your recent changes comply with established project guidelines before integration.