mcpField
R
roblox-publish-checklist

roblox-publish-checklist

github.com/tabooharmonyTesting & quality1382.0k installsUpdated 2w ago
Repository

About roblox-publish-checklist

roblox-publish-checklist is a release-readiness skill for teams publishing or updating Roblox experiences. It organizes risk-based tests, evidence requirements, and rollback planning into explicit readiness outcomes.

Key features

  1. 01Release scope and gate classification
  2. 02Risk-based checks for persistence and remotes
  3. 03Testing of shipped surfaces and devices
  4. 04Evidence required for each passed gate
  5. 05Readiness status and rollback reporting

Use cases

  1. 01Reviewing a live experience update
  2. 02Checking persistence or purchase changes
  3. 03Validating device and input coverage
  4. 04Recording release blockers and evidence

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/tabooharmony/roblox-brain --skill roblox-publish-checklist

After installing, type/roblox-publish-checklistin Claude Code to confirm it loaded.

Bundled filesreferences/full.md

Details

From the project README

Roblox Publish Checklist

When to Load

Load before publishing or updating a live experience. Test the surfaces and risks the change introduces.

Quick Reference

1. Define the release

Record the changed places, scripts, assets, configuration, schemas, products, supported devices, and rollback path. Classify each gate as required, conditional, or not applicable before testing.

2. Block on high-consequence failures
  • Persistence changed: load, save, migration, duplicate-session, disconnect, and shutdown behavior. Load roblox-data or roblox-server-data.
  • Remotes or authority changed: validate types, bounds, state, ownership, replay, and abusive frequency. Load roblox-networking and roblox-security.
  • Purchases changed: test durable, idempotent receipt grants and retries. Load roblox-monetization.
  • Cloud auth or webhooks changed: verify secrets, scopes, callback state, retries, signatures, and deduplication. Load roblox-cloud.

A failed high-consequence gate means NOT READY. Do not average it into a percentage. Precedence: user approval authorizes an otherwise permitted action; it does not satisfy a mandatory policy and does not turn a failed or unverified gate into PASS.

3. Exercise the shipped surface
  • Run one normal flow plus failure, retry, leave/rejoin, and rapid-input cases relevant to the change.
  • Test every supported input mode and representative viewport/device tier.
  • Measure errors, memory, frame/network cost and streaming.
  • Verify focus, touch targets, readable contrast, non-color state cues, reduced motion, and localized overflow where applicable.
  • Confirm Dashboard metadata, permissions and policy; after publishing, verify the version actually serving players.
4. Require evidence

Every PASS cites a test, log, profiler capture, readback, screenshot, or dashboard inspection. UNVERIFIED if unavailable; approval is not evidence.

Output

READY, NOT READY, or READY WITH ACCEPTED RISK; blockers first, then warnings, unverified gates, evidence, rollback plan, and skipped gates with reasons.

Details: references/full.md

Comments

Markdown supported