Checking Changes
Testing & Qualitychecking-changesChecking Changes is an Agent Skill for testing & quality published in the streamlit/streamlit repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
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.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/streamlit/streamlit/blob/HEAD/.claude/skills/checking-changes/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/checking-changes, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
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 checksucceeds
Notes
- E2E tests are not included by default; use
E2E_CHECK=true make checkto also run changed e2e tests - E2E snapshot mismatches can be ignored (they require manual updates)