checking-changes

Name: checking-changes
Availability: InStock
Author: Streamlit

Run formatting, linting, type checking, and unit tests on uncommitted Python and TypeScript changes.

45.5k|4.4k|Updated Aug 24, 2019

Search Tags:#formatting #pre-commit #code-quality #make #lint #type-checking #unit-tests

Ready to run

npx skills add https://github.com/streamlit/streamlit --skill checking-changes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: checking-changes
Source: https://github.com/streamlit/streamlit/tree/main/.claude/skills/checking-changes
Command: npx skills add https://github.com/streamlit/streamlit --skill checking-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates code changes before committing by running formatting, linting, type checking, and unit tests across all uncommitted files.

Core Features & Use Cases

End-to-end pre-commit validation: Runs formatters, linters, type checkers, and tests to ensure code quality before commit.
Supports Python and TypeScript: Works with backend Python and frontend TypeScript changes in a single workflow.
Use Case: Before finishing a feature, run the check to catch style and type errors early, reducing rework.

Quick Start

Run the check target to validate your changes before committing.

Frequently Asked Questions about checking-changes

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

FAQPage Schema

How do I run pre-commit checks for formatting and linting on Python and TypeScript code?▼

Pre-commit checks validate code quality by running formatting, linting, type checking, and unit tests across uncommitted Python and TypeScript files using a Makefile target named 'check'.

What do I need to validate code changes before committing?▼

Validating code changes requires a functioning local development environment and a Makefile target named 'check' to execute formatting, linting, type checking, and unit tests.

Does pre-commit validation work with both backend Python and frontend TypeScript changes?▼

Pre-commit validation supports both backend Python and frontend TypeScript changes, running formatting, linting, type checking, and unit tests in a single workflow across all uncommitted files.

What is the best way to catch style and type errors before finishing a feature?▼

The best way to catch style and type errors early is to run end-to-end pre-commit validation on uncommitted code, reducing rework by ensuring code quality before finishing a feature.

Why should I run code quality checks on uncommitted work instead of waiting until commit?▼

Running code quality checks on uncommitted work catches style and type errors early, reducing rework by validating formatting, linting, type checking, and unit tests before committing.