streamlit / checking-changes
Install for your project team
Run this command in your project directory to install the skill for your entire team:
mkdir -p .claude/skills/checking-changes && curl -L -o skill.zip "https://fastmcp.me/Skills/Download/3424" && unzip -o skill.zip -d .claude/skills/checking-changes && rm skill.zipProject Skills
This skill will be saved in .claude/skills/checking-changes/ and checked into git. All team members will have access to it automatically.
Important: Please verify the skill by reviewing its instructions before using it.
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.
0 views
0 installs
Skill Content
--- name: checking-changes description: 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. ```bash make check ``` This runs formatting, linting, type checking, 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)