check

Validate changed files against project guidelines using lint and typecheck.

Updated Apr 17, 2026

Search Tags:#code-quality #guidelines #lint #typecheck #git-diff #check

Ready to run

npx skills add https://github.com/alleneee/topsport-agent --skill check-alleneee

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: check
Source: https://github.com/alleneee/topsport-agent/tree/main/.agents/skills/check
Command: npx skills add https://github.com/alleneee/topsport-agent --skill check-alleneee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates recently written code against project-specific development guidelines to ensure consistency and quality before integration.

Core Features & Use Cases

Guideline-driven validation: Checks code against .trellis/spec modules relevant to the changed files.
Automated discovery & selection: Detects changed files via git and selects applicable spec modules automatically.
Quality enforcement & reporting: Runs lint and typecheck and reports violations for remediation, reducing drift and risky changes.
Use Case: Use this tool when preparing a commit or during long-working sessions to keep changes aligned with standards.

Quick Start

Run the check on your latest changes to ensure they conform to project guidelines before committing.

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 before a git commit?▼

To automate code quality checks before a git commit, you can run a validation tool that identifies changed files via git diff and enforces lint and typecheck rules against project guidelines. This reports violations directly for remediation before integration.

What is guideline-driven code validation for changed files?▼

Guideline-driven code validation is the process of checking recently modified files against project-specific development guidelines. It automatically discovers changed files, selects applicable spec modules, and enforces lint and typecheck rules to ensure consistency and quality.

How do I run lint and typecheck only on recently changed files?▼

You can run lint and typecheck only on recently changed files by using a tool that detects file modifications via git diff. The system automatically determines and selects applicable spec modules to validate the targeted code changes.

Does automated code validation work with project-specific spec modules?▼

Yes, automated code validation works with project-specific spec modules by reading their indexes and applying them to changed files. It enforces lint and typecheck rules defined in the specifications to guide necessary fixes before committing.

Why should I validate code against guidelines during long working sessions?▼

Validating code against guidelines during long working sessions prevents standard drift and reduces risky changes. Continuously running lint and typecheck enforcement on modified files ensures changes remain aligned with project standards before final integration.