trellis-check

Coordinate linting, type-checking, and tests against project specifications.

Updated Apr 30, 2026

Search Tags:#code quality #testing #architecture #linting #refactoring #compliance

Ready to run

npx skills add https://github.com/znc15/Open-Design --skill trellis-check-znc15

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: trellis-check
Source: https://github.com/znc15/Open-Design/tree/main/.cursor/skills/trellis-check
Command: npx skills add https://github.com/znc15/Open-Design --skill trellis-check-znc15

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of maintaining code quality and architectural integrity during development by automating verification across specs, tests, and data layers.

Core Features & Use Cases

Comprehensive Verification: Validates code against project specs, linting, type-checking, and unit tests.
Cross-Layer Consistency: Ensures data flow and schema integrity across storage, service, API, and UI layers.
Use Case: Before committing a major feature, use this Skill to verify that your new code adheres to existing design patterns and does not introduce regressions or circular dependencies.

Quick Start

Run the trellis-check skill to perform a full quality verification on the current codebase changes.

Frequently Asked Questions about trellis-check

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

FAQPage Schema

How do I automate cross-layer consistency checks before committing code?▼

Cross-layer consistency checks validate data flow and schema integrity across storage, service, API, and UI layers. You can automate this by running comprehensive verification scripts that enforce architectural specifications before a commit.

Why does context drift happen during long development sessions and how do I prevent it?▼

Context drift occurs when long sessions cause code to deviate from established design patterns. Prevent it by applying automated architectural verification that enforces project specs, linting, and type-checking against baseline conventions.

What is the best way to run pre-commit linting and type-checking against project-specific specs?▼

Pre-commit linting and type-checking against project specs is executed by coordinating static analysis tools with unit tests. This verifies new code adheres to existing design patterns and prevents regressions or circular dependencies.

Can I validate architectural compliance and data flow across multiple application layers automatically?▼

Yes, architectural compliance and data flow validation can be automated. Comprehensive quality verification coordinates linting, type-checking, and test execution to ensure schema integrity across storage, service, API, and UI layers.

Does comprehensive code quality verification detect circular dependencies in new features?▼

Comprehensive code quality verification detects circular dependencies by validating new code against established design patterns. It coordinates linting and testing to ensure major feature additions do not introduce regressions.

When do I need to run full quality verification on my codebase changes?▼

Full quality verification is needed before committing a major feature or during long development sessions. It performs linting, type-checking, and test execution to prevent context drift and ensure adherence to architectural specifications.