trellis-check

Automate code quality checks across specs, linting, typing, and tests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automated verification of code quality across specs, lint, type-checking, and tests to catch issues before they reach production.

Core Features & Use Cases

  • Coordinated quality checks across specs, linting, type-checking, and tests
  • Cross-layer consistency verification and drift detection during long sessions
  • Guidance for maintaining alignment with project specs and governance

Quick Start

Run the trellis-check process to perform code-quality verification on your latest 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 code quality checks across linting, type-checking, and tests before committing?

Automating code quality checks involves running lint, type-check, and tests on your recent code changes to catch issues before production. This process analyzes diffs and enforces a cross-cutting quality checklist to ensure spec-aligned verification.

What is cross-layer consistency verification and when do I need it for my project?

Cross-layer consistency verification detects drift across multi-layer changes during long development sessions. You need it when maintaining alignment with project specs and governance, ensuring coordinated checks across specs, linting, type-checking, and tests.

Can I verify that my recent code changes align with project specs automatically?

Yes, you can verify code aligns with project specs automatically by reading relevant specs from the .trellis/spec directory. This guides checks from diff analysis to spec-aligned verification, producing a concise report with actionable fixes.

Does trellis-check work with multi-layer changes in complex projects?

trellis-check is designed for projects with multi-layer changes, guiding checks from diff analysis to spec-aligned verification. It enforces a cross-cutting quality checklist across specs, linting, typing, and tests before commits.

What's the best way to catch code drift during long development sessions?

The best way to catch code drift is by running coordinated quality checks across specs, linting, type-checking, and tests. This detects cross-layer inconsistencies and maintains alignment with project governance throughout long sessions.

Do I need to run lint and tests separately to verify code quality?

No, you do not need to run them separately. The process automates comprehensive code quality verification by running lint, type-check, and tests together, analyzing recent diffs to produce a single actionable report.