check

To automate code quality checks, this Skill identifies changed files via git diff, discovers applicable spec modules from .trellis/spec/, and runs lint and typecheck to report guideline violations. It focuses on recently modified code to ensure compliance before committing.

A lint and typecheck workflow validates modified files by diffing recent changes, selecting relevant spec modules based on changed paths, and executing lint and typecheck commands. It then reports any development guideline violations found in the affected packages.

Yes, you can use git diff to focus code review on recently touched files. This Skill uses git diff to identify changed files, determines applicable spec modules, and reads the spec index to ensure the modified code adheres to project-specific development guidelines.

You should run a code review for guideline compliance after writing code and before committing changes. It is also useful during long development sessions to catch context drift and verify that your code changes adhere to the project standards defined in the spec index.

The best way to catch context drift in long coding sessions is to run automated quality checks against your project guidelines. This Skill diffs recent changes, reads the spec index, and executes lint and typecheck to identify and report any guideline violations automatically.

Typecheck reports violations on files not in the spec index because it validates all changed files identified by git diff. It reads the spec index to determine applicable guidelines, but executes lint and typecheck broadly across affected packages to enforce standards.