checking-changes

star 8

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.

whitphx By whitphx schedule Updated 2/3/2026

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.

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; use make run-e2e-test e2e_playwright/<test>_test.py separately if needed
Install via CLI
npx skills add https://github.com/whitphx/streamlit --skill checking-changes
Repository Details
star Stars 8
call_split Forks 1
navigation Branch main
article Path SKILL.md
More from Creator