publish-review
Skill9 starsChanged 7 months agoMITView on GitHub
Pre-publish review checklist for a Roblox experience update. Covers DataStore readiness, exploit checks, performance, content policy compliance, metadata, and rollback planning.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- pero3dev/ai-agent-librarytheir own version, first seen Nov 4, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- pero3dev/ai-agent-library★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository51 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- asset-auditSkill
- asset-from-imageSkill
- balance-checkSkill
- brainstormSkill
- bug-reportSkill
- changelogSkill
- code-reviewSkill
- datastore-reviewSkill
- design-reviewSkill
- design-systemSkill
- doctorSkill
- economy-auditSkill
- estimateSkill
- exploit-checkSkill
- gate-checkSkill
- gddSkill
- generate-assetSkill
- hotfixSkill
- launch-checklistSkill
- luau-lintSkill
- map-systemsSkill
- milestone-reviewSkill
- monetization-modelSkill
- onboardSkill
- patch-notesSkill
- perf-profileSkill
- project-stage-detectSkill
- prototypeSkill
- release-checklistSkill
- remotes-auditSkill
- retention-analysisSkill
- retrospectiveSkill
- reverse-documentSkill
- scope-checkSkill
- sprint-planSkill
- startSkill
- studio-inspectSkill
- studio-screenshotSkill
- studio-testSkill
- team-combatSkill
- team-economySkill
- team-polishSkill
- team-releaseSkill
- team-uiSkill
- tech-debtSkill
- wiki-ingestSkill
- wiki-lintSkill
- wiki-querySkill
- wiki-seedSkill
- wiki-updateSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Before publishing an update to Roblox, verify ALL of the following:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/publish-review — Pre-Publish Checklist
Before publishing an update to Roblox, verify ALL of the following:
Delegate to: release-manager (with qa-lead, exploit-security-specialist, performance-analyst for verification)
1. Code Quality
- All code reviewed (no TODO/FIXME/HACK remaining for this release)
- No
print()debug statements in production code - No test/debug features enabled
- All deprecated API usage removed (wait, spawn, delay)
2. Data Safety
- DataStore schema changes are backwards-compatible OR migration tested
- Session locking functioning correctly
- BindToClose handler tested (simulate server shutdown)
- No data loss possible during update rollout
3. Security
/exploit-checkpassed with no Critical findings- All remotes validated server-side
- No sensitive logic exposed to client
4. Performance
- Server heartbeat stable (< 30ms per frame)
- Client FPS acceptable on low-end devices (> 30 FPS mobile)
- Memory usage within budget (< 2GB server, < 800MB client mobile)
- No memory leaks (test with 30-min session)
5. Content Policy
- No Roblox ToS violations (violence, gambling, inappropriate content)
- All text is chat-filter safe (no hardcoded profanity)
- Age-appropriate content
6. Experience Configuration
- Game icon updated (512x512)
- Thumbnails updated (if changed)
- Description updated
- Social links configured
- Max players set correctly
- Genre tags appropriate
7. Rollback Plan
- Previous version identified (what to revert to if something breaks)
- DataStore rollback procedure documented (if schema changed)
- Team aware of monitoring procedures post-publish
8. Analytics & Monitoring
- Analytics events updated for new features
- Dashboards set up to watch post-publish metrics
- Alert thresholds configured (crash rate, error rate)
- First 24-hour monitoring plan in place
9. Patch Notes & Communication
- Patch notes written and reviewed (via
/patch-notes) - Social media posts drafted (if applicable)
- Discord/community announcements drafted
- Content creators notified if the update is significant
Output
Checklist with pass/fail for each item. Block publish recommendation if any Critical item fails.
# Publish Review: [Version]
**Date**: YYYY-MM-DD
**Version**: X.Y.Z
**Reviewer**: [user]
## Critical Items
- [✅/❌] Item 1
- [✅/❌] Item 2
## Recommendation
[✅] **APPROVED FOR PUBLISH**
[⏸️] **HOLD — blockers listed below**
[❌] **REJECTED — critical issues must be resolved**
## Blockers (if any)
1. [Specific issue, owner, ETA]
## Post-Publish Monitoring
- Watch dashboards for first 2 hours
- Post-publish review in 24 hoursSave to production/releases/publish-review-<version>.md on approval.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

