check-and-test

Featured

Run lint checks (ruff for Python, Biome for TS/JS), type checks (pyright for Python, tsc for TS/JS), and the standard pytest tiers (unit + e2e + tests skipped during pre-commit). Investigates failures to determine if they are application bugs or test issues, and fixes application bugs rather than weakening tests. Does not run paid-LLM real-API tests or scenario probes from the test-* command family.

Testing & QA 756 stars 83 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 92/100

Stars 20%
96
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Check and Test Run the standard check-and-test flow (lint + type-check + pytest tiers), including tests normally skipped during pre-commit hooks. ## Overview This command runs the standard check-and-test tiers: - **Python lint checks** via ruff (code quality, security, complexity) - **Python type checks** via pyright (type safety) - **TypeScript/JavaScript lint checks** via Biome (code quality, formatting, import sorting) - **TypeScript/JavaScript type checks** via tsc (type safety) - **Unit tests** in `reflexio/tests/` (excluding e2e and tests under reflexio/tests/server/llm/) - **E2E tests** in `reflexio/tests/e2e_tests/` (skip all the low priority test by NOT setting RUN_LOW_PRIORITY env variable) - **Tests skipped during pre-commit** (those decorated with `@skip_in_precommit`) The key difference from pre-commit is that `PRECOMMIT` env var is NOT set, so all tests run. ## Prerequisites Before running tests, activate the virtual environment: ```bash source .venv/bin/activate ``` ## Test Execution **IMPORTANT**: Run all tests sequentially using `-n 0` to avoid test conflicts. The default pytest config uses parallel execution (`-n auto`), but this can cause race conditions and shared state issues between tests. ### Step 0: Run Lint and Type Checks Run lint and type checks across the full codebase before running tests. **0a. Ruff auto-fix:** ```bash ruff check --fix reflexio/ ruff format reflexio/ ``` **0b. Ruff remaining errors:** ```bash ruff check reflexio/ ``...

Details

Author
ReflexioAI
Repository
ReflexioAI/claude-smart
Created
3 months ago
Last Updated
today
Language
Python
License
Apache-2.0

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Testing & QA Listed

test-check

MUST use after implementing new features or bug fixes, when user asks 'run the tests', 'are tests passing?', 'test this', or before any deployment step. Also trigger when tests were previously failing and fixes were applied.

0 Updated today
lethilu4796
Testing & QA Listed

tests

Fixes failing tests and lint/type errors, audits test-suite quality with a fleet of specialist reviewers, or drives coverage — for any project configured with a supermodo skills.config.json. Modes: `tests` (default) fixes every failure tier by tier (unit, integration, E2E, lint); `tests audit [scope]` spawns parallel specialist reviewers (spec-alignment, assertion-strength, corner-cases, coverage-balance, and a domain lens derived from the project's docs), runs mutation probes where configured, and adversarially verifies every finding with a second model before reporting; `tests coverage` drives coverage to the configured target with a balance check. Use whenever the user mentions failing tests, lint errors, "make tests pass", green build, flaky tests, test quality, weak or missing tests, corner cases, coverage, mutation testing, or asks whether the tests actually protect the core logic — even without "/tests".

1 Updated 3 days ago
supermodo
Testing & QA Listed

testing

WRITE, RUN, or DEBUG tests for the project's code -- pytest (Python), Jest/RTL (TypeScript), Playwright (E2E), and deployment config testing. NOT for finding coverage gaps or untested modules -- that read-only gap analysis belongs to test-coverage. NOT for CI pipeline configuration (use deployment).

3 Updated today
atretyak1985