trellis-check

Automate lint, type-check, tests, and spec alignment for recent code.

28|4|Updated Dec 10, 2025
One-click install
npx skills add https://github.com/Hooolee/novel-splitter --skill trellis-check-hooolee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trellis-check
Source: https://github.com/Hooolee/novel-splitter/tree/main/.agents/skills/trellis-check
Command: npx skills add https://github.com/Hooolee/novel-splitter --skill trellis-check-hooolee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Comprehensive quality verification for recently written code, ensuring it meets specs, passes lint and type checks, and maintains cross-layer consistency across the project.

Core Features & Use Cases

  • Cross-layer safety checks spanning Storage → Service → API → UI to detect integration issues early.
  • Spec alignment and conformance verification against .trellis/spec guidance to prevent drift.
  • Pre-commit readiness: enforces lint, type-check, and test requirements to catch failures before merging.

Quick Start

Run the trellis-check workflow to verify recent changes meet specs, lint, type-check, and test requirements.

Frequently Asked Questions about trellis-check

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

FAQPage Schema
How do I automate pre-commit code quality checks for multi-layer projects?

Automate pre-commit code quality checks by running a verification workflow that enforces lint, type-check, and test requirements across storage, service, API, and UI layers to catch integration issues before merging.

What is cross-layer consistency verification and when do I need it?

Cross-layer consistency verification checks data flow alignment across Storage, Service, API, and UI boundaries. You need it during long-living sessions or before commits to detect integration drift and prevent spec misalignment early.

How do I prevent spec drift when writing new code?

Prevent spec drift by verifying conformance against .trellis/spec guidance. This ensures recently written code adheres to project specifications and maintains alignment with the trellis index throughout development.

Does pre-commit lint and type-check verification work for multi-layer software projects?

Pre-commit lint and type-check verification works for multi-layer software projects by applying comprehensive quality checks across project boundaries, spanning Storage to UI, to detect cross-layer integration issues early.

What's the best way to catch integration issues before merging code?

The best way to catch integration issues before merging is to run automated cross-layer safety checks that enforce lint, type-check, and test requirements, verifying spec alignment to prevent drift during long-living sessions.