trellis-check

Name: trellis-check
Availability: InStock
Author: tecnb

Run lint, type-check, tests, and cross-layer data-flow validation on code changes.

2|Updated Apr 8, 2026

Search Tags:#code-quality #lint #spec-compliance #tests #type-check #code-reuse #cross-layer

Ready to run

npx skills add https://github.com/TECNB/MediaNexus --skill trellis-check-tecnb

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: trellis-check
Source: https://github.com/TECNB/MediaNexus/tree/main/.agents/skills/trellis-check
Command: npx skills add https://github.com/TECNB/MediaNexus --skill trellis-check-tecnb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Comprehensive quality verification for recently written code. It ensures spec compliance, lint, type-check, tests, cross-layer data flow validation, code reuse checks, and consistency verification to prevent drift.

Core Features & Use Cases

Spec compliance checks against project specifications before merging
Linting, type-checking, and test execution as a unified quality gate
Cross-layer data-flow validation and consistency checks across UI, API, and service layers
Guidance to update specs when gaps are found during development or reviews

Quick Start

Run trellis-check on your codebase to perform lint, type-check, tests, and cross-layer quality 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 code quality checks before a commit?▼

To run code quality checks before a commit, execute lint, type-check, and tests across your codebase. This validates cross-layer data flow and ensures spec compliance to prevent drift before merging changes.

What is cross-layer data-flow validation in code reviews?▼

Cross-layer data-flow validation checks consistency across UI, API, and service layers during code reviews. It ensures data structures align correctly between different architectural layers before changes are committed.

How do I ensure spec compliance for recent code changes?▼

To ensure spec compliance for recent code changes, verify your code against project specifications and run automated quality gates. You should also update specs when gaps are found during iterative development.

Can I check for code reuse and consistency across different packages?▼

Yes, you can check for code reuse and consistency across different packages. The quality verification process identifies redundant logic and validates data flow across multiple architectural layers before commits.

What is the best way to prevent spec drift during iterative development?▼

The best way to prevent spec drift during iterative development is to apply unified quality gates that enforce spec compliance, linting, type-checking, and tests, while providing guidance to update specifications when gaps are discovered.