Skip to main content
skill CX Codex

checking-changes — Claude Code skill: checks before commit

checking-changes is a Claude Code skill that runs code checks after a set of changes, before a commit or the end of a work session. It covers Python backend and TypeScript frontend work.

Apache-2.0 122 installs ★ 46,474 updated 2026-10-25

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add streamlit/streamlit --skill checking-changes -a claude-code
Open on GitHub

What checking-changes does

The skill runs make check against all uncommitted files, including staged, unstaged, and untracked changes. The command formats code, runs lint and type checks, uses Knip to find unused exports and dependencies, and runs unit tests. Run it at the end of a work session or after a set of changes, rather than after each small edit.

When checks report errors, fix them and run the command again; work is complete once it passes. E2E tests are excluded by default. To include changed E2E tests, run E2E_CHECK=true make check. E2E snapshot mismatches can be ignored while iterating; for a pull request, add the update-snapshots label and merge the snapshot PR opened by the workflow.

What it helps with

  • check formatting and lint before committing
  • catch type errors and unused exports
  • run unit tests on uncommitted files
  • rerun checks after fixing reported issues

Example prompts for the agent

  • Run checks on all my changes before I commit.
  • Check my Python changes and fix any reported errors.
  • Include changed E2E tests in the checks.

How to install checking-changes

1Skills CLI (Vercel)

npx skills add streamlit/streamlit --skill checking-changes -a claude-code

2Manually: put the files in place

~/.claude/skills/checking-changes/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/checking-changes/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about checking-changes

How do I install checking-changes in Claude Code?

Run npx skills add streamlit/streamlit --skill checking-changes -a claude-code. The skill file is installed at ~/.claude/skills/checking-changes/SKILL.md.

What does checking-changes do?

It runs formatting, lint, type, Knip unused-export and dependency checks, and unit tests on uncommitted files. If checks fail, fix the reported issues and run them again.

How do I include E2E checks?

Run E2E_CHECK=true make check to add changed E2E tests to the check.

Source text

SKILL.md · Apache-2.0
---
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, 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 while iterating. On a pull request, add the `update-snapshots` label and merge the snapshot PR the workflow opens.

© streamlit · Apache-2.0 · streamlit/streamlit

Similar skills

All skills for Testing and QA →

From the same set6

Project sponsors

Companies that keep this analytics open