trellis-check

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

4|1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/ZipperCode/lingma2api --skill trellis-check-zippercode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trellis-check
Source: https://github.com/ZipperCode/lingma2api/tree/main/.opencode/skills/trellis-check
Command: npx skills add https://github.com/ZipperCode/lingma2api --skill trellis-check-zippercode

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 layers before committing. This Skill runs a structured quality verification pass over recently changed code so defects and context drift are caught before they reach the repository. ## Core Features & Use Cases - Spec Compliance Review: Reads the applicable .trellis/spec/ package and layer indexes and checks changed code against their Quality Check guidelines. - Project Checks: Runs the project's lint, type-check, and test commands and requires failures to be fixed before proceeding. - Cross-Layer Analysis: Traces data flow (Storage → Service → API → UI), checks code reuse, import paths, circular dependencies, and same-layer consistency for multi-layer changes. - Use Case: After implementing a feature spanning the API and UI layers, run this check before committing to confirm tests pass, types align across layers, and the spec docs are updated with any lessons learned. ## Quick Start Ask the assistant to run the trellis quality check on the 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 check code quality before committing changes?

Run a structured review that inspects git diff output, executes the project's lint, type-check, and test commands, and walks a checklist covering debug logging, test coverage, and spec synchronization. Fix any failures and re-run the checks before committing.

How to verify cross-layer data flow in a full-stack change?

Trace the read path from Storage through Service and API to the UI, and the write path in reverse. Confirm types and schemas are passed correctly between layers and that errors propagate to the caller instead of being swallowed.

When should spec documentation be updated after a code change?

Update the spec when a change introduces new patterns or conventions, or when a bug fix reveals something non-obvious. The rule of thumb is to document anything that would help avoid hitting the same issue again.

What should I check when creating new utility code or constants?

Search the codebase for existing similar implementations before writing new ones. If two or more places define the same value, extract it into a shared constant, and after batch modifications verify all occurrences were updated.

Can this check be skipped for single-layer changes?

The cross-layer dimensions such as data flow tracing and import dependency checks can be skipped when the change is confined to a single layer. The core lint, type-check, test, and spec compliance steps still apply.