skills.rest
Lin117-shygo
Lin117-shygoCOMMUNITY
Explore all skills by this author →
GitHub

check-backend

Validate modified backend code against guidelines in .trellis/spec/backend.

Updated Mar 6, 2026
Search Tags:#testing#backend#quality#guidelines#lint#code-review
One-click install
npx skills add https://github.com/Lin117-shygo/ros_car --skill check-backend-lin117-shygo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: check-backend
Source: https://github.com/Lin117-shygo/ros_car/tree/main/.agents/skills/check-backend
Command: npx skills add https://github.com/Lin117-shygo/ros_car --skill check-backend-lin117-shygo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams ensure that backend changes adhere to established guidelines, reducing introduction of bugs and non-compliant practices.

Core Features & Use Cases

  • Validate code against backend guidelines for changes related to databases, error handling, logging, and type safety.
  • Provide a structured review process that points out violations and suggests fixes.
  • Integrate into a CI-like flow where developers can quickly verify compliance before merging.

Quick Start

Run the check-backend flow on your latest commit to verify guideline compliance.

Frequently Asked Questions about check-backend

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

FAQPage Schema
How do I enforce backend coding guidelines for database changes and error handling?▼

You can validate backend code compliance by running this Skill on your latest commit. It identifies violations of guidelines for database changes, error handling, logging, and type safety, providing suggested fixes for any non-compliant code.

What is the best way to lint backend code for type-safety and logging compliance?▼

The best way to lint backend code for type-safety and logging compliance is to validate modifications against the .trellis/spec/backend guidelines. This Skill acts as a code review tool, catching non-compliant practices and suggesting fixes before merging.

Does this backend guideline checker work without external dependencies?▼

Yes, this backend guideline checker operates without external dependencies. It relies on the internal .trellis/spec/backend configuration to review modified code and ensure modifications follow established team guidelines.

Can I integrate backend code review into a CI-like flow before merging?▼

Yes, you can integrate this backend code review into a CI-like flow. It helps developers quickly verify guideline compliance on their latest commits, reducing the introduction of bugs and non-compliant practices before merging.

Why should I use an automated backend code review instead of manual checks?▼

Automated backend code review ensures changes consistently adhere to established guidelines, reducing bugs and non-compliant practices. Unlike manual checks, it provides a structured process that points out violations and suggests fixes quickly.

Related Skills

Explore More Software Engineering Skills→
Lin117-shygoLin117-shygo

before-backend-dev

Guide backend tasks by consulting guideline files for database, error handling, logging, and type-safety.

Community
Intermediate
peancharoenpeancharoen

speckit.reviewer

Review git diffs and file paths for code issues with severity labels.

Community
Intermediate
GoBeromsuGoBeromsu

verification-validator

Validate code changes with pytest, webpack, or Playwright tests based on change type.

Community
Intermediate
baphledbaphled
1

static-analysis

Guide static code analysis tools to detect bugs, vulnerabilities, and style violations.

Community
Intermediate