// Rules for interacting with local version control and remote platforms (GitHub, GitLab, Forgejo).
Visual target generation, risk-first game decomposition, and verification criteria. Load at pipeline start before architecture.
Manage tasks, epics, and bugs. Default to remote CVS platforms. Use local .issues/ ONLY if ISSUE_TRACKING_FS=1 in .env.ai. Require cvs skill.
Godot MCP servers reference — editor, diagnostics, testing, docs, runtime. Load when doing Godot game dev.
When this skill is loaded, the developer follows the Red-Green-Refactor cycle. The orchestrator loads this skill when the user requests TDD.
Godot 4 project scaffolding — project.godot, architecture notes, script stubs, scene builders, build order. Load after game decomposition.
Task implementation workflow, test harnesses, screenshot/video capture, visual debugging. Load before implementing game tasks.
| name | cvs |
| description | Rules for interacting with local version control and remote platforms (GitHub, GitLab, Forgejo). |
Rules for interacting with local version control and remote platforms (GitHub, GitLab, Forgejo).
.env.ai)Check .env.ai for tool and platform overrides before starting:
CVS_TOOL: Local version control CLI. git (default) or jj.CVS_PLATFORM: Remote platform. github (default), gitlab, or forgejo.ISSUE_TRACKING_FS=1: Force local .issues/ tracking instead of remote.cvs_github_*, cvs_gitlab_*, cvs_forgejo_*) or CLI fallback (gh, glab, forgejo-cli) for issues, PRs, and comments.CVS_TOOL for commits, branches, and pushes.issue-tracking skill.| Platform | Detection Hint | MCP Prefix | CLI Fallback |
|---|---|---|---|
| GitHub | github.com | cvs_github_... | gh |
| GitLab | gitlab.com | cvs_gitlab_... | glab |
| Forgejo | forgejo / gitea / codeberg.org | cvs_forgejo_... | forgejo-cli |