PlayCanvas Editor Version Control
SkillDocs & knowledgeUse when working with the PlayCanvas Editor version control system (VCS), managing checkpoints, handling branches, merging histories, or resolving document conflicts.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the PlayCanvas Editor Version Control skill
What this skill tells your AI
The instructions your AI receives, as published by teknokomo/universo-platformo-react in .agents/skills/playcanvas-editor-version-control/SKILL.md and read by ahel’s review.
Use this skill when managing the project version control, committing checkpoints, branching, and resolving scene or asset merge conflicts.
Version Guard
- Schema and operation logs follow PlayCanvas VCS specifications.
- Pinned to the version control panel capabilities of Editor
v2.30.4.
Required Output
Before performing branching or merging operations:
- state current branch and target branch names;
- identify conflicts in scene graphs or asset configurations;
- describe the resolution strategy (keep mine, keep theirs, manual merge).
Workflow
- Create branches as fork pointers of scene/asset states.
- Checkpoints are committed with explicit description messages.
- Merging compares JSON diffs of scene hierarchies and asset models.
- Conflict resolution requires manual user validation before committing the merged state.
Blocking Rules
- Do not attempt automatic merges on binary assets (textures, models). They must fail closed, requiring explicit user selection.
- Do not bypass checkout validations.
- Do not lose document revision history.
- Do not let a merge operation overwrite unsaved local modifications.
Signals
- GitHub stars
- 22
- Forks
- 3
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
playcanvas-editor-version-control- Source
- github.com/teknokomo/universo-platformo-react