القائمة
Review the current changes against project rules, conventions, and quality standards. Use when the user asks to review changes, check the diff before committing, or look over recent edits.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Scaffold a new blit386-demos demo file with the correct next NNN slug, the standard demo class pattern, and beginner-friendly comments. Use when the user wants to add, create, or scaffold a new demo or example, or says 'make a demo for X' or 'add a demo that shows Y'.
Create a pull request with automatic quality checks, a conventional commit, and the gh CLI. Use when the user wants to open a PR or push a branch for review.
Comprehensive pre-push review combining automated checks, a security audit, AI code analysis, and a PR-ready summary. Use before pushing significant changes or opening a pull request.
Run all quality checks (format, lint, spellcheck, knip, docs:links, build) before committing or pushing. Use when the user wants to verify the code is ready to commit or run every check at once.
Run cspell across the project, fix typos, and add legitimate words to the dictionary. Use when the user wants to spellcheck, fix spelling, or resolve cspell failures.
Run MCP security preflight and documented fallbacks for blit386-demos security workflows.
| name | demos-review |
| description | Review the current changes against project rules, conventions, and quality standards. Use when the user asks to review changes, check the diff before committing, or look over recent edits. |
Review current changes against project rules and quality standards.
/demos-review
git diff to see all unstaged modificationsgit diff --cached to see staged changespnpm run lint – Report any lint issuespnpm run spellcheck – Check for spelling issuespnpm run build – Confirm the production build succeeds (deployment gate for Cloudflare Pages)src/*.js demo files: every logical block must have a plain-English comment explaining
what it does and why. Comments that only restate the code (e.g., "// increment counter" above i++) are not
sufficient. Math functions, loop structures, and engine API calls must be explained in plain language.src/shared/ui.js (applyTheme() in init() before BT.paletteSet(),
ui.tick() as the first line of update(), ui.begin() / widgets / ui.end() in render()). Never hand-rolled
panels, buttons, or HUD text colors (018-flurry is the only intentional exception: immersive screensaver, no demo
HUD)ui.button with a { key } binding, directional input also
has ui.dpadWidget() and/or ui.swipe(), and hardware-showcase demos (028, 031, 035) show a warm "needs a
keyboard/gamepad" label when ui.hasTouch() is trueBT.isKeyPressed, BT.isKeyReleased, BT.inputString, kit { key } bindings via
ui.tick()) are read from update(), never render()BT.soundPlay() before unlock is dropped;
BT.musicPlay() is queued), and audio demos gate their prompt on BT.isAudioUnlockedNNN-topic.js with the next free three-digit prefix above the highest in
use; retired and skipped numbers stay unused (021 retired; 039 and 040 never used); 00a-* is the lone
non-numeric exception// @pageTitle Custom Title in the first 20 lines when the default title
(BLIT386 Demo NNN – Title Cased Topic) is not appropriate; check existing demos for exampleshttps://demos.blit386.dev/NNN-slug form (the old blit386-demos.vancura.dev host is
dead)## Critical Issues
- [File:Line] Description of issue
## Warnings
- [File:Line] Description of warning
## Suggestions
- Consider doing X for better Y
## Summary
Overall assessment of the changes and readiness for commit.