skills.rest
alsdmlals4-eng
alsdmlals4-engCOMMUNITY
Explore all skills by this author →
GitHub

managing-game-project-operating-system

Installs, audits, reconciles, migrates, and verifies game project repository operating systems.

Updated Jul 9, 2026
Search Tags:#game development#verification#godot#project governance#repository audit#legacy migration#workspace authority
One-click install
npx skills add https://github.com/alsdmlals4-eng/Base --skill managing-game-project-operating-system-alsdmlals4-eng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: managing-game-project-operating-system
Source: https://github.com/alsdmlals4-eng/Base/tree/main/skills/managing-game-project-operating-system
Command: npx skills add https://github.com/alsdmlals4-eng/Base --skill managing-game-project-operating-system-alsdmlals4-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Game projects accumulate duplicate versioned files, stale references, conflicting authority sources, and unverified third-party tool adoptions. This Skill provides a governed lifecycle for installing new project operating systems, auditing existing ones, reconciling legacy artifacts, migrating approved content, and verifying the whole structure with evidence. ## Core Features & Use Cases - Five Skill Modes: install, audit, reconcile-legacy, migrate, and verify, each with explicit read/write boundaries and approval gates so existing projects are never restructured without sign-off. - Workspace Authority Governance: Enforces a repository-first canon with derived human-facing PDFs, treating Notion and Google Sheets as legacy read-only or compatibility-only migration sources. - Third-Party Provider Contracts: Manages HiGodot exact-pin adoption, GUT deterministic testing, and Hera live-QA boundaries with canary, regression, and rollback evidence requirements. - Use Case: After merging a large restructuring PR, run the verify mode to re-read the exact new main, adversarially review the full approved scope, correct findings through new branches, and confirm zero remaining work before reporting completion. ## Quick Start Audit my existing game project repository and produce a legacy file reconciliation table without making any changes.

Frequently Asked Questions about managing-game-project-operating-system

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

FAQPage Schema
How do I audit an existing game project repository structure?▼

Use the audit Skill Mode, which runs in PLAN or REVIEW Work Mode and performs no bulk changes. It produces a responsibility map, duplicate and conflict lists, a provider inventory, and a user-approved disposition table before any modification.

How do I migrate a game project from Notion or Google Sheets to a repository?▼

Use the migrate mode with an approved migration table. Legacy sources are audited as UNIQUE, DUPLICATE, or OBSOLETE, unique material is transferred to repository canon with readback and tests, and only then is the original lifecycle decided.

Can this Skill delete old versioned files like v2 or final copies?▼

Deletion requires the reconcile-legacy mode with explicit user approval, succession of all unique information to the current canon, updated references or compatibility stubs, verified recovery paths, and no blocking findings from reference-freshness audits.

Does it support Godot tooling like HiGodot, GUT, and Hera?▼

Yes. HiGodot is the sole persistent Godot authoring authority with exact pins and loopback-only networking, GUT handles deterministic GDScript tests when adopted, and Hera is restricted to live QA with source-delta guards. Floating latest versions are forbidden.

What happens after a merge to the main branch?▼

The verify mode runs a post-merge adversarial progress loop: it re-reads the exact new main, reviews the full approved scope, corrects valid findings through new branches and PRs, and recalculates remaining work before declaring completion.

When should this Skill not be used on a project?▼

Do not force a new install structure onto an existing project with its own documents and history; switch to audit instead. It also does not perform actual runtime deployment, legal review, or platform approval, which remain NOT_RUN.

Related Skills

Explore More Product & Management Skills→
athina-aiathina-ai
1.1k

client-package-notion

Package client project assets into a structured Notion page with linked Google Sheets.

Official
Advanced
MozurokMozurok
6

godot-runtime-verify

Runs built Godot scenes and classifies runtime errors to gate slice acceptance behavior.

Community
Advanced
WalliieeWalliiee

freshness-watch

Detect stale workspace artifacts and missed maintenance cycles in agent workspaces.

Community
Intermediate
burgebjburgebj

octopus-quick

Execute small software changes with atomic commits and state tracking.

Community
Intermediate