skills.rest
wise-claw
wise-clawOFFICIAL
Explore all skills by this author →
GitHub

trellis-check

Verify code changes against quality standards and project specifications before commits.

10|Updated May 11, 2026
Search Tags:#git#testing#code review#type checking#quality check#lint#spec validation
One-click install
npx skills add https://github.com/wise-claw/wise-tui --skill trellis-check-wise-claw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trellis-check
Source: https://github.com/wise-claw/wise-tui/tree/main/.cursor/skills/trellis-check
Command: npx skills add https://github.com/wise-claw/wise-tui --skill trellis-check-wise-claw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents incomplete or inconsistent code changes from reaching commits by systematically checking specifications, implementation quality, and cross-layer correctness.

Core Features & Use Cases

  • Quality Verification: Reviews changed files against project specs, lint rules, type checks, and test requirements.
  • Cross-Layer Validation: Checks data flow, code reuse, dependency consistency, and synchronization across application layers.
  • Use Case: Use this Skill after implementing a feature to identify missing tests, spec drift, or integration issues before committing changes.

Quick Start

Run the trellis-check skill to verify the latest code changes and fix any quality issues 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 verify code quality before committing changes?▼

To verify code quality before committing, you can run a quality check skill that reviews changed files against project specs, lint rules, type checks, and test requirements to prevent incomplete changes from shipping.

What is cross-layer consistency validation in software engineering?▼

Cross-layer consistency validation checks data flow, code reuse, dependency consistency, and synchronization across application layers to maintain reliable code quality before commits.

How do I check for spec drift and missing tests after implementing a feature?▼

To check for spec drift and missing tests after implementation, run a quality verification skill that compares changed files against project specifications and validates test requirements before committing.

Does this quality check tool require any specific dependencies to run?▼

No, this quality check tool does not require any specific dependencies to run, allowing you to directly verify code changes against project specifications without additional environment setup.

When should I run spec validation during my git workflow?▼

You should run spec validation after implementing a feature and before committing changes, ensuring the code quality check identifies missing tests, spec drift, or integration issues early.

Related Skills

Explore More Software Engineering Skills→
yun-s-ohyun-s-oh

openspec-verify-change

Verify code implementation against change artifacts using command-line tools.

Community
Advanced
jellyrockjellyrock
37

commit

Automate secure, convention-compliant Git commits with pre-commit security checks.

Official
Advanced
tarekBassiounytarekBassiouny

Najaah LMS - Code Quality Agent

Enforces code quality standards for the Najaah LMS project using Pest, PHPStan, and Laravel Pint.

Community
Advanced
jfrometajfrometa

lint-and-validate

Run lint, type checks, and security audits on Node.js and Python projects.

Community
Advanced