Menu
Run the repository test suite and lint checks, report results, and note any failures or required approvals.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run and debug specify-poker end-to-end behavior against the docker-compose stack using Playwright (apps/ui/tests/e2e), including stack bring-up, readiness checks, and log/trace triage with docker compose and Grafana Loki/Tempo.
Integrate and troubleshoot Grafana Mimir as the Prometheus-compatible metrics backend in specify-poker’s docker-compose stack, including OTel Collector scraping + remote_write, Grafana datasource provisioning, PromQL validation, and diagnosing ring/remote-write startup issues. Use when replacing Prometheus, debugging missing metrics/service map, or fixing Mimir/otel-collector compose failures.
Triage and debug specify-poker issues using the LGTM stack (Grafana + Loki + Tempo + Mimir) and docker compose logs, centered on OpenTelemetry traceId correlation across gateway/game/balance/player/event/notify; use for failing E2E tests, runtime 5xx/gRPC INTERNAL errors, auth/join-seat failures, or production-like compose debugging.
Troubleshoot Grafana Tempo traces and the Tempo Service Map in specify-poker’s docker-compose LGTM stack. Use when Grafana shows empty traces/service map, service-map edges look slow, Tempo search errors like “invalid start … value out of range”, or trace panels are missing data.
Debug stalled poker hands and table UI issues in specify-poker (stuck on preflop, turn never advances, hand timers not firing, players can't see their own hole cards, duplicate seating, invalid hand.turn/seat status) using Gateway APIs, Game Service state, and docker-compose logs.
Create or expand consumer-centric test suites and coverage for microservices (gRPC/HTTP handlers, service flows, event consumers, caches, jobs, observability) while preserving behavior and hitting coverage targets. Use when asked to add tests, raise coverage, or validate consumer-facing behavior across services.
| name | run-tests-lint |
| description | Run the repository test suite and lint checks, report results, and note any failures or required approvals. |
Use this skill when the user asks to run tests, check linting, or validate CI-style checks.
source ~/.zshrc then nvm use 20 to select Node.js 20 LTS.npm testnpm run lintpackage.json scripts and report the gap.