blit386-demos

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.

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.

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.

Explain that blit386-demos has no automated tests and how to verify demos by hand instead. Use when the user asks to run, write, or find tests in this repo.

Format all code with Biome and Prettier, then verify formatting passes. Use when the user asks to format, reformat, or clean up code style, or to fix a failing format check.

Quickly format all code with Biome and Prettier, skipping the verification step. Use for a fast cleanup after edits or to fix formatting flagged by CI or a hook.