list

To list all configured hookify rules, the Skill scans your project directory for rule files and extracts their frontmatter metadata. It then presents a tabular summary showing each rule's name, enabled state, event, and matching pattern for quick auditing.

The best way to audit hookify rule configurations is to automatically enumerate all rule files and read their frontmatter. This approach extracts the name, enabled state, event, and pattern from each file to produce a concise, sortable summary suitable for compliance checks.

Yes, you can see the events and patterns by reading the frontmatter from each hookify rule file. The Skill identifies all configured rules and displays their associated events and matching patterns in a tabular summary alongside their names and enabled states.

To check if a hookify rule is enabled or disabled, the Skill reads the frontmatter of each rule file in your project. It compiles this metadata into a summary table that clearly shows the enabled state for every configured rule.

Yes, this tool works with any project that contains hookify automation rules. It applies to your repository by identifying all configured rule files and extracting their core metadata, regardless of the specific automation patterns you have set up.

You need to audit hookify rules before a code review to verify rule coverage and ensure every rule is enabled for its expected events. This process extracts rule metadata like name, event, and pattern to support debugging and confirm configuration compliance across the project.