trellis-check

Verify changed code paths against specs and quality gates.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jhxxr/OpenSciReader --skill trellis-check-jhxxr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trellis-check
Source: https://github.com/jhxxr/OpenSciReader/tree/main/.opencode/skills/trellis-check
Command: npx skills add https://github.com/jhxxr/OpenSciReader --skill trellis-check-jhxxr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Comprehensive quality verification for recently written code, combining spec compliance, cross-layer safety checks, and pre-commit style audits to prevent drift and regressions.

Core Features & Use Cases

  • Step-by-step checks for changed code paths, including identifying changes, reading specs, running lint/type/test checks, reviewing against a checklist, and reporting findings.
  • Cross-layer validation: ensures data-flow integrity, consistency, and actionable remediation guidance across layers (storage, service, API, UI).
  • Quick-start guided workflow: provides a repeatable, auditable process before committing changes.

Quick Start

Initiate a trellis-check pass on the latest changes to verify spec compliance, lint, type-check, tests, and cross-layer data integrity 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 run pre-commit checks for lint, type-checking, and tests on changed code?

Pre-commit checks identify recently changed code paths and sequentially execute lint, type-check, and test verifications against project specs before committing. This structured process reports findings and enforces code quality through a guided workflow.

What is cross-layer data-flow verification and when do I need it before committing?

Cross-layer data-flow verification ensures data integrity and consistency across storage, service, API, and UI layers. You need this pre-commit validation to prevent drift and regressions when code changes impact multiple architectural layers.

How do I verify code changes against project specs and quality gates?

Verify code changes against project specs by following a deterministic pre-commit workflow that reads specifications, runs quality gates like lint and type-checks, and reviews changes against a structured checklist to produce actionable audit artifacts.

Can I use this pre-commit workflow for code changes across any package or module?

Yes, you can use this pre-commit workflow for code changes across any package or module that requires linting, type-checking, tests, and cross-layer data-flow verification during development. It applies broadly to enforce consistent quality gates.

What's the best way to prevent regressions when modifying code across multiple layers?

The best way to prevent regressions is enforcing cross-layer validation during pre-commit checks, ensuring data-flow integrity and consistency across storage, service, API, and UI layers. This provides actionable remediation guidance before changes are committed.