check

Run lint and typecheck on git-changed packages against .trellis/spec guidelines.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/SilentFlower/flower-cli --skill check-silentflower
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check
Source: https://github.com/SilentFlower/flower-cli/tree/main/.agents/skills/check
Command: npx skills add https://github.com/SilentFlower/flower-cli --skill check-silentflower

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates recently written code against project-specific development guidelines, surfacing violations before they cause issues.

Core Features & Use Cases

  • Identify changed files via git diff and determine applicable spec modules based on file paths.
  • Run lint and typecheck on affected packages and report any guideline violations.
  • Use case: during a commit or PR, quickly verify adherence to .trellis/spec before review.

Quick Start

Run the check on the current git changes to verify all modified files against the project's guidelines.

Frequently Asked Questions about check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify code quality against project guidelines before a commit?

To verify code quality against project guidelines, run a check that identifies changed files via git diff and evaluates them against your .trellis/spec modules. It applies lint and typecheck to affected packages, reporting any guideline violations found.

What is the best way to lint and typecheck only the files changed in a git diff?

The best way to lint and typecheck only modified files is to use a check tool that parses the git diff output to determine applicable spec modules. It then runs lint and typecheck exclusively on those affected packages to surface violations.

How does checking code against .trellis/spec modules work during a pull request?

Checking code against .trellis/spec modules during a pull request works by reading the project guidelines, analyzing the git diff for changed file paths, and running lint and typecheck on affected packages to report any adherence violations before review.

Can I use project spec modules to typecheck affected packages automatically?

Yes, you can use project spec modules to typecheck affected packages automatically. The check process maps changed files from the git diff to their applicable .trellis/spec modules and runs typecheck specifically on those impacted packages.

Why does my code check report guideline violations on unaffected packages?

Code check reports guideline violations by targeting only the affected packages determined by your git diff. If violations appear on unaffected packages, it indicates the file path mapping to the .trellis/spec modules has identified broader changes than expected.

Do I need external dependencies to run lint and typecheck on modified code?

No, you do not need external dependencies to run lint and typecheck on modified code against .trellis/spec modules. The check process autonomously reads the guidelines and evaluates the git diff without requiring additional component installations.