generate-hooks

Generate GitHub Copilot hook JSON configurations for lifecycle events.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/vndkubi/bootstrap-toolkits --skill generate-hooks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-hooks
Source: https://github.com/vndkubi/bootstrap-toolkits/tree/main/.github/skills/generate-hooks
Command: npx skills add https://github.com/vndkubi/bootstrap-toolkits --skill generate-hooks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of GitHub Copilot lifecycle hooks by generating .github/hooks/*.json files to coordinate agent sessions.

Core Features & Use Cases

  • Detect project tooling (formatters, linters, build tools) and generate corresponding hooks for events such as sessionStart, sessionEnd, preToolUse, postToolUse, and agentStop.
  • Produce organized, scalable hook configurations that support both standard workflows and enterprise governance.
  • Use case: bootstrap Copilot configuration in a multi-repo setup and enforce consistent automation across teams.

Quick Start

Run the generate-hooks skill to automatically create and configure .github/hooks/*.json based on detected tooling in your project.

Frequently Asked Questions about generate-hooks

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

FAQPage Schema
How do I generate GitHub Copilot hooks for lifecycle events?

To generate GitHub Copilot hooks for lifecycle events, run the generate-hooks skill to automatically detect your project tooling and output JSON configurations under .github/hooks with version 1 schema.

What are Copilot hooks used for in agent sessions?

Copilot hooks are used to automate lifecycle events for agent sessions by coordinating actions like sessionStart, sessionEnd, preToolUse, postToolUse, and errorOccurred based on your project's detected tooling.

Can I bootstrap Copilot configuration across multiple repositories?

Yes, you can bootstrap Copilot configuration across multiple repositories by running the generate-hooks skill to produce organized, scalable hook configurations that enforce consistent automation across teams.

Does the generate-hooks skill detect existing formatters and linters?

Yes, the generate-hooks skill detects project tooling such as formatters, linters, type checkers, and build tools to generate corresponding hooks for standard workflows and enterprise governance.

What's the best way to enforce consistent automation hooks in multi-repo setups?

The best way to enforce consistent automation hooks in multi-repo setups is to generate .github/hooks/*.json files using the generate-hooks skill, which produces organized configurations supporting both standard workflows and enterprise governance.

What schema version do generated Copilot hook configurations use?

Generated Copilot hook configurations use version 1 schema and are output as JSON files under the .github/hooks directory to coordinate agent sessions across projects with varying toolchains.