check

Validate changed code against project guidelines via git diff and lint/typecheck.

3.9k|339|Updated Feb 3, 2026

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

Ready to run

npx skills add https://github.com/zhukunpenglinyutong/desktop-cc-gui --skill check-zhukunpenglinyutong

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: check
Source: https://github.com/zhukunpenglinyutong/desktop-cc-gui/tree/main/.agents/skills/check
Command: npx skills add https://github.com/zhukunpenglinyutong/desktop-cc-gui --skill check-zhukunpenglinyutong

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 using git diff to focus reviews on recently touched code.
Determine applicable spec modules based on changed paths via the context script.
Read the spec index and the actual guidelines referenced in it, to ensure compliance.
Run lint and typecheck for affected packages and report violations automatically.
Use case: before committing changes, or during long sessions, to ensure code adheres to project standards.

Quick Start

Run this skill after writing code to verify it conforms to the project guidelines and report any violations.

Frequently Asked Questions about check

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

FAQPage Schema

How do I automate code quality checks against project development guidelines?▼

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.

How does a lint and typecheck workflow validate modified files?▼

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.

Can I use git diff to focus code review on recently touched files?▼

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.

When should I run a code review for guideline compliance during development?▼

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.

What is the best way to catch context drift in long coding sessions?▼

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.

Why does typecheck report violations on files not in the spec index?▼

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.