check-backend

Inspect modified backend files against repository guidelines and report violations.

2|Updated Jan 30, 2026

Search Tags:#type safety #quality assurance #code review #backend #guidelines #git status

Ready to run

npx skills add https://github.com/LinXueyuanStdio/viben --skill check-backend-linxueyuanstdio

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: check-backend
Source: https://github.com/LinXueyuanStdio/viben/tree/main/packages/core/templates/codex/skills/check-backend
Command: npx skills add https://github.com/LinXueyuanStdio/viben --skill check-backend-linxueyuanstdio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you catch backend issues early by verifying your recently changed code against the repository’s backend development guidelines, reducing the risk of inconsistent quality, unsafe patterns, and maintainability problems.

Core Features & Use Cases

Guideline-aware review: Verifies your changes against the appropriate backend spec documents.
Change-driven checks: Selects specific guideline areas based on what you modified (e.g., database, error handling, logging, type safety).
Actionable fixes: Reports violations and instructs how to correct them before you proceed.

Quick Start

Run the check-backend skill after your backend changes, so it inspects modified files and validates them against the relevant documents under docs/specs/backend/.

Frequently Asked Questions about check-backend

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

FAQPage Schema

How do I check if my backend code changes follow project guidelines?▼

Backend code review for guideline compliance works by inspecting git status for modified files, reading the backend spec index, validating changes against relevant docs, and reporting violations with actionable fix prompts.

What backend development guidelines can be verified against modified code?▼

Verifiable backend development guidelines cover database updates, error handling, logging adjustments, and type-safety modifications, selected dynamically based on the actual files modified in the live repository.

How does change-driven code review select which backend specs to check?▼

Change-driven code review selects backend spec areas by inspecting git status for modified files, then matching those changes to relevant guideline documents under docs/specs/backend/ for targeted violation reporting.

Do I need a live git repository to run backend guideline checks?▼

A live git repository is required to run backend guideline checks, because the process depends on inspecting git status and reading actual modified files from the working repository to validate against specs.

What is the best way to enforce type safety and quality assurance in backend code?▼

To enforce type safety and quality assurance in backend code, run change-driven checks that inspect modified files against backend specification documents under docs/specs/backend/, reporting violations and prompting fixes before proceeding.

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

Automated backend guideline checks reduce risks of inconsistent quality, unsafe patterns, and maintainability problems by verifying recently changed code against the repository's backend development guidelines and prompting fixes.