check-backend

Backend code quality review involves evaluating recent changes against established development guidelines. This skill inspects touched files in your git status, reads relevant guideline documents covering database and error handling, and produces actionable violation reports with remediation steps.

The backend guidelines covered during code review include database, error handling, logging, type-safety, and overall quality standards. The skill reads the Trellis backend index and consults relevant guideline files to evaluate compliance across these five areas.

You can automate backend code review by running the check-backend skill on your latest changes. It follows a deterministic workflow: inspect git status, read the Trellis backend index, consult relevant guideline files, assess compliance, and output violation reports with remediation steps.

Check-backend works with your existing project guidelines by reading the relevant guideline documents stored in your repository, including the Trellis backend index. It requires no external dependencies and scopes its analysis to files touched in your recent changes.

To fix backend code that doesn't follow quality standards, use the violation reports generated by the skill, which include concrete remediation steps and follow-up tasks. These actionable steps are aligned with your project's backend development guidelines to bring code back into compliance.

Backend code drifts from established guidelines when frequent changes are made without continuous compliance checks, risking bugs and maintenance challenges. Automated guideline-aware evaluation reduces these regressions by catching violations early before they accelerate into larger code review issues.