trellis-check

Run spec compliance, lint, type-check, and test suites on new changes.

52|7|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/RebornQ/fl_api_hub --skill trellis-check-rebornq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trellis-check
Source: https://github.com/RebornQ/fl_api_hub/tree/main/.cursor/skills/trellis-check
Command: npx skills add https://github.com/RebornQ/fl_api_hub --skill trellis-check-rebornq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Comprehensive quality verification for recently written code by combining spec compliance, lint, type-check, and tests into a single quality gate before commits, reducing drift and rework.

Core Features & Use Cases

  • Spec compliance verification across changed code to ensure alignment with task artifacts.
  • Cross-layer safety checks that validate data flow and consistency between storage, service, and UI layers.
  • Pre-commit checks that run linting, type checking, and tests to catch issues early.
  • Use Case: A developer introduces a change and wants an automatic guarantee that it respects specs, passes validations, and won't break downstream components.

Quick Start

Run the trellis-check workflow on your recent changes to verify spec compliance, cross-layer safety, and pre-commit checks.

Frequently Asked Questions about trellis-check

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

FAQPage Schema
How do I run pre-commit checks for linting, type checking, and tests together?

Run pre-commit checks by executing the unified workflow on recent changes to perform linting, type checking, and tests together. This quality gate catches issues early and prevents regressions before commits.

What is cross-layer safety validation in code reviews?

Cross-layer safety validation verifies data flow and consistency between storage, service, and UI layers. It ensures that changes introduced in one layer do not break downstream components or cause regressions.

Can I enforce spec compliance automatically before a git commit?

You can enforce spec compliance automatically by running the pre-commit workflow on changed code. It verifies alignment with task artifacts to reduce drift and ensure new changes respect the defined specifications.

How do I prevent code drift and regressions during development?

Prevent code drift and regressions by integrating spec compliance, lint, type-check, and test suites into a single pre-commit workflow. This comprehensive quality gate verifies consistency before changes are committed.

Does pre-commit code quality checking work for cross-layer data flow validation?

Pre-commit code quality checking does include cross-layer data flow validation. It checks that data flow and consistency remain intact across storage, service, and UI layers before new changes are committed.

What is the best way to automate spec compliance checks for recent code changes?

The best way to automate spec compliance is to use a unified pre-commit workflow that verifies changed code against task artifacts. This ensures alignment, reduces manual rework, and catches drift early.