Menu
Run project tests. Use after modifying code to catch regressions before committing.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Check for drift between spec.md, plan.md, tasks.md, and the actual code. Reports the gaps; does not fix them.
Run a category-specific quality pass (security / performance / accessibility / i18n / privacy / observability) against the current plan and code.
Surface [NEEDS CLARIFICATION] markers in spec.md (or plan.md) to the user, one at a time, and edit the file with the answers.
Bootstrap or amend constitution.md (framework, preset, or project). Inspects existing project context first; enforces the amendment process: issue first, one article per PR, reviewer non-author.
Print the pipeline quick-reference — a one-screen summary of every /aia:* command and its hand-offs, prefixed by a state-aware "Próximo passo" line.
Execute an approved plan + tasks list by dispatching one fresh subagent per task and applying two-stage review (spec compliance, then code quality) before moving on.
| name | run-tests |
| description | Run project tests. Use after modifying code to catch regressions before committing. |
| disable-model-invocation | true |
| allowed-tools | Bash, Read, Grep |
| argument-hint | [backend|frontend|mobile|all] [--file path] [--app appname] |
Run the test suite for the project. Default runs all layers.
/run-tests — Run all layers/run-tests backend — Django backend tests/run-tests frontend — React frontend tests/run-tests mobile — React Native (RNTL) mobile tests/run-tests backend --app accounts — Specific Django app/run-tests backend --file tests/ai/test_service.py — Specific test file/run-tests frontend --file src/__tests__/Component.test.tsx — Specific test filecd backend && pytest --tb=short
# Specific app:
cd backend && pytest tests/<app>/ --tb=short
# Specific file:
cd backend && pytest <path> -v
# With coverage:
cd backend && pytest --cov=. --cov-report=term-missing
cd frontend && npx jest --no-coverage
# Specific file:
cd frontend && npx jest --no-coverage <path>
# Watch mode:
cd frontend && npx jest --watch
cd <mobile-dir> && npx jest --no-coverage
# Specific file:
cd <mobile-dir> && npx jest --no-coverage <path>
cd frontend && npx tsc --noEmit
# Backend
cd backend && ruff check .
# Frontend
cd frontend && npm run lint
$ARGUMENTS (default: all)systematic-debuggingSuccess:
✓ Backend: 87 passed in 4.2s
✓ Frontend: 23 passed in 8.1s
✓ TypeScript: no errors
Failure:
✗ Backend: 2 failed, 85 passed
FAILED tests/autodev/test_pipeline.py::test_spec_generation - AssertionError
FAILED tests/ai/test_service.py::test_litellm_fallback - ConnectionError
→ Recommend: run systematic-debugging on these failures
Document any known flaky tests here when discovered:
# Add entries as: test_name — reason — since version