trellis-check

Name: trellis-check
Availability: InStock
Author: XiaSanw

Validate lint, type checks, tests, and spec alignment for recent code changes.

2|Updated May 25, 2026

Search Tags:#code-quality #lint #specs #tests #type-check #cross-layer

Ready to run

npx skills add https://github.com/XiaSanw/LLM-WIKI-Xiasanw --skill trellis-check-xiasanw

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: trellis-check
Source: https://github.com/XiaSanw/LLM-WIKI-Xiasanw/tree/main/.claude/skills/trellis-check
Command: npx skills add https://github.com/XiaSanw/LLM-WIKI-Xiasanw --skill trellis-check-xiasanw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Comprehensive quality verification for recently written code, validating specs, lint, type-checks, tests, and cross-layer consistency to prevent drift and regressions.

Core Features & Use Cases

Identify changes since the last commit and pull relevant specs.
Execute linting, type checks, and tests, and compare against spec guidelines.
Validate cross-layer data flow and consistency, with remediation guidance when issues are found.
Use as a pre-commit or during ongoing development to prevent context drift.

Quick Start

Run trellis-check after coding to verify lint, types, tests, and spec alignment 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 validate code quality and specs before a commit?▼

To validate code quality before a commit, run a check against recently written code to verify linting, type checks, tests, and cross-layer consistency. This process ensures changes align with project specs and prevents regressions.

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

Cross-layer data flow validation verifies that data interactions across different architectural layers remain consistent. It detects context drift during ongoing development and provides remediation guidance when issues are found.

How do I prevent context drift during long-running development sessions?▼

Prevent context drift during long-running sessions by validating recently written code against project specs and guidelines. Running quality checks mid-session detects drift early and prevents regressions before committing.

Can I use automated checks to compare new code against project specs?▼

Yes, you can identify changes since the last commit and pull relevant specs to compare against. The check executes lint, type, and test validations, then compares the results against your spec guidelines.

What is the best way to enforce end-to-end code consistency before pushing?▼

The best way to enforce end-to-end consistency is running a pre-commit validation that checks lint, types, tests, and cross-layer data flow. This detects drift and ensures alignment with project guidelines before changes are committed.