skills.rest
yizhitangtongxue
yizhitangtongxueCOMMUNITY
Explore all skills by this author →
GitHub

check-backend

Review recently written code against backend development guidelines and report violations.

Updated Mar 24, 2026
Search Tags:#git#code review#best practices#backend#guidelines#quality check
One-click install
npx skills add https://github.com/yizhitangtongxue/opencode-switch --skill check-backend-yizhitangtongxue
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: check-backend
Source: https://github.com/yizhitangtongxue/opencode-switch/tree/main/.agents/skills/check-backend
Command: npx skills add https://github.com/yizhitangtongxue/opencode-switch --skill check-backend-yizhitangtongxue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After writing backend code, it is easy to miss project-specific conventions around databases, error handling, logging, and type safety. This Skill checks your recent changes against the team's documented backend guidelines so violations are caught before review. ## Core Features & Use Cases - Change Detection: Runs git status to identify which files you just modified. - Guideline Mapping: Reads .trellis/spec/backend/index.md and loads only the guideline files relevant to your changes, such as database, error handling, logging, or type safety rules. - Violation Reporting: Reviews your code against the applicable guidelines, reports any violations, and fixes them when found. - Use Case: After adding a new database query and error handling logic to an API endpoint, run this Skill to verify the code follows the project's database and error-handling guidelines before committing. ## Quick Start Check the code I just wrote against the backend development guidelines and fix any violations.

Frequently Asked Questions about check-backend

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

FAQPage Schema
How do I check my code against backend development guidelines?▼

Run this Skill after making changes. It executes git status to find modified files, reads the guideline index at .trellis/spec/backend/index.md, then reviews your code against the relevant guideline documents and reports violations.

What backend guidelines does this code review cover?▼

It covers database guidelines, error handling, logging guidelines, type safety, and general quality guidelines. The Skill selects which documents to read based on what you changed, with quality guidelines applied to any change.

Does this Skill require a specific project structure?▼

Yes, it expects guideline files under .trellis/spec/backend/, including index.md and topic-specific files like database-guidelines.md and error-handling.md. It also requires a git repository so git status can identify modified files.

Can it fix guideline violations automatically?▼

Yes, after reviewing your code against the applicable guidelines, it reports any violations found and fixes them. You should verify the fixes before committing the changes.

When should I run a backend guideline check?▼

Run it right after writing or modifying backend code, before committing or opening a pull request. It works best when the .trellis guideline documents are kept up to date with team conventions.

Related Skills

Explore More Software Engineering Skills→
imbingoximbingox

trellis-spec-bootstarp

Automate creation and refresh of .trellis/spec guidelines from codebase.

Community
Advanced
netbox-communitynetbox-community
21.3k

run-tests

Run NetBox Django tests via manage.py with testing configuration.

Official
Intermediate
cyhinversecyhinverse

lint-and-validate

Run automated linters and type checkers on Node.js/TypeScript and Python repositories.

Community
Intermediate
w7panelw7panel
182

development-review

Run linting, type checking, and code formatting checks for development standards.

Official
Advanced