appmod-hooks

Automate lifecycle orchestration with ordered hook execution and a centralized action registry.

35|8|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/microsoft/github-copilot-modernization --skill appmod-hooks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: appmod-hooks
Source: https://github.com/microsoft/github-copilot-modernization/tree/main/plugins/github-copilot-modernization/skills/appmod-hooks
Command: npx skills add https://github.com/microsoft/github-copilot-modernization --skill appmod-hooks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Lifecycle hooks for the modernize-rearchitecture coordinator provide a structured way to trigger actions at defined points during workflow execution, enabling predictable orchestration and auditable changes.

Core Features & Use Cases

  • Hook Points: before_all, before_task, after_task, after_all with clear context and execution timing to coordinate DAG tasks.
  • Registered Actions: A centralized registry (see references/actions.yml) that maps actions to commands and enforces execution order and optionality.
  • Execution Rules: Actions run in order; failures log and continue; mandatory vs optional actions; coordinator executes hooks locally.

Quick Start

Register hook points and actions in the coordinator to orchestrate a multi-phase modernization workflow.

Frequently Asked Questions about appmod-hooks

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

FAQPage Schema
How do I orchestrate multi-phase modernization workflows with ordered hook execution?

Workflow orchestration for multi-phase modernization uses lifecycle hooks to trigger actions at defined points, enabling predictable execution and auditable changes across DAG tasks.

What are lifecycle hooks in a modernization coordinator and how do they work?

Lifecycle hooks provide structured trigger points like before_all, before_task, after_task, and after_all to coordinate DAG tasks, ensuring clear context and precise execution timing during workflow orchestration.

How do I register actions for a multi-phase modernization workflow?

You register actions in a centralized registry that maps actions to commands, enforcing execution order and optionality while applying mandatory or optional behavior rules within the workflow.

What happens when an action fails during workflow orchestration?

Error-tolerant action execution logs failures and continues the workflow, distinguishing between mandatory and optional actions so that non-critical errors do not halt the entire orchestration process.

Can I use conditional behavior for tasks in a modernization workflow?

Conditional behavior is supported through the central action registry, allowing you to enforce execution order and optionality for actions while handling context-rich task dispatch.

What is the best way to coordinate DAG tasks across multiple modernization phases?

The best way to coordinate DAG tasks is using hook-point sequencing with before_all and after_all triggers, providing a structured lifecycle that ensures predictable and auditable workflow changes.