Block no verify

Skill vtgiang-dotcom/Solo-Code-Harness/.claude/skills/block-no-verify

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.From its SKILL.md

Install

npx -y skills add vtgiang-dotcom/Solo-Code-Harness --skill block-no-verify

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.2 KB, as published. Nobody here has run it

Block No-Verify

Prevent git commit --no-verify which bypasses security scanning, lint, and pre-commit hooks.

Detection Patterns

Block any of these patterns:

git commit --no-verify
git commit -n
git push --no-verify
git am --no-verify

Response

When 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)

Governance

If bypass is accepted, document in .kilo/logs/no-verify-audit.md:

Date and time
Reason for bypass
Files changed
Who approved