[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75FSG83WWB7CE4N02XCXPJV":3,"skill-same:01M75FSG83WWB7CE4N02XCXPJV":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M75FSG83WWB7CE4N02XCXPJV","block-no-verify-hook",null,"Configure a PreToolUse hook to prevent AI agents from skipping git pre-commit hooks with --no-verify and other bypass flags. Use when setting up Claude Code projects that enforce commit quality gates.","RudyCity\u002Fsuperagent","RudyCity","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F82188919?v=4","01M75FP5X8AW8ACBH0SH34WS7M","01M75FP5YAHJK8M1Q52BWXB82K",70,"MIT","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fblock-no-verify-hook\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: block-no-verify-hook\ndescription: Configure a PreToolUse hook to prevent AI agents from skipping git pre-commit hooks with --no-verify and other bypass flags. Use when setting up Claude Code projects that enforce commit quality gates.\n---\n\n# Block No-Verify Hook\n\nPreToolUse hook configuration that intercepts and blocks bypass-flag usage before execution, ensuring AI agents cannot skip pre-commit hooks, GPG signing, or other git safety mechanisms.\n\n## Overview\n\nAI coding agents (Claude Code, Codex, etc.) can run shell commands with flags like `--no-verify` that bypass pre-commit hooks. This defeats the purpose of linting, formatting, testing, and security checks configured in pre-commit hooks. The block-no-verify hook adds a PreToolUse guard that rejects any tool call containing bypass flags before execution.\n\n## Problem\n\nWhen AI agents commit code, they may use bypass flags to avoid hook failures:\n\n```bash\n# These commands skip pre-commit hooks entirely\ngit commit --no-verify -m \"quick fix\"\ngit push --no-verify\ngit commit --no-gpg-sign -m \"unsigned commit\"\ngit merge --no-verify feature-branch\n```\n\nThis allows:\n- Unformatted code to enter the repository\n- Linting errors to bypass checks\n- Security scanning to be skipped\n- Unsigned commits to bypass signing policies\n- Test suites to be circumvented\n\n## Solution\n\nAdd a `PreToolUse` hook to `.claude\u002Fsettings.json` that inspects every Bash tool call and blocks commands containing bypass flags.\n\n### Configuration\n\nAdd the following to your project's `.claude\u002Fsettings.json`:\n\n```json\n{\n  \"hooks\": {\n    \"PreToolUse\": [\n      {\n        \"matcher\": \"Bash\",\n        \"hook\": {\n          \"type\": \"command\",\n          \"command\": \"if printf '%s' \\\"$TOOL_INPUT\\\" | grep -qE '(^|&&|;|\\\\|)\\\\s*git\\\\s+.*--(no-verify|no-gpg-sign)'; then echo 'BLOCKED: --no-verify and --no-gpg-sign flags are not allowed. Run the commit without bypass flags so that pre-commit hooks execute properly.' >&2; exit 2; fi\"\n        }\n      }\n    ]\n  }\n}\n```\n\n### How It Works\n\n1. **Matcher**: The hook targets only `Bash` tool calls, so it does not interfere with other tools (Read, Edit, Grep, etc.).\n2. **Inspection**: The `$TOOL_INPUT` environment variable contains the full command the agent is about to execute. The hook uses `printf` to safely pass input (avoiding `echo` pitfalls with special characters) and checks for `--no-verify` or `--no-gpg-sign` flags only when preceded by a `git` command.\n3. **Blocking**: If a bypass flag is found in a git command, the hook exits with code 2 and prints an error message. Exit code 2 signals Claude Code to reject the tool call entirely.\n4. **Pass-through**: If no bypass flag is found, the hook exits with code 0 and the command executes normally.\n\n### Exit Codes\n\n| Code | Meaning |\n|------|---------|\n| 0 | Allow the tool call to proceed |\n| 1 | Error (tool call still proceeds, warning shown) |\n| 2 | Block the tool call entirely |\n\n## Blocked Flags\n\n| Flag | Purpose | Why Blocked |\n|------|---------|-------------|\n| `--no-verify` | Skips pre-commit and commit-msg hooks | Bypasses linting, formatting, testing, security checks |\n| `--no-gpg-sign` | Skips GPG commit signing | Bypasses commit signing policy |\n\n## Installation\n\n### Per-Project Setup\n\nCreate or update `.claude\u002Fsettings.json` in your project root:\n\n```bash\nmkdir -p .claude\ncat > .claude\u002Fsettings.json \u003C\u003C 'EOF'\n{\n  \"hooks\": {\n    \"PreToolUse\": [\n      {\n        \"matcher\": \"Bash\",\n        \"hook\": {\n          \"type\": \"command\",\n          \"command\": \"if printf '%s' \\\"$TOOL_INPUT\\\" | grep -qE '(^|&&|;|\\\\|)\\\\s*git\\\\s+.*--(no-verify|no-gpg-sign)'; then echo 'BLOCKED: --no-verify and --no-gpg-sign flags are not allowed. Run the commit without bypass flags so that pre-commit hooks execute properly.' >&2; exit 2; fi\"\n        }\n      }\n    ]\n  }\n}\nEOF\n```\n\n### Global Setup\n\nTo enforce across all projects, add to `~\u002F.claude\u002Fsettings.json`:\n\n```bash\nmkdir -p ~\u002F.claude\ncat > ~\u002F.claude\u002Fsettings.json \u003C\u003C 'EOF'\n{\n  \"hooks\": {\n    \"PreToolUse\": [\n      {\n        \"matcher\": \"Bash\",\n        \"hook\": {\n          \"type\": \"command\",\n          \"command\": \"if printf '%s' \\\"$TOOL_INPUT\\\" | grep -qE '(^|&&|;|\\\\|)\\\\s*git\\\\s+.*--(no-verify|no-gpg-sign)'; then echo 'BLOCKED: --no-verify and --no-gpg-sign flags are not allowed. Run the commit without bypass flags so that pre-commit hooks execute properly.' >&2; exit 2; fi\"\n        }\n      }\n    ]\n  }\n}\nEOF\n```\n\n## Verification\n\nTest that the hook blocks bypass flags:\n\n```bash\n# This should be blocked by the hook:\ngit commit --no-verify -m \"test\"\n\n# This should succeed normally:\ngit commit -m \"test\"\n```\n\n## Extending the Hook\n\n### Adding More Blocked Flags\n\nTo block additional flags (e.g., `--force`), extend the grep pattern:\n\n```json\n{\n  \"hooks\": {\n    \"PreToolUse\": [\n      {\n        \"matcher\": \"Bash\",\n        \"hook\": {\n          \"type\": \"command\",\n          \"command\": \"if printf '%s' \\\"$TOOL_INPUT\\\" | grep -qE '(^|&&|;|\\\\|)\\\\s*git\\\\s+.*--(no-verify|no-gpg-sign|force-with-lease|force)'; then echo 'BLOCKED: Bypass flags are not allowed.' >&2; exit 2; fi\"\n        }\n      }\n    ]\n  }\n}\n```\n\n### Combining with Other Hooks\n\nThe block-no-verify hook works alongside other PreToolUse hooks:\n\n```json\n{\n  \"hooks\": {\n    \"PreToolUse\": [\n      {\n        \"matcher\": \"Bash\",\n        \"hook\": {\n          \"type\": \"command\",\n          \"command\": \"if printf '%s' \\\"$TOOL_INPUT\\\" | grep -qE '(^|&&|;|\\\\|)\\\\s*git\\\\s+.*--(no-verify|no-gpg-sign)'; then echo 'BLOCKED: Bypass flags not allowed.' >&2; exit 2; fi\"\n        }\n      },\n      {\n        \"matcher\": \"Bash\",\n        \"hook\": {\n          \"type\": \"command\",\n          \"command\": \"if printf '%s' \\\"$TOOL_INPUT\\\" | grep -qE 'rm\\\\s+-rf\\\\s+\u002F'; then echo 'BLOCKED: Dangerous rm command.' >&2; exit 2; fi\"\n        }\n      }\n    ]\n  }\n}\n```\n\n## Best Practices\n\n1. **Commit the settings file** -- Add `.claude\u002Fsettings.json` to version control so all team members benefit from the hook.\n2. **Document in onboarding** -- Mention the hook in your project's contributing guide so developers understand why bypass flags are blocked.\n3. **Pair with pre-commit hooks** -- The block-no-verify hook ensures pre-commit hooks run; make sure you have meaningful pre-commit hooks configured.\n4. **Test after setup** -- Verify the hook works by intentionally triggering it in a test commit.\n","# Block No-Verify Hook\n\nPreToolUse hook configuration that intercepts and blocks bypass-flag usage before execution, ensuring AI agents cannot skip pre-commit hooks, GPG signing, or other git safety mechanisms.\n\n## Overview\n\nAI coding agents (Claude Code, Codex, etc.) can run shell commands with flags like `--no-verify` that bypass pre-commit hooks. This defeats the purpose of linting, formatting, testing, and security checks configured in pre-commit hooks. The block-no-verify hook adds a PreToolUse guard that rejects any tool call containing bypass flags before execution.\n\n## Problem\n\nWhen AI agents commit code, they may use bypass flags to avoid hook failures:\n\n```bash\n# These commands skip pre-commit hooks entirely\ngit commit --no-verify -m \"quick fix\"\ngit push --no-verify\ngit commit --no-gpg-sign -m \"unsigned commit\"\ngit merge --no-verify feature-branch\n```\n\nThis allows:\n- Unformatted code to enter the repository\n- Linting errors to bypass checks\n- Security scanning to be skipped\n- Unsigned commits to bypass signing policies\n- Test suites to be circumvented\n\n## Solution\n\nAdd a `PreToolUse` hook to `.claude\u002Fsettings.json` that inspects every Bash tool call and blocks commands containing bypass flags.\n\n### Configuration\n\nAdd the following to your project's `.claude\u002Fsettings.json`:\n\n```json\n{\n  \"hooks\": {\n    \"PreToolUse\": [\n      {\n        \"matcher\": \"Bash\",\n        \"hook\": {\n          \"type\": \"command\",\n          \"command\": \"if printf '%s' \\\"$TOOL_INPUT\\\" | grep -qE '(^|&&|;|\\\\|)\\\\s*git\\\\s+.*--(no-verify|no-gpg-sign)'; then echo 'BLOCKED: --no-verify and --no-gpg-sign flags are not allowed. Run the commit without bypass flags so that pre-commit hooks execute properly.' >&2; exit 2; fi\"\n        }\n      }\n    ]\n  }\n}\n```\n\n### How It Works\n\n1. **Matcher**: The hook targets only `Bash` tool calls, so it does not interfere with other tools (Read, Edit, Grep, etc.).\n2. **Inspection**: The `$TOOL_INPUT` environment variable contains the full command the agent is about to execute. The hook uses `printf` to safely pass input (avoiding `echo` pitfalls with special characters) and checks for `--no-verify` or `--no-gpg-sign` flags only when preceded by a `git` command.\n3. **Blocking**: If a bypass flag is found in a git command, the hook exits with code 2 and prints an error message. Exit code 2 signals Claude Code to reject the tool call entirely.\n4. **Pass-through**: If no bypass flag is found, the hook exits with code 0 and the command executes normally.\n\n### Exit Codes\n\n| Code | Meaning |\n|------|---------|\n| 0 | Allow the tool call to proceed |\n| 1 | Error (tool call still proceeds, warning shown) |\n| 2 | Block the tool call entirely |\n\n## Blocked Flags\n\n| Flag | Purpose | Why Blocked |\n|------|---------|-------------|\n| `--no-verify` | Skips pre-commit and commit-msg hooks | Bypasses linting, formatting, testing, security checks |\n| `--no-gpg-sign` | Skips GPG commit signing | Bypasses commit signing policy |\n\n## Installation\n\n### Per-Project Setup\n\nCreate or update `.claude\u002Fsettings.json` in your project root:\n\n```bash\nmkdir -p .claude\ncat > .claude\u002Fsettings.json \u003C\u003C 'EOF'\n{\n  \"hooks\": {\n    \"PreToolUse\": [\n      {\n        \"matcher\": \"Bash\",\n        \"hook\": {\n          \"type\": \"command\",\n          \"command\": \"if printf '%s' \\\"$TOOL_INPUT\\\" | grep -qE '(^|&&|;|\\\\|)\\\\s*git\\\\s+.*--(no-verify|no-gpg-sign)'; then echo 'BLOCKED: --no-verify and --no-gpg-sign flags are not allowed. Run the commit without bypass flags so that pre-commit hooks execute properly.' >&2; exit 2; fi\"\n        }\n      }\n    ]\n  }\n}\nEOF\n```\n\n### Global Setup\n\nTo enforce across all projects, add to `~\u002F.claude\u002Fsettings.json`:\n\n```bash\nmkdir -p ~\u002F.claude\ncat > ~\u002F.claude\u002Fsettings.json \u003C\u003C 'EOF'\n{\n  \"hooks\": {\n    \"PreToolUse\": [\n      {\n        \"matcher\": \"Bash\",\n        \"hook\": {\n          \"type\": \"command\",\n          \"command\": \"if printf '%s' \\\"$TOOL_INPUT\\\" | grep -qE '(^|&&|;|\\\\|)\\\\s*git\\\\s+.*--(no-verify|no-gpg-sign)'; then echo 'BLOCKED: --no-verify and --no-gpg-sign flags are not allowed. Run the commit without bypass flags so that pre-commit hooks execute properly.' >&2; exit 2; fi\"\n        }\n      }\n    ]\n  }\n}\nEOF\n```\n\n## Verification\n\nTest that the hook blocks bypass flags:\n\n```bash\n# This should be blocked by the hook:\ngit commit --no-verify -m \"test\"\n\n# This should succeed normally:\ngit commit -m \"test\"\n```\n\n## Extending the Hook\n\n### Adding More Blocked Flags\n\nTo block additional flags (e.g., `--force`), extend the grep pattern:\n\n```json\n{\n  \"hooks\": {\n    \"PreToolUse\": [\n      {\n        \"matcher\": \"Bash\",\n        \"hook\": {\n          \"type\": \"command\",\n          \"command\": \"if printf '%s' \\\"$TOOL_INPUT\\\" | grep -qE '(^|&&|;|\\\\|)\\\\s*git\\\\s+.*--(no-verify|no-gpg-sign|force-with-lease|force)'; then echo 'BLOCKED: Bypass flags are not allowed.' >&2; exit 2; fi\"\n        }\n      }\n    ]\n  }\n}\n```\n\n### Combining with Other Hooks\n\nThe block-no-verify hook works alongside other PreToolUse hooks:\n\n```json\n{\n  \"hooks\": {\n    \"PreToolUse\": [\n      {\n        \"matcher\": \"Bash\",\n        \"hook\": {\n          \"type\": \"command\",\n          \"command\": \"if printf '%s' \\\"$TOOL_INPUT\\\" | grep -qE '(^|&&|;|\\\\|)\\\\s*git\\\\s+.*--(no-verify|no-gpg-sign)'; then echo 'BLOCKED: Bypass flags not allowed.' >&2; exit 2; fi\"\n        }\n      },\n      {\n        \"matcher\": \"Bash\",\n        \"hook\": {\n          \"type\": \"command\",\n          \"command\": \"if printf '%s' \\\"$TOOL_INPUT\\\" | grep -qE 'rm\\\\s+-rf\\\\s+\u002F'; then echo 'BLOCKED: Dangerous rm command.' >&2; exit 2; fi\"\n        }\n      }\n    ]\n  }\n}\n```\n\n## Best Practices\n\n1. **Commit the settings file** -- Add `.claude\u002Fsettings.json` to version control so all team members benefit from the hook.\n2. **Document in onboarding** -- Mention the hook in your project's contributing guide so developers understand why bypass flags are blocked.\n3. **Pair with pre-commit hooks** -- The block-no-verify hook ensures pre-commit hooks run; make sure you have meaningful pre-commit hooks configured.\n4. **Test after setup** -- Verify the hook works by intentionally triggering it in a test commit.\n",{"name":5,"description":7},"main","62c7af5ced2c21355d148c243edb6d5921cca1a6",".agents\u002Fskills\u002Fblock-no-verify-hook",8,"https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent","https:\u002F\u002Fgithub.com\u002FRudyCity","2026-11-14 22:58:49",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add RudyCity\u002Fsuperagent --skill block-no-verify-hook",{"tool":36,"command":37},"bunx","bunx skills add RudyCity\u002Fsuperagent --skill block-no-verify-hook",{"tool":39,"command":40},"pnpm","pnpm dlx skills add RudyCity\u002Fsuperagent --skill block-no-verify-hook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fblock-no-verify-hook\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M75GP28CM6QCSXSHKFF3NNKS","telegram_bot","Use Telegram Bot when the user asks for Telegram Bot or this provider's API.","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002Fmuse-bridge-kit\u002Fskills\u002Ftelegram-bot\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M75GNZGZYM7NWDV6MBP3HS14","superagent-bridge","Operate the Muse\u003C->superagent Telegram bridge: poll the private group for task_request\u002Ftask_result envelopes, validate senders, and reply with task_batch\u002Ftask_done as Muse (the remote brain).","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002Fmuse-bridge-kit\u002Fskills\u002Fsuperagent-bridge\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M75GNHN19HJWZ7NAPM5E5JCV","Writing Skills","TDD for process documentation - test with subagents before writing, iterate until bulletproof","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M75GNCQEKVRA4FH161NZPZNB","writing-shape","Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-shape\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M75GNAF9NAYCSTBDZDGMK0DZ","Writing Plans","Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M75GN72EV0V5NQAW9CSPFRFH","writing-guidelines","Review docs\u002Fprose for Writing Guidelines compliance. Use when asked to \"review my docs\", \"check writing style\", \"audit prose\", \"review docs voice and tone\", or \"check this page against the writing handbook\".","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-guidelines\u002FSKILL.md",[],[]]