mcpbeat

Checking Changes

streamlit/checking-changes

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.

229 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
45465
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/streamlit/streamlit --skill checking-changes

The instruction itself

3 sections, as written by the author

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, and unit tests on all uncommitted files (staged, unstaged, and untracked).

Workflow

  • Run make check
  • If issues are found:
  • Fix the reported errors
  • Re-run make check
  • Repeat until all checks pass
  • 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)

How to use it

Copy the folder

Take streamlit/checking-changes from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.