checking-changes
A validation suite to verify code quality, formatting, and tests before finalizing commits.
Install
mkdir -p .claude/skills/checking-changes && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/3424" && unzip -o skill.zip -d .claude/skills/checking-changes && rm skill.zipInstalls to .claude/skills/checking-changes
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
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.Key capabilities
- →Run code formatting checks
- →Execute linting rules
- →Perform type safety validation
- →Run unit tests on uncommitted files
How it works
It triggers a make check command that scans all staged, unstaged, and untracked files for compliance with project standards.
Inputs & outputs
When to use checking-changes
- →Validating code before commit
- →Running lint and type checks
- →Executing unit tests for new changes
- →Ensuring code consistency in a session
About this skill
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)
When not to use it
- →Running checks after every minor edit
- →Replacing full E2E test suites
Limitations
- →E2E tests are excluded by default
- →Requires manual updates for E2E snapshot mismatches
How it compares
It centralizes multiple validation steps into a single command to ensure workspace cleanliness before committing.
Compared to similar skills
checking-changes side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| checking-changes (this skill) | 1 | 5mo | Review | Beginner |
| moai-foundation-quality | 0 | 3mo | No flags | Advanced |
| verification-loop | 0 | 4mo | Review | Intermediate |
| ast-grep-find | 3 | 7mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by streamlit
View all by streamlit →You might also like
moai-foundation-quality
modu-ai
Enterprise code quality orchestrator with TRUST 5 validation, proactive analysis, and automated best practices enforcement
verification-loop
tom237ttkk
A comprehensive verification system for Codex work sessions.
ast-grep-find
parcadei
AST-based code search and refactoring via ast-grep MCP
unit-testing-test-generate
sickn33
Generate comprehensive, maintainable unit tests across languages with strong coverage and edge case focus.
naming-analyzer
davila7
Suggest better variable, function, and class names based on context and conventions.
codex-code-review
tyrchen
Perform comprehensive code reviews using OpenAI Codex CLI. This skill should be used when users request code reviews, want to analyze diffs/PRs, need security audits, performance analysis, or want automated code quality feedback. Supports reviewing staged changes, specific files, entire directories, or git diffs.