Skill Store 33

Checking Changes

Validates all code changes before committing by running format, lint, type, and unit test checks.

by streamlit · Apache-2.0

The skill

Validates all code changes before committing by running format, lint, type, and unit test checks. Use after making backend (Python) or frontend (TypeScript) changes, before committing or finishing a work session.

Checking Changes

Run at the end of a work session or after completing a set of changes — not after every small edit.

make check

This runs formatting, linting, type checking, Knip unused-export and unused-dependency analysis, and unit tests on all uncommitted files (staged, unstaged, and untracked).

Workflow

  1. Run make check
  2. If issues are found:
    • Fix the reported errors
    • Re-run make check
    • Repeat until all checks pass
  3. Only consider work complete when make check succeeds

Notes

  • E2E tests are not included by default; use E2E_CHECK=true make check to also run changed e2e tests
  • E2E snapshot mismatches can be ignored (they require manual updates)

Use this skill

Connect your agent to the Skill Store MCP server and ask for it by ref: streamlit/checking-changes-51154313461.

Download SKILL.md · Markdown version

Details

Publisher
streamlit
Category
Software Development › Testing & QA
License
Apache-2.0
Updated
2026-10-19

References

More from streamlit

Related skills

  • Check Validate code quality — auto-fix formatting/lint, verify types, run tests.
  • Validate Code Run the full code quality validation suite for this codebase.
  • Code Polish Simplifies and reviews code changes in a Git repository, fixing verified defects by severity (securi
  • Verify Use when you want to validate changes before committing, or when you need to check all React cont…
  • Fix Use when you have lint errors, formatting issues, or before committing code to ensure it passes CI.