菜单
Verify nest-blog-api changes with npm run lint, npm run build, npm run test, module registration coherence, DTO validation coverage, service exception handling, and integration boundary review. Use after implementation, during reviews, for reruns, and whenever a task risks regressions.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/junjuny0227/nest-blog-api --skill quality-gate命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Plan and review nest-blog-api NestJS module structure, dependency injection, entity design, and API contract scope. Use for any module creation, cross-module dependency decision, or architecture scope question.
Review nest-blog-api changed files using dynamically discovered .claude/rules, NestJS module conventions, DTO validation, service/controller boundaries, security basics, and validation results. Use for code review requests, staged diff review, pre-PR review, and after multi-file implementation.
Create actual nest-blog-api Git commits by inspecting changed files, splitting logical units, staging the right files, and running git commit with project Conventional Commit messages. Use when the user explicitly asks to commit, make a commit, split commits, or commit staged/unstaged changes. Do not push.
基于 SOC 职业分类
正在显示 SKILL.md
| name | quality-gate |
| description | Verify nest-blog-api changes with npm run lint, npm run build, npm run test, module registration coherence, DTO validation coverage, service exception handling, and integration boundary review. Use after implementation, during reviews, for reruns, and whenever a task risks regressions. |
Use this skill to verify changes before final delivery.
Discover and read project harness rules before static review:
find .claude/rules -name "*.md" 2>/dev/null
Use these files together with CLAUDE.md and nearby source patterns.
Run these when feasible:
npm run lint
npm run build
npm run test
For e2e tests when relevant:
npm run test:e2e
If a command fails, inspect whether the failure is caused by the current change, the environment (missing DB, missing env vars), or pre-existing repository state.
Check the boundaries affected by the task:
providers of the owning *.module.ts.For DTO changes, compare both sides:
PartialType is used for Update DTOs instead of duplicating fields.For service changes:
Error.Report findings in this order:
If no issues are found, say so directly and still list the checks that were run.