setup-automation

Inspects game projects and proposes Codex hooks, AGENTS.md guidance, and agent profiles with digest confirmation.

13|Updated Jul 30, 2026
One-click install
npx skills add https://github.com/frabcd/codex-ai-game-studio --skill setup-automation-frabcd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-automation
Source: https://github.com/frabcd/codex-ai-game-studio/tree/main/plugins/ai-game-studio-automation/skills/setup-automation
Command: npx skills add https://github.com/frabcd/codex-ai-game-studio --skill setup-automation-frabcd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Adopting automation in a game project risks silently overwriting existing configuration or installing untrusted hooks. This Skill keeps inspection and proposal read-only, then applies changes only after the user confirms an exact transaction digest. ## Core Features & Use Cases - Read-only project inspection: Runs the core doctor command to report OS, engine, existing guidance, active MCP hosts, and constraints without writing files. - Digest-gated apply workflow: Generates a plan with proposed AGENTS.md files, engine-specific agent profiles, permissions, backups, and rollback operations, applying it only after verbatim digest confirmation. - Engine-aware setup: Supports unity, godot, unreal, browser, and generic engine values, selecting matching specialist agents for the project. - Use Case: A developer adopting the automation pack on a Unity project runs the inspection, reviews the proposed hooks and agent TOML files, confirms the digest, and later rolls back the transaction with a second confirmation if needed. ## Quick Start Use the setup-automation skill to inspect this game project and propose the automation pack configuration without changing any files.

Frequently Asked Questions about setup-automation

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

FAQPage Schema
How do I set up Codex automation hooks for a game project safely?

Run the inspection first, which stays read-only and reports OS, engine, existing guidance, and MCP hosts. Review the proposed plan with its digest, then confirm that digest verbatim before anything is applied to the project.

How to preview automation changes without modifying project files?

Request a preview-only run, which stops after presenting the proposal. No plan is written inside the project, no confirmation is solicited, and no files are created or changed.

Which game engines does the automation setup support?

The setup supports five engine values: unity, godot, unreal, browser, and generic. The selected engine determines which specialist agent profiles are included in the proposal.

Can I roll back applied automation configuration?

Yes, rollback is available through the core pack rollback command using the transaction ID reported after apply. A rollback proposal is generated first and requires a second digest confirmation before executing.

Does the setup overwrite existing AGENTS.md or agent files?

Existing files are preserved through the transaction backup created during apply. Agents inherit the active Codex model and permission mode, and no model pins, memory fields, or fixed turn limits are added.