trellis-check

Run lint, type-check, tests, and spec compliance checks before commits.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/21ess/graffiti --skill trellis-check-21ess
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trellis-check
Source: https://github.com/21ess/graffiti/tree/main/.claude/skills/trellis-check
Command: npx skills add https://github.com/21ess/graffiti --skill trellis-check-21ess

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Comprehensive quality verification for recently written code. Combines spec compliance, cross-layer safety, and pre-commit checks.

Core Features & Use Cases

  • Identify what changed in the codebase to narrow the scope of checks.
  • Read applicable specs and follow the Quality Check guidelines across layers.
  • Run lint, type-check, and tests; enforce a clean, verified state before commits.
  • Review against a cross-layer quality checklist to ensure consistency and prevent drift.

Quick Start

Run trellis-check on your current changes to verify spec compliance, linting, 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 pre-commit code quality checks for lint, types, and tests?

To automate pre-commit code quality checks, you run a verification process across specs, linting, typing, and tests to enforce a clean state. This ensures cross-layer data-flow integrity and prevents context drift before committing.

What is cross-layer quality assurance in software engineering?

Cross-layer quality assurance is the process of reviewing code against a checklist to ensure consistency across architectural layers. It verifies spec synchronization and data-flow integrity to prevent drift during ongoing development.

How do I detect context drift in newly written code during long sessions?

To detect context drift in newly written code during long sessions, you identify changed codebase areas and verify them against applicable specs. Running continuous lint, type-check, and test validations maintains spec compliance.

Can I narrow the scope of code quality checks to only changed files?

Yes, you can narrow the scope of code quality checks by identifying what changed in the codebase first. This targeted verification reads applicable specs and runs lint, type-checks, and tests only on the modified scope.

What's the best way to ensure specs and tests stay synchronized before a commit?

The best way to ensure specs and tests stay synchronized before a commit is running an end-to-end verification that reads applicable specs and enforces test passes. This cross-layer check prevents data-flow inconsistencies.