cs2match-local-update

Rebuilds and reloads local Docker frontend and Nakama Go backend services.

Updated Jun 6, 2026
One-click install
npx skills add https://github.com/jonathanlin768/CS2Match-Nakama --skill cs2match-local-update-jonathanlin768
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cs2match-local-update
Source: https://github.com/jonathanlin768/CS2Match-Nakama/tree/main/.agents/skills/cs2match-local-update
Command: npx skills add https://github.com/jonathanlin768/CS2Match-Nakama --skill cs2match-local-update-jonathanlin768

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Updating a local CS2Match development environment requires rebuilding the Go plugin, restarting Nakama, and recreating the frontend container in the correct order. This Skill automates that workflow so natural-language requests like "帮我更新前端" or "帮我更新后端" trigger the right build and verification steps without manual command recall. ## Core Features & Use Cases - Targeted Updates: Distinguishes frontend-only, backend-only, and combined update requests, rebuilding only the requested side. - Backend Workflow: Compiles the Go plugin via the repository build scripts, restarts Nakama with Docker Compose, and verifies plugin loading through container status and logs. - Frontend Workflow: Rebuilds the frontend image with --no-cache, force-recreates the container, and checks that the service responds on port 3000. - Use Case: After editing Go server code, ask the AI to update the backend; it compiles backend.so, restarts Nakama, inspects logs for plugin-loading errors, and reports whether the update actually succeeded. ## Quick Start Ask the AI to update the backend and frontend of the local CS2Match project and verify both services are running.

Frequently Asked Questions about cs2match-local-update

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

FAQPage Schema
How do I update the Nakama Go backend plugin locally?

Run the repository build script (server/build.sh on Linux/macOS/WSL2 or server\\build.bat on Windows), then run docker compose up -d db nakama and restart the nakama service. Verify success by checking docker compose ps and the Nakama logs for plugin-loading errors.

How do I rebuild the frontend Docker container without cache?

Run docker compose build --no-cache frontend, then docker compose up -d --no-deps --force-recreate frontend. The no-cache build ensures the image is not created from a stale cached source layer, and you can verify the result at http://localhost:3000.

Why does Nakama fail to start after rebuilding the Go plugin?

Nakama fails to start when the plugin compilation produced errors or the .so artifact is incompatible. Check docker compose logs --tail 100 nakama for plugin-loading errors, and never restart Nakama with an old artifact after a failed build.

Can I update only the frontend without touching the backend?

Yes, a frontend-only request triggers only the frontend rebuild and container recreation. The workflow explicitly avoids rebuilding the unrequested side and does not run Luban config generation unless explicitly asked.

When should I use update-local-config.ps1 instead of a normal update?

Use scripts/update-local-config.ps1 only when you explicitly need to publish changed Excel or Luban configuration. It performs Luban generation plus both frontend and backend updates, which a standard update request does not trigger.