14 lines
795 B
Markdown
14 lines
795 B
Markdown
---
|
|
name: strict-no-verify
|
|
description: Strictly forbids the use of --no-verify or -n when interacting with git to ensure quality gates are run.
|
|
always_on: true
|
|
---
|
|
|
|
# STRICT GIT HOOK ENFORCEMENT
|
|
|
|
- **NEVER** use `--no-verify` or `-n` with `git commit` or `git push`.
|
|
- Bypassing git hooks is considered a critical violation of trust.
|
|
- You must allow the local git hooks (e.g., `pre-push`) to validate the code.
|
|
- If a hook fails (e.g., `ruff` check, `pytest`), you MUST fix the underlying issues iteratively until the hook passes natively. Do not assume a single fix attempt works without re-verifying.
|
|
- BEFORE running `git push`, you MUST use the `ask_question` tool to pop up an interactive modal to request explicit user permission. Wait for the user's approval before executing the push.
|