microsoft/appmod-hooks
plugins/github-copilot-modernization/skills/appmod-hooks/SKILL.md
Lifecycle hooks for the modernize-rearchitecture coordinator. Defines hook points, registered actions, and execution rules.
$ install --global
skillsauthnpx skillsauth add microsoft/github-copilot-modernization appmod-hooksInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 4, 2026, 8:53 AM129.8s6 files scanned
SKILL.md
- name:
- appmod-hooks
- description:
- Lifecycle hooks for the modernize-rearchitecture coordinator. Defines hook points, registered actions, and execution rules.
appmod-hooks
Lifecycle hooks that fire at defined points during coordinator execution. Each hook point triggers registered actions in order.
Hook Points
| Point | When | Coordinator context |
|---|---|---|
| before_all | After DAG is generated, before first task dispatch | Full DAG available, no tasks started |
| before_task | Before dispatching each worker | Task ID and role known, profile read for Progress |
| after_task | After worker returns and verify passes | Task artifact available, status decided. If all tasks in the current phase are now ✅, also execute phase-completion actions (git commit, commit-pin, phase counter increment) |
| after_all | After completion criteria met (§3.7) | All tasks resolved |
Registered Actions
See references/actions.yml for the action registry. Actions use dotted namespace: appmod.<domain>.<verb>.
Execution Rules
- Actions within a hook point execute in order (top to bottom in the registry)
- An action that fails does NOT block subsequent actions — log the error and continue
optional: falseactions MUST execute;optional: trueactions execute only if theirconditionis met- The coordinator executes hook actions itself (shell commands for git, file writes for profile) — hooks are NOT delegated to workers
Related Skills
microsoft/clarifying-scenarios
development
VerifiedTrustedCommunity
Evaluates whether a user's modernization/rewrite request provides enough scenario context to proceed (e.g., target component library, screenshots, design system for frontend; API contract policy, data migration strategy for backend). Produces a deterministic clarity score, asks the user for missing required fields via a structured form, and writes a canonical `clarification.md` artifact consumed by all downstream agents. Triggers: "clarification gate", "scenario clarification", "elicit missing context", "evaluate prompt completeness", "ask user for screenshots / target library / design system". NOT for: feature specification (use feature-inventory), planning (use creating-implementation-plan), implementation (use implementing-code), or resolving spec-time `[NEEDS CLARIFICATION]` markers (those remain owned by feature-inventory).
12SKILL.mdUpdated Jun 4, 2026
microsoft/team-charters
development
VerifiedTrustedCommunity
Provides role charters (mission, ownership, core principles, quality bar) for a multi-agent coding team. Each charter defines the role's mission, ownership scope, core principle (boundary constraints), and quality bar. Most roles also include communication rules. Consumed by the coordinator during task decomposition to assign work to the correct role. Triggers: "look up role charter", "what does the architect own", "check role boundaries", "find team roles", "which role handles X", "list agent charters", "role responsibilities". NOT for: task decomposition (use breaking-down-tasks), implementation (use implementing-code), architecture analysis (use analyzing-architecture).
12SKILL.mdUpdated May 14, 2026
microsoft/project-recon
tools
VerifiedTrustedCommunity
Zero-dependency shell recon for any code repository — detect languages, count LOC, and report project scale. Pure POSIX find/wc or PowerShell, no Python or third-party tools required. Triggers: "how big is this project", "what languages", "project sizing", "repo recon", "LOC count", "scope check".
12SKILL.mdUpdated May 14, 2026
microsoft/list-plans
data-ai
VerifiedTrustedCommunity
Discovers valid migration plans in the workspace and returns the selected plan path. A valid plan is a subdirectory of .github/modernize/ that contains plan.md AND tasks.json (tasks.json may be in the plan folder or in a .metadata subfolder). Handles 0, 1, or multiple plans and prompts the user when a choice is needed. Triggers: "list plans", "find plans", "select plan", "list-and-select-plan", "discover plans".
12SKILL.mdUpdated May 14, 2026