lint-and-validate

Lint and validate Python code changes with syntax checks and file-size limits.

1|3|Updated May 22, 2025
One-click install
npx skills add https://github.com/minuum/vla --skill lint-and-validate-minuum
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint-and-validate
Source: https://github.com/minuum/vla/tree/main/.agent/skills/lint-and-validate
Command: npx skills add https://github.com/minuum/vla --skill lint-and-validate-minuum

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintain code quality by running linters on modified files and ensuring that large assets are not committed accidentally, preventing broken builds and oversized repos.

Core Features & Use Cases

  • Linting: Validates syntax for modified files and runs flake8/pylint when available to catch common errors early.
  • File Size & LFS Check: Enforces a 50MB limit for new files and suggests Git LFS usage or ignoring large binaries to prevent bloated history.
  • Auto-Fix: Automatically fixes simple issues like trailing whitespace or missing newline to streamline commits.
  • Use Case: Before committing, run lint-and-validate to ensure all new/modified code is clean and compliant with size constraints.

Quick Start

Run lint-and-validate on the staged changes to detect syntax errors, large files, and minor formatting issues.

Frequently Asked Questions about lint-and-validate

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

FAQPage Schema
How do I run linting and syntax checks on Python files before a git commit?

To run linting before a git commit, you can apply a pre-commit hook that validates modified Python files using py_compile for syntax and flake8 or pylint for static analysis. This detects syntax errors and common issues early.

What is the best way to prevent large files from being committed to a git repository?

The best way to prevent large files in a git repository is enforcing a file size limit policy during pre-commit. This Skill enforces a 50MB limit for new files and suggests using Git LFS or ignoring large binaries to prevent bloated history.

Does pre-commit linting automatically fix formatting issues like trailing whitespace?

Yes, pre-commit linting can automatically fix simple issues like trailing whitespace and missing newlines. This auto-fix capability streamlines commits by cleaning up minor formatting problems without manual intervention.

Do I need flake8 or pylint installed to validate code quality during pre-commit?

You do not strictly need flake8 or pylint installed to validate code quality during pre-commit. The Skill requires Python and uses py_compile for mandatory syntax checks, running flake8 or pylint optionally when available for deeper static analysis.

When should I configure Git LFS for my Python project assets?

You should configure Git LFS for your Python project assets when adding new files that exceed the 50MB size threshold. The pre-commit validation policy flags these oversized files and advises using Git LFS to avoid bloated repository history.

Why does my git commit fail with a file size limit check?

Your git commit fails the file size limit check because a newly staged file exceeds the 50MB enforcement policy. This validation prevents oversized commits and broken builds by suggesting you either remove the file, ignore it, or use Git LFS.