trellis-check

Automate pre-commit code quality checks including linting, type-checking, and testing.

8|1|Updated May 4, 2026
One-click install
npx skills add https://github.com/yuanjing-hash/OhMyCine --skill trellis-check-yuanjing-hash
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trellis-check
Source: https://github.com/yuanjing-hash/OhMyCine/tree/main/.agents/skills/trellis-check
Command: npx skills add https://github.com/yuanjing-hash/OhMyCine --skill trellis-check-yuanjing-hash

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures code quality by performing a suite of checks including spec compliance, linting, type-checking, and testing before changes are committed, preventing context drift and maintaining code integrity.

Core Features & Use Cases

  • Comprehensive Checks: Validates spec compliance, linting, type-checking, and testing.
  • Pre-commit Safety: Catches issues early in the development process.
  • Cross-Layer Analysis: Inspects data flow, code reuse, and consistency across layers.

Quick Start

Run the trellis-check skill to verify the quality of your code changes 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 automate code quality checks before committing changes?

Automating pre-commit code quality checks involves validating spec compliance, linting, type-checking, and testing. This process prevents context drift and maintains code integrity before changes are committed.

What is cross-layer data flow analysis in pre-commit checks?

Cross-layer data flow analysis inspects data movement, code reuse, and consistency across architectural layers during pre-commit checks. It ensures structural integrity and validates that changes align with context-specific specifications.

How do I ensure spec compliance during code linting?

Ensuring spec compliance during linting requires context-specific specifications integrated into your pre-commit checks. The validation process verifies code against these specifications alongside standard linting and type-checking rules.

Do I need context-specific specifications to run pre-commit type-checking?

Yes, context-specific specifications are required to run pre-commit type-checking and spec compliance validation. These specifications provide the necessary rules for cross-layer analysis, ensuring code reuse and consistency.

What is the best way to prevent context drift before a code commit?

Preventing context drift before a code commit is best achieved by automating a comprehensive suite of pre-commit checks. Validating spec compliance, linting, type-checking, and testing catches deviations early and maintains code integrity.