Guide testers through structured playtest verification for implemented game features.
npx skills add https://github.com/AirMile/claude-config --skill game-verify
Please help me install this Agent Skill. Skill: game-verify Source: https://github.com/AirMile/claude-config/tree/main/skills/game-verify Command: npx skills add https://github.com/AirMile/claude-config --skill game-verify
Human playtests for implemented game features after the build are time-consuming and prone to inconsistent results. This Skill guides testers through a structured verification flow, aggregates feedback, and drives iterative fix loops until acceptance criteria are met.
Run /game-verify after /game-build to start the verification loop and begin structured tester feedback.
High-intent search queries and answers about installing and using this skill.
Playtest verification is automated by guiding testers through a structured feature checklist, categorizing feedback into testable and subjective items, and driving iterative fix loops. This Skill coordinates testing using feature.json and tests.checklist files to ensure traceable fixes.
The best way to structure game-testing feedback is to automatically parse and categorize it into TESTABLE, MEASURABLE, and SUBJECTIVE buckets. This provides clear next steps for each item and drives re-test baselines until acceptance criteria are met.
Post-build feature verification in Godot runs by executing the verification loop after your game build. It relies on feature.json, tests.checklist, and baselines to coordinate testing, capture feedback, and ensure regression safety.
Yes, structured playtest verification complements GUT tests by handling human feedback after automated unit tests pass. It uses re-test baselines and optional cross-requirement scenario generation to ensure regression safety alongside automated testing.
No, it requires feature.json and tests.checklist files to coordinate testing. It relies on these predefined baselines to guide testers through the verification flow, capture structured feedback, and drive iterative fix loops.
Automated feedback parsing should be used when you need consistent, traceable categorization of playtest notes into TESTABLE, MEASURABLE, and SUBJECTIVE items. It prevents inconsistent results and drives clear next steps for iterative fixes.
AirMileConvert game feature ideas into structured specifications for Godot 4.x projects.
lovecrushfamilyAutomate iterative gap detection and fixing in software specifications, tests, and UX.
Totes-MickGOATsProvides Godot Engine testing blueprints with GUT for TDD and CI/CD integration.
LordKuperGenerate playtest report templates and analyze notes into structured findings.
