trellis-check

Verify lint, type-check, tests, and data-flow quality gates for changed code.

45|9|Updated Feb 22, 2026

Search Tags:#code-quality #lint #code-review #tests #type-check #trellis

Ready to run

npx skills add https://github.com/Tendo33/IdeaGo --skill trellis-check-tendo33

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates comprehensive quality verification to ensure newly written code meets specifications, passes lint and type checks, runs tests, and preserves cross-layer data flow and code reuse integrity.

Core Features & Use Cases

Spec compliance, linting, type-check, and test execution across changed code
Cross-layer data-flow validation and consistency checks to catch context drift
Suitable for pre-commit hooks and CI pipelines to prevent regressions

Quick Start

Run the trellis-check workflow on changed packages to validate lint, type-checks, and tests before committing.

Frequently Asked Questions about trellis-check

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

FAQPage Schema

How do I automate code quality verification for changed code before committing?▼

You can automate code quality verification by running a workflow that compares code diffs against specs and applies lint, type-check, and test execution to changed packages. This process ensures consistency, prevents regressions, and guards against unsafe changes before committing.

What is cross-layer data-flow validation and when do I need it for code review?▼

Cross-layer data-flow validation checks consistency across your codebase to catch context drift during code review. You need it when newly written code risks breaking data flow between layers, ensuring specifications are met and regressions are prevented.

Can I use automated lint and type-check enforcement in CI pipelines?▼

Yes, you can use automated lint and type-check enforcement in CI pipelines to prevent regressions. The workflow validates changed code against specifications, runs project checks, documents failures, and guides fixes to ensure newly written code meets quality gates.

What's the best way to verify spec compliance for recently changed code?▼

The best way to verify spec compliance is to compare code diffs against specifications while running lint, type-check, and tests. This end-to-end quality verification enforces checklist completion, documents failures, and guides fixes to ensure consistency across the codebase.

Why does my code review workflow miss context drift and cross-layer inconsistencies?▼

Your code review workflow misses context drift because it lacks cross-layer data-flow validation. By comparing diffs against specs and validating consistency across the codebase, you can catch context drift, document failures, and guide fixes to prevent regressions.

Do I need dependencies to run end-to-end quality verification on changed packages?▼

No, you do not need external dependencies to run end-to-end quality verification. The workflow independently compares diffs against specs, applies lint and type-checks, runs tests, and validates cross-layer data flow to ensure code quality without requiring additional setup.