Hookify List

Parse hookify rule files and present statuses, events, patterns, and file paths in a structured table.

2|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/Poorgramer-Zack/copilot-cli-things --skill hookify-list
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Hookify List
Source: https://github.com/Poorgramer-Zack/copilot-cli-things/tree/main/plugins/hookify/skills/hookify-list
Command: npx skills add https://github.com/Poorgramer-Zack/copilot-cli-things --skill hookify-list

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers catalog and audit all configured hookify rules across a project, surfacing statuses, events, patterns, and file paths to simplify rule management and troubleshooting.

Core Features & Use Cases

  • Discover and enumerate all hookify rule files across the repository.
  • Display a consolidated view with status, event type, pattern, and file path for each rule.
  • Provide per-rule previews and quick actions for modification or debugging in audits and reviews.

Quick Start

Ask the AI to run the Hookify List skill to display all configured hookify rules.

Frequently Asked Questions about Hookify List

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I list all hookify rules configured in my project?

To list all hookify rules configured in a project, use a cataloging tool to parse rule files, extract frontmatter, and present a structured table displaying status, event types, patterns, and file paths.

What is the best way to audit hookify rule files across a repository?

Auditing hookify rule files across a repository is best handled by enumerating all configurations and surfacing statuses, events, patterns, and file paths in a consolidated view for quick inspection and troubleshooting.

Can I view the status and file paths of my hookify rules in a single table?

Yes, you can view hookify rule statuses and file paths in a single table by parsing the rule files to extract frontmatter and consolidating the metadata into a structured display with per-rule previews.

How does frontmatter extraction work when discovering hookify rules?

Frontmatter extraction for discovering hookify rules works by parsing configured rule files to identify metadata like status, event types, and patterns, then presenting those details in a structured table format.

Do I need any dependencies to catalog hookify rules for troubleshooting?

No dependencies are required to catalog hookify rules for troubleshooting, as the inspection process parses existing rule files directly to surface statuses, event types, and file paths without additional setup.

Why are some hookify rules not showing up in my project audit?

Hookify rules may not show up in a project audit if the rule files cannot be parsed or the frontmatter is missing, preventing the tool from extracting the status, event type, and pattern data needed for the table.