gm-accept

Present GodotMaker tag build evaluation results for user acceptance decisions.

511|44|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/RandallLiuXin/GodotMaker --skill gm-accept
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gm-accept
Source: https://github.com/RandallLiuXin/GodotMaker/tree/main/skills/core/gm-accept
Command: npx skills add https://github.com/RandallLiuXin/GodotMaker --skill gm-accept

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents you from sealing the wrong build by presenting the tag’s evaluation results, screenshots, and reviewer triage data so you can accept or request fixes before finalizing.

Core Features & Use Cases

  • Per-tag acceptance gate: Confirms only the current tag (vX.Y.Z) is ready, without claiming the entire game is complete.
  • Grounded review package: Summarizes evaluation outcomes, unit/E2E test status, known limitations, and existing screenshot evidence for fast verification.
  • Decision tracking & safe stopping: Records your accept/fix/done decision into .godotmaker/stage.jsonl and provides explicit guidance for the next step (/gm-finalize, /gm-fixgap, or resume later).

Quick Start

Run /gm-accept to present the current tag’s evaluation summary and ask you whether to approve, fix issues, or stop for now.

Frequently Asked Questions about gm-accept

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

FAQPage Schema
How do I review and accept a game tag build in Godot?

To accept a game tag build in Godot, run /gm-accept to aggregate evaluation status, plan completion, known limitations, and evaluator screenshots into a single review package. It appends your decision to `.godotmaker/stage.jsonl` and guides the next action.

What is per-tag acceptance workflow for iterative game development?

Per-tag acceptance workflow is a review checkpoint that confirms if a specific game tag build (vX.Y.Z) is ready to be sealed or archived. It aggregates evaluation outcomes, test status, known limitations, and screenshots to prevent finalizing the wrong build.

How do I finalize a game tag after evaluating test results and screenshots?

To finalize a game tag after evaluation, run /gm-accept to present the current tag's evaluation summary and screenshot evidence. You can then choose to approve, request fixes via /gm-fixgap, or seal the tag using /gm-finalize.

Does the GodotMaker acceptance workflow require specific stage or evaluation files?

Yes, the GodotMaker acceptance workflow requires explicit invocation via /gm-accept and enforces preconditions by checking existing stage and evaluation files. It uses these files to aggregate evaluation status and known limitations for your review.

When should I request fixes instead of sealing a game tag during acceptance?

You should request fixes instead of sealing a game tag when the aggregated evaluation results, unit/E2E test status, or reviewer triage data reveal issues. Run /gm-accept to review the evidence, then choose the fix option to trigger /gm-fixgap for corrections.