trellis-check

Verifies code changes against specs, lint, type checks, tests, and cross-layer consistency.

2|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/42team-ru/teampilot --skill trellis-check-42team-ru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trellis-check
Source: https://github.com/42team-ru/teampilot/tree/main/.cursor/skills/trellis-check
Command: npx skills add https://github.com/42team-ru/teampilot --skill trellis-check-42team-ru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After writing code, it is easy to miss spec violations, broken tests, leftover debug logging, or inconsistencies across architectural layers. This Skill runs a structured quality verification pass over recent changes before they are committed, catching drift and defects early. ## Core Features & Use Cases - Spec Compliance Verification: Reads the applicable Trellis spec indexes and guideline files for each changed package or layer, then checks the code against them. - Project Checks: Runs the project's lint, type-check, and test commands and requires failures to be fixed before proceeding. - Cross-Layer Review: Validates data flow (Storage → Service → API → UI), code reuse, import/dependency correctness, and same-layer consistency for multi-layer changes. - Use Case: After implementing a feature spanning the API and UI layers, run this check to confirm types propagate correctly, tests cover the new behavior, and the spec docs are updated with any lessons learned. ## Quick Start Run the trellis-check quality verification on my current uncommitted changes and fix any violations it finds.

Frequently Asked Questions about trellis-check

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

FAQPage Schema
How do I verify code quality before committing changes?

Run a structured check that inspects git diff output, reads applicable spec files, executes the project's lint, type-check, and test commands, and reviews a checklist covering debug logging, test coverage, and spec synchronization. Fix any failures before committing.

How to check cross-layer data flow in a full-stack codebase?

Trace read flows from Storage through Service and API to UI, and write flows in reverse. Confirm types and schemas pass correctly between layers and that errors propagate to the caller. This applies when changes touch three or more layers.

When should I update spec documentation after a code change?

Update specs when you fix a bug, discover a non-obvious pattern, or establish a new convention. The guiding question is whether documenting it would prevent future occurrences of the same issue.

What test coverage should accompany new code changes?

New functions require unit tests, bug fixes require regression tests, and changed behavior requires updating existing tests. The verification checklist enforces all three cases before changes are considered complete.

Does this check work for single-layer changes?

Yes, but the cross-layer dimensions step is skipped when the change is confined to a single layer. Lint, type-check, test, and spec compliance steps still apply to every change.