/hooks test <HOOK>
Hooks Test/code/commands/interactive/hooks-test
Hooks Test.
- Options
- 2
- Arguments
- 1
- Examples
- 1
- Industry
- 0 of 5 mapped
About
Supported options and rules: --event EVENT; --dry-run default true for mutating handlers unless explicitly confirmed.
Syntax
The canonical syntax string as recorded in the catalogue. It is authoritative — it is never reconstructed from the option and argument lists below.
Subcommand of /hooks
Arguments
hookidentifierRequiredposition 1Hook name or identifier.
Options
Defaults, allowed values, conflicts and scope come from the catalogue; blank fields mean the catalogue records nothing, not that the constraint is absent.
--event <string>stringOptionalChoose the hook event used for a test invocation.
--dry-runbooleanOptionalValidate and preview the operation without applying its mutating effect. Default: True.
Defaulttrue
Examples
With options
WITH OPTIONS/hooks test format-after-edit --event POST_TOOL_USE
Hooks Test.
Availability & requirements
Nothing recorded — this command is offered in the default session, with no repository, authentication, capability or platform requirement attached to it.
Relationships
Aliases
None recordedNo alias resolves to this commandAlternate surfaces
Not applicableThis command exists on one surface onlyRelated commands
None recordedNo related command is recordedIndustry comparison
0 of 5 products mapped
Command-level mappings against 5 audited products, each with its documentation source and capture date. No documented equivalent means the audit found nothing in that product’s official documentation — it is not a claim that the product lacks the capability.
Every canonical command was reviewed against all 5 products in one pass captured 2026-09-18. A product with no mapping is a reviewed finding of no documented equivalent, not an unreviewed pair.
Captured 2026-09-18 · 238 commands × 5 products
All 5 results below are negative. That is this command’s reviewed finding — not an incomplete row.