skills.rest
tincopper
tincopperCOMMUNITY
Explore all skills by this author →
GitHub

trellis-check

Verify recent code changes for quality regressions and implementation drift.

10|Updated Mar 21, 2026
Search Tags:#testing#quality assurance#code review#linting#type checking#regression#spec compliance
One-click install
npx skills add https://github.com/tincopper/neeko --skill trellis-check-tincopper
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trellis-check
Source: https://github.com/tincopper/neeko/tree/main/.agents/skills/trellis-check
Command: npx skills add https://github.com/tincopper/neeko --skill trellis-check-tincopper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you catch quality issues after code changes by checking spec alignment, lint, type safety, tests, and cross-layer consistency before you commit or continue working.

Core Features & Use Cases

  • Change Review: Identifies what files and packages changed so the right checks are applied.
  • Validation Workflow: Runs lint, type-check, and tests to confirm the code is working as expected.
  • Consistency Checks: Reviews code reuse, imports, dependencies, and same-layer behavior to reduce drift and regressions.
  • Use Case: A developer finishes a feature branch and uses this Skill to verify the implementation, update specs if needed, and fix any issues before opening a pull request.

Quick Start

Use the trellis-check skill to review the latest code changes for spec compliance, tests, lint, type safety, and cross-layer consistency 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 and spec compliance before a commit?▼

Pre-commit validation involves reviewing recent code changes by running lint, type-check, and tests. This ensures spec alignment and checks cross-layer consistency to prevent quality regressions before committing.

What is cross-layer consistency checking in code review?▼

Cross-layer consistency checking reviews code reuse, imports, and dependencies across changed packages to reduce drift and regressions. It ensures same-layer behavior remains stable after modifying files.

How do I check for implementation drift during a long development session?▼

Long-session drift checks involve applying lint, type-check, and spec-sync validations to recently modified code. This confirms that ongoing changes have not introduced implementation drift or broken cross-layer consistency.

Can I use automated lint and type-checking for release readiness reviews?▼

Automated lint and type-checking are essential for release readiness reviews. Applying them alongside tests and spec-sync checks across changed files confirms quality and prevents regressions before a release.

What is the best way to update specs after modifying code packages?▼

The best way to update specs after modifying packages is to run a validation workflow that includes spec-sync reviews. This identifies implementation drift and updates specifications to match the recent code changes.

Related Skills

Explore More Software Engineering Skills→
brainbrewlabsbrainbrewlabs
7

code-scanning

Scan changed files for code quality and dependency issues.

Official
Advanced
dobrinz123dobrinz123

gsd-ship

Push branches, create pull requests, and monitor merge status.

Community
Intermediate
tedtv1007-ctrltedtv1007-ctrl

playwright-testing

Automate browser-based end-to-end testing with Playwright.

Community
Advanced
Obsidian-OwlObsidian-Owl
9

gate-wiring

Detect unused exports, orphaned files, layer violations, and circular dependencies in changed code.

Official
Intermediate