check

Run lint and typecheck on git-changed files using local project guidelines.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates recently written code against project-specific development guidelines maintained in .trellis/spec. It helps teams ensure consistency and catch drift before changes are committed.

Core Features & Use Cases

  • Identify changed files using git diff to limit scope to relevant changes.
  • Determine applicable spec modules based on changed paths using local tooling.
  • Load and consult the spec index and guidelines to drive validation checks.
  • Run lint and typecheck on affected packages and report violations with guidance.
  • Ideal for pre-commit checks, code reviews, and long-running sessions where drift may occur.

Quick Start

Review the latest changes and run the check to ensure compliance with 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 run lint and typecheck only on changed files before a git commit?

To run lint and typecheck on changed files before a commit, use the check skill. It identifies modified files via git diff, loads project-specific guidelines, and reports violations with actionable guidance for affected packages.

What is the best way to enforce development guidelines from my local repository during code review?

Enforcing development guidelines during code review is done by loading specs from the local repository's .trellis/spec directory. The check skill validates recent changes against these guidelines to catch consistency drift before changes are committed.

How does static analysis scope validation work when using git diff?

Static analysis scope validation works by using git diff to detect changed files, determining applicable spec modules based on those paths, and limiting lint and typecheck execution to the affected packages rather than the entire codebase.

Do I need to manually configure spec modules to validate code quality in a long-running session?

You do not need to manually configure spec modules to validate code quality in a long-running session. The check skill automatically loads the spec index and guidelines from the local repository to drive validation checks and surface drift.

Why does my pre-commit check report violations for packages unaffected by my current changes?

Pre-commit check violations for unaffected packages should not occur because validation is scoped by detecting changed files with git diff and determining applicable spec modules. It specifically targets lint and typecheck results for the affected packages only.