メニュー
Prevent commits that skip pre-commit hooks (--no-verify, -n). Auto-loads when git commit with bypass flags is attempted. Triggers: commit --no-verify, git commit -n, git push --no-verify.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Bắt buộc khai báo độ phức tạp Big-O và cấu trúc dữ liệu trước khi viết thuật toán.
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.
Explore ideas before implementation, design features, make architecture decisions, and validate approaches. Use when: brainstorm, explore options, design, what approach, how should we, ideas, before building.
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines.
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
| name | block-no-verify |
| description | Prevent commits that skip pre-commit hooks (--no-verify, -n). Auto-loads when git commit with bypass flags is attempted. Triggers: commit --no-verify, git commit -n, git push --no-verify. |
| license | MIT |
Prevent git commit --no-verify which bypasses security scanning, lint, and pre-commit hooks.
Block any of these patterns:
git commit --no-verifygit commit -ngit push --no-verifygit am --no-verifyWhen detected, respond with:
BLOCKED: git commit with --no-verify detected.
Pre-commit hooks exist for a reason — they run:
- Secret scanning (python .github/scripts/security_scan.py .)
- Linting (ruff check .)
- Guard tests (node .github/hooks/scripts/guard.test.js)
Run without --no-verify to pass all gates, OR
explain why you need to bypass (e.g., emergency hotfix with documented reason).
If you have a valid reason, run:
git commit -m "message" --no-verify
(will be logged for audit)
If bypass is accepted, document in .kilo/logs/no-verify-audit.md: