trellis-check

Run linting, type checks, tests, and spec compliance on git diffs.

60|7|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/Ziphyrien/Pi-Telegram --skill trellis-check-ziphyrien
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trellis-check
Source: https://github.com/Ziphyrien/Pi-Telegram/tree/main/.pi/skills/trellis-check
Command: npx skills add https://github.com/Ziphyrien/Pi-Telegram --skill trellis-check-ziphyrien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Comprehensive quality verification for recently written code. Combines spec compliance, lint, type-check, tests, cross-layer safety, and consistency checks to catch drift before changes are committed.

Core Features & Use Cases

  • Enforces spec adherence, linting, type-checking, and tests across changed code paths.
  • Validates cross-layer data flow and promotes code reuse with a structured checklist.
  • Use Case: during active development or pre-commit to ensure high-quality, stable code and reduce regressions.

Quick Start

Run trellis-check on your latest changes to validate quality 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 check code quality and specification compliance before a commit?

Pre-commit quality verification catches context drift in multi-layer projects by validating recently changed code through linting, type-checking, tests, and spec compliance. It prevents regressions and ensures cross-layer data flow safety before changes are committed.

How do I prevent context drift when verifying recently changed code?

To verify changed code, the process reads git diffs to identify modified paths, consults .trellis/spec indices for specification compliance, runs lint and type-check commands, executes tests, and outputs a structured checklist reporting all findings and cross-layer safety validations.

Does this pre-commit code review tool work with multi-layer software projects?

Yes, this quality verification process specifically targets multi-layer software projects during development. It validates cross-layer data flow and enforces spec compliance, linting, type-checking, and tests across changed code paths to ensure stability.

What is the best way to enforce lint, type-check, and test validation on changed code?

The best way to enforce validation is by targeting only recently changed code paths rather than the entire project. This method reads git diffs, consults .trellis/spec indices, runs necessary commands, and promotes code reuse with a structured checklist.

Why does my long-running development work lose specification compliance over time?

Long-running work often loses specification compliance due to context drift. Running a pre-commit quality check that consults .trellis/spec indices and validates cross-layer data flow catches this drift early and enforces adherence to original specs.