skills.rest
elebirds
elebirdsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

trellis-check

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

Updated Apr 4, 2026
Search Tags:#testing#code review#pre-commit#quality check#spec compliance#lint#cross-layer
One-click install
npx skills add https://github.com/elebirds/panoptes --skill trellis-check-elebirds
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trellis-check
Source: https://github.com/elebirds/panoptes/tree/main/.opencode/skills/trellis-check
Command: npx skills add https://github.com/elebirds/panoptes --skill trellis-check-elebirds

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 provides a structured quality verification workflow that catches these issues before committing. ## Core Features & Use Cases - Spec Compliance Verification: Reads applicable specs from .trellis/spec/ via the context script and checks changed code against each layer's quality guidelines. - Project Checks: Runs lint, type-check, and test commands and requires all failures to be fixed before proceeding. - Cross-Layer Review: Traces data flow (Storage → Service → API → UI), checks code reuse, import correctness, and same-layer consistency for changes spanning multiple layers. - Use Case: After implementing a feature touching the API and service layers, run this check to confirm tests pass, no duplicated constants were introduced, and the spec docs are updated with any lessons learned. ## Quick Start Ask the agent to run the trellis quality check on the current uncommitted changes before committing them.

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 this check after writing code: it inspects git diff output, reads applicable specs, executes the project's lint, type-check, and test commands, then reviews a checklist covering debug logging, test coverage, and spec synchronization before you commit.

How to check cross-layer data flow consistency in a codebase?▼

The check traces read flow from Storage through Service and API to UI, and write flow in reverse. It verifies types and schemas pass correctly between layers and that errors propagate properly to callers when changes touch three or more layers.

What does the trellis spec directory contain?▼

The .trellis/spec directory holds per-package, per-layer spec indexes with quality check sections. The get_context.py script lists applicable packages, and each index points to specific guideline files that must be read for the changed layers.

When should I skip the cross-layer review steps?▼

Skip the cross-layer dimensions when your change is confined to a single layer. The data flow, code reuse, import, and same-layer consistency checks only apply to changes spanning multiple layers or creating new files and shared constants.

Does this check update documentation automatically?▼

It prompts you to update .trellis/spec docs when you fix a bug or discover something non-obvious, so future work avoids the same issue. The actual spec edits are made as part of the review, not by an automated script.

Related Skills

Explore More Software Engineering Skills→
kaosnyrbkaosnyrb
12

commit

Stage and commit Git changes with a diff-derived message.

Community
Intermediate
santychuycomsantychuycom

ship

Analyze diffs, create atomic conventional commits, push, and open pull requests.

Official
Advanced
michael-watsonmichael-watson
8

keep-ai-ready

Update AGENTS.md and HOWTOAI.md after significant implementation changes.

Community
Intermediate
redpanda-dataredpanda-data
34

setup-quality-gate

Set up a quality gate with biome, tsgo, and vitest.

Official
Advanced