trellis-check

Verify code changes against project specifications and quality checks.

132|26|Updated Sep 9, 2022
One-click install
npx skills add https://github.com/ROYIANS/print-template-designer --skill trellis-check-royians
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trellis-check
Source: https://github.com/ROYIANS/print-template-designer/tree/main/.cursor/skills/trellis-check
Command: npx skills add https://github.com/ROYIANS/print-template-designer --skill trellis-check-royians

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps catch implementation defects, specification drift, incomplete tests, and cross-layer inconsistencies before code is committed or released.

Core Features & Use Cases

  • Comprehensive Verification: Reviews changes against project specifications, linting, type-checking, and test requirements.
  • Cross-Layer Safety Checks: Traces data flow, validates imports and dependencies, and checks consistency across application layers.
  • Use Case: After implementing a new template API feature, use this Skill to identify missing regression tests, specification updates, type issues, and integration errors before committing.

Quick Start

Use the trellis-check skill to inspect the current changes, run all applicable project checks, and fix any quality or specification violations.

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 and spec compliance before committing changes?

Pre-commit code quality verification inspects changed files, reads applicable project specifications, and runs lint, type-check, and test commands to detect implementation defects and specification drift before changes ship.

How do I detect cross-layer inconsistencies and context drift across application packages?

Cross-layer validation traces data flow, validates imports and dependencies, and checks consistency across application layers to detect context drift and integration errors across packages before release.

What is the best way to run pre-commit checks for feature implementation and bug fixes?

Pre-commit review for feature implementations and bug fixes applies comprehensive verification by inspecting changed files, running lint and type-check commands, and validating cross-layer data flow and reuse against project specifications.

Does pre-commit code review work for catching missing regression tests and specification updates?

Pre-commit code review identifies missing regression tests, specification updates, type issues, and integration errors by inspecting changed files and validating them against applicable project specifications and quality requirements.

How do I validate cross-layer data flow and imports before shipping code changes?

Cross-layer data flow validation traces dependencies, validates imports, and checks consistency across application layers by inspecting changed files and running applicable project checks before code is committed.

When should I use automated code quality checks instead of manual review?

Automated code quality checks should be used for pre-commit reviews, feature implementations, and bug fixes to catch implementation defects, incomplete tests, and specification drift that manual review might miss before changes ship.