skills.rest
curtismu7
curtismu7COMMUNITY
Explore all skills by this author →
GitHub

verify-ai-demo2

Diagnose testing, Docker deployment, and verification pitfalls in the AI-DEMO2 repository.

1|Updated Jun 25, 2026
Search Tags:#vitest#devops#jest#git worktree#docker#deployment verification#test debugging
One-click install
npx skills add https://github.com/curtismu7/AI-DEMO2 --skill verify-ai-demo2-curtismu7
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-ai-demo2
Source: https://github.com/curtismu7/AI-DEMO2/tree/main/.claude/skills/verify-ai-demo2
Command: npx skills add https://github.com/curtismu7/AI-DEMO2 --skill verify-ai-demo2-curtismu7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Changes in the AI-DEMO2 repo often appear correct, tested, and merged yet never actually run in the live Docker stack, and worktree-based test runs fail for environmental reasons that look like code bugs. This Skill documents the verified operational gotchas so you can prove a code path executes, deploy changes correctly, and avoid misdiagnosing infrastructure noise as regressions. ## Core Features & Use Cases - Worktree test setup: Bootstrap node_modules in fresh git worktrees via scripts/bootstrap-worktree.sh and avoid the jest --testPathIgnorePatterns trap that drags live-stack suites into unit runs. - Docker deploy correctness: Distinguish bind-mounted services (restart suffices) from image-built services (rebuild required), including the dual scope-topology.json copies needing different deploy verbs. - Live verification discipline: Prove code paths run via container log markers, verify deploys by content rather than stamps, and detect when a concurrent agent session's deploy invalidated your live run. - Use Case: After merging a topology change, you grep your own diff marker inside the authz-server container, rebuild only the image-based services, and restart ping-gateway — instead of shipping half the change while every container reports healthy. ## Quick Start Ask the agent to verify whether your merged change is actually running in the AI-DEMO2 Docker stack and follow the worktree and deploy guidance it applies.

Frequently Asked Questions about verify-ai-demo2

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run jest tests from a git worktree in this repo?▼

Run bash scripts/bootstrap-worktree.sh first to symlink node_modules from the main checkout, then run CI=true npm test -- --forceExit --maxWorkers=4. Do not pass --testPathIgnorePatterns, since the config self-detects worktrees and the flag replaces the exclusion list.

Why does my Docker service restart not pick up code changes?▼

Only demo-api-server and ui bind-mount source; every other service gets code from a built image, so restart recreates the container from the old image while reporting healthy. Rebuild image-based services with ./run-docker.sh build <service> and verify by grepping a marker from your own diff inside the container.

Why do different test suites fail on each run of identical code?▼

Disjoint failures across runs indicate parallel-load contention, not a regression — a real regression fails the same suite twice. Re-run the failing suite in isolation before treating it as a finding, using npx vitest run <file> for the UI side.

Does docker compose restart apply .env changes?▼

No. Environment variables are baked in at container creation and are not re-read on restart. Use docker compose up -d <service> to recreate the container so env changes take effect, then confirm with docker compose logs.

How do I verify a merged feature actually runs in production code paths?▼

Grep container logs for a marker from the function, since code existing in a file is not evidence it executes — several merged features sat on paths requests never take. Add a log marker, drive the path, and confirm the guard fails when the fix is reverted.

What should I check when a live UI run fails with a 404 or 502?▼

Check whether another agent session deployed mid-run by inspecting container start timestamps with docker inspect before and after the run. A deploy restarting ui or demo-api-server kills in-flight requests with no matching server logs, which mimics a routing bug.

Related Skills

Explore More Software Engineering Skills→
caseymanoscaseymanos

local-ssl

Automates creation and trust of local SSL certificates for development environments.

Community
Advanced
paulinett1508-devpaulinett1508-dev

Git-Commit-Push

Commit and push code with pre-push validations and main merge.

Community
Advanced
orient-botorient-bot

mcp-debugging

Inspect MCP server logs, trace requests via correlation IDs, and analyze tool performance.

Official
Intermediate
diegoliriodiegolirio

sec-multi-monorepo-kotlin-nextjs-hybrid-pipeline

Configure a unified CI/CD pipeline for Kotlin Spring Boot and Next.js monorepos.

Community
Advanced