메뉴
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.
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.
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.
| name | demos-deep-review |
| description | 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. |
Comprehensive code review that combines automated checks, AI-powered analysis, and security auditing. Use this before pushing significant changes or creating pull requests.
/demos-deep-review
/demos-security-run or pnpm run security:mcp-preflight with the session MCP descriptor path and
--allow-fallbackpnpm run preflight (format, lint, spellcheck, knip, docs:links, build – build is already included)pnpm run security:audit (pnpm audit)git diff origin/main...HEAD to see all changes vs maingit log origin/main..HEAD --oneline to see commit historysrc/*.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.## Pre-Push Review Summary
### Changes Overview
- [Brief description of what changed]
- Files modified: X
- Lines added: +Y, removed: -Z
### Automated Checks
- [PASS/FAIL] Format check
- [PASS/FAIL] Lint check
- [PASS/FAIL] Spell check
- [PASS/FAIL] Unused exports (knip)
- [PASS/FAIL] Docs links (docs:links)
- [PASS/FAIL] Build
- [PASS/FAIL] Security audit
### Code Review Findings
#### Critical Issues
- [File:Line] Description (must fix before merge)
#### Warnings
- [File:Line] Description (should address)
#### Suggestions
- Description (nice to have)
### Verdict
[READY TO PUSH / NEEDS FIXES / NEEDS DISCUSSION]