check

Verify changed files against project guidelines using git diff, lint, and typecheck.

4|1|Updated Aug 9, 2025

Search Tags:#quality-assurance #lint #code-review #typecheck #git-diff #spec-guidelines

Ready to run

npx skills add https://github.com/LinnkidChen/Stock-Tracker --skill check-linnkidchen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: check
Source: https://github.com/LinnkidChen/Stock-Tracker/tree/main/.agents/skills/check
Command: npx skills add https://github.com/LinnkidChen/Stock-Tracker --skill check-linnkidchen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates recently written code against project-specific development guidelines from .trellis/spec/. Identifies changed files via git diff, discovers applicable spec modules, runs lint and typecheck, and reports guideline violations. Use when code is written and needs quality verification, to catch context drift during long sessions, or before committing changes.

Core Features & Use Cases

Identify changed files via git diff and map to relevant spec modules.
Discover applicable spec modules using the project context tool and read guidance.
Run lint and typecheck, report violations, and guide remediation to maintain code quality.

Quick Start

Run this skill after coding to automatically verify your changes against the project guidelines in .trellis/spec/.

Frequently Asked Questions about check

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

FAQPage Schema

How do I validate code changes against project-specific development guidelines?▼

To validate code changes, this skill identifies modified files via git diff, locates applicable spec modules in .trellis/spec/, and runs lint and typecheck operations. It reports guideline violations and provides remediation guidance to maintain code quality.

What is the best way to automate pre-commit code review for guideline drift?▼

Automating pre-commit code review involves detecting changed files through git diff and mapping them to relevant spec modules. This skill runs lint and typecheck to catch context drift and prevent guideline violations before changes are committed.

How does verifying code quality with git diff and spec modules work?▼

Verifying code quality works by analyzing git diff output to identify changed files, discovering applicable spec modules using the project context tool, and running lint and typecheck. It then reports any discovered guideline violations with guidance.

Do I need a .trellis/spec/ directory to run lint and typecheck checks?▼

Yes, you need a .trellis/spec/ directory containing project-specific development guidelines. The skill reads these spec modules to verify recently written code and report any violations against the established guidelines.

Can I use this code review skill during long coding sessions to catch context drift?▼

Yes, you can use this skill during long coding sessions to catch context drift. It validates recently written code against project-specific guidelines by running lint and typecheck on changed files identified via git diff.

What happens when lint and typecheck report violations in my changed files?▼

When lint and typecheck report violations, the skill provides guidance on remediation to maintain code quality. It maps the violations from your changed files back to the applicable spec modules found in .trellis/spec/.