check-backend

Check backend code changes against repository guidelines for violations.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/MaShouo/CodexAuthExchange --skill check-backend-mashouo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-backend
Source: https://github.com/MaShouo/CodexAuthExchange/tree/main/.agents/skills/check-backend
Command: npx skills add https://github.com/MaShouo/CodexAuthExchange --skill check-backend-mashouo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensure backend changes comply with established guidelines to improve reliability and maintainability.

Core Features & Use Cases

  • Guideline alignment checks: Verifies changes against the backend guidelines in the repository, including database changes, error handling, logging, type-safety, and overall quality.
  • Guided review workflow: Provides a structured checklist and actionable steps to review modifications before merging.
  • Use Case: During a code review, run the check-backend skill to surface violations and generate compliant remediation steps.

Quick Start

Analyze the latest code changes in your feature branch and run the backend guidelines check to surface any violations and recommended fixes.

Frequently Asked Questions about check-backend

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check backend code changes against repository guidelines during a code review?

To check backend code changes, you analyze feature branch modifications and verify alignment with established guidelines, surfacing violations in database changes, error handling, logging, and type-safety to generate compliant remediation steps.

What backend quality guidelines are typically enforced in automated code reviews?

Backend quality guidelines enforced in code reviews cover database changes, error handling, logging, type-safety, and overall code reliability. Verifying alignment with these guidelines ensures backend changes meet maintainability standards before merging.

How do I enforce type-safety and error handling compliance before merging backend modifications?

You enforce type-safety and error handling compliance by running a backend guidelines check that reads repository specs and surfaces violations. This provides a structured checklist and actionable remediation steps for non-compliant modifications.

Does this backend code review check require specific configuration files in the repository?

Yes, the backend code review check requires configuration files. It reads the repository's established backend guidelines located in the `.trellis/spec/backend` directory to enforce compliance across relevant code changes.

What is the best way to automate linting for database changes in a backend feature branch?

The best way to automate linting for database changes is to run a backend check skill that identifies code modifications and verifies alignment with repository guidelines, automatically surfacing violations related to database schema or query changes.