trellis-check

Verify code changes against Trellis task artifacts and spec guidelines.

92|8|Updated May 15, 2026
One-click install
npx skills add https://github.com/LonelyHerbivore/Trellis-Herbivore --skill trellis-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trellis-check
Source: https://github.com/LonelyHerbivore/Trellis-Herbivore/tree/main/.cursor/skills/trellis-check
Command: npx skills add https://github.com/LonelyHerbivore/Trellis-Herbivore --skill trellis-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It prevents context drift and quality regressions by verifying that newly written code matches the task artifacts and Trellis specs before you commit or merge.

Core Features & Use Cases

  • Spec compliance verification: Enforces guidance from .trellis/spec/<package>/<layer>/index.md and related guideline files.
  • Project-grade checks: Runs lint, type-check, and tests, then fixes failures before continuing.
  • Cross-layer consistency checks: Validates data flow, dependency correctness, and type/schema integrity when changes span multiple layers.
  • Maintainability and reuse validation: Checks for debug logging, unsafe bypasses, and whether similar logic should be reused or extracted.

Quick Start

Use trellis-check when you have finished implementing code for the current task and want to confirm it still passes the repository’s quality gates and spec requirements.

Frequently Asked Questions about trellis-check

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

FAQPage Schema
How do I verify code quality and spec compliance before a merge?

Spec compliance verification inspects recent code diffs against Trellis task artifacts and per-package quality guidelines. It catches lint, type-check, and test failures while validating cross-layer data flow and code reuse to prevent context drift before merging.

How do I check cross-layer data flow and dependencies in a multi-layer codebase?

Cross-layer validation inspects diffs and status changes to verify dependency correctness, type integrity, and data flow across multiple layers. It enforces spec guidelines to catch inconsistencies and ensure changes comply with architectural boundaries before merge.

How do I automate fixing lint and type-check failures during implementation?

Project-grade checks run lint, type-check, and tests, then automatically apply fixes to resolve failures before continuing. The process iteratively inspects diffs and reruns checks until the code passes all repository quality gates and spec requirements.

Can I use spec compliance checks to prevent debug logging and unsafe bypasses?

Yes, spec compliance checks validate maintainability by detecting debug logging, unsafe bypasses, and duplicate logic. It reviews code against spec guidelines to enforce proper reuse and extraction, ensuring new implementations match task artifacts before commit.

When should I run spec compliance and quality checks in my workflow?

Run spec compliance checks during implementation after finishing code for a task, before commit or merge. This timing catches context drift and quality regressions early by verifying recent changes against task artifacts and repository quality gates.