setup-automation

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Adopting an automation pack in a game project risks unwanted file changes, untrusted hooks, and misconfigured agents. This Skill keeps inspection and proposal strictly read-only until the user confirms an exact transaction digest, preventing accidental or premature configuration changes. ## Core Features & Use Cases - Read-only project inspection: Runs doctor --project <root> to report the detected OS, engine, existing guidance, active MCP hosts, and constraints without modifying anything. - Digest-gated apply workflow: Generates a plan via scripts/project_setup.py plan, presents proposed AGENTS.md files, roles, permissions, backups, and rollback operations, then applies only after the user confirms the digest verbatim. - Safe rollback support: Produces rollback proposals through pack rollback <transaction-id> that also require a second digest confirmation before execution. - Use Case: A developer adopting the automation pack in a Unity project previews the proposed hooks and agent profiles, confirms the digest, applies the plan, and later rolls it back safely if needed. ## Quick Start Ask the assistant to inspect this game project and propose the optional automation pack setup 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 safely set up automation hooks in a game project?

Run the read-only inspection first, which reports the detected OS, engine, existing guidance, and constraints. Then review the generated plan and confirm the transaction digest verbatim before anything is applied to the project.

How do I preview automation setup without changing 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 configuration is applied.

Which game engines does the automation setup support?

The setup supports one engine value per plan: unity, godot, unreal, browser, or generic. The engine is selected during inspection and passed to the planning script.

Can I undo an applied automation setup?

Yes, a rollback proposal can be generated with the core pack rollback command using the transaction ID. Rollback is never executed without a second digest confirmation, and existing files are preserved through transaction backups.

Why are hooks not active immediately after setup?

Hooks remain disabled until they are separately reviewed and trusted through the /hooks flow. The setup only proposes them and never trusts hooks or writes project files before digest confirmation.