القائمة
Run all tests (vitest), lint (eslint), and commit changes. Use when user says "test and commit", "run tests and commit", "verify and commit", or "CI and commit".
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Kill all running local development processes (TanStack Start dev, email service, PostgREST), wait for termination, then restart them. Use when user says "boot local", "restart local", "reboot dev", or needs to refresh local services.
Run user story acceptance tests using Playwright browser automation. Executes test steps from user-stories/*.md files and reports pass/fail status with reasons. Use when user says "run user stories", "test user stories", "acceptance test", or "run e2e tests".
Scrape, load, and manage the base recipe pool for the meal planner. Handles scraping Swedish recipe sites, loading into database, and verifying integration. Use when user says "scrape recipes", "load base recipes", "base recipe pool", or "update base recipes".
Evaluate test coverage and create appropriate tests based on risk assessment. Use when user says "build tests", "update tests", "add test coverage", "write tests for this", or "improve test coverage".
Reviews code quality, pattern adherence, and architecture with red-team validation. Use when user says "check your code", "code quality review", "is this well-written", or "review code quality". Different from check-your-work which finds bugs.
Orchestrates 6 quality agents in parallel (duplicate-detector, user-intent, deep-bug-hunter, security, performance, correctness) with severity validation. Use when user says "check your work", "review what we wrote", "quality check", or after writing new features.
| name | test-and-commit |
| version | 1.0.0 |
| description | Run all tests (vitest), lint (eslint), and commit changes. Use when user says "test and commit", "run tests and commit", "verify and commit", or "CI and commit". |
| allowed-tools | Read, Write, Edit, Bash, Grep, Glob, AskUserQuestion |
| context | fork |
Run tests, lint, then commit — ensuring code quality before every commit.
<when_to_use>
Invoke when user says:
</when_to_use>
| Phase | Action | Gate |
|---|---|---|
| 1 | Run unit tests | Must pass |
| 2 | Run API integration tests | Required for schema changes |
| 3 | Lint all packages | Must pass |
| 4 | Review changes for commit | User approval |
| 5 | Commit changes | Only if all pass |
Read .claude/skills/test-and-commit/references/execution-phases.md for detailed phase instructions, then execute sequentially.
<quick_reference>
# Run unit tests
pnpm check:test
# Run API tests (requires test Docker)
pnpm check:api
# Lint
pnpm check:lint
# All checks (lint + test)
pnpm check
# Git status
git status
</quick_reference>
<approval_gates>
| Gate | Phase | Question |
|---|---|---|
| Pre-existing failures | 1 | "Tests failed but unrelated to changes. Skip or fix?" |
| Commit scope | 4 | "Commit all together or split?" |
</approval_gates>