{{skill-name-kebab-case}}
Skill220 starsChanged 7 days agoMITView on GitHub
{{WHAT this skill does in one sentence.}} WHEN: {{trigger phrase 1}}, {{trigger phrase 2}}, {{trigger phrase 3}}, {{e.g. "upgrade .NET Framework to .NET 10", "migrate Struts to Spring MVC", "fix CVE vulnerabilities", "containerize legacy app"}}. NOT for: {{explicit exclusions — prevents false triggering, e.g. "greenfield development, infrastructure-only changes"}}.
In this repository11 other files it gives its agents.
- 03-Azure/01-04-AI/01_Agentic_SDLC/.github/copilot-instructions.mdCopilot instructions
- 03-Azure/01-04-AI/02_Inventory_Planning_Fabric/.github/copilot-instructions.mdCopilot instructions
- 03-Azure/01-04-AI/03_Inventory_Planning_Agentic/.github/copilot-instructions.mdCopilot instructions
- 03-Azure/01-04-AI/04_Agentic_Contract_Lifecycle_Management/.github/copilot-instructions.mdCopilot instructions
- 03-Azure/01-04-AI/08_Predictive_Maintenance/.github/copilot-instructions.mdCopilot instructions
- 03-Azure/01-04-AI/11_Healthcare_Regulatory_Intelligence/.github/copilot-instructions.mdCopilot instructions
- dotnet-upgradeSkill
- java-upgradeSkill
- skill-creatorSkill
- frontend-designSkill
- reconciliationSkill
The file
Files
<!--
SKILL TEMPLATE — App Modernization knowledge package
Copy to: <target-repo>/.github/skills/{{skill-name}}/SKILL.md
Picked up by GitHub Copilot CLI (/skills list) and auto-matched by the
modernize CLI against your prompt during `modernize plan create`.
The `description` is the routing contract — invest most effort there.
The skill name must be lowercase and hyphenated (no spaces) and match its folder name.
Optional supporting files live next to this file (rulebooks, scripts, examples).
-->{{Skill Title — e.g. ".NET Framework → .NET 10 Migration Rules"}}
Purpose
{{1–2 sentences: what knowledge this skill packages and what outcome it enables.}}
Prerequisites
- {{e.g. "Assessment report (ASSESSMENT.md) exists"}}
- {{e.g. ".NET 10 SDK installed — verify with
dotnet --list-sdks"}}
Procedure
Step 1 — {{e.g. "Detect the migration surface"}}
{{Concrete instructions. Prefer commands and decision tables over prose.}}
{{command or code example}}Step 2 — {{e.g. "Apply transformation rules"}}
| Source pattern | Target pattern | Notes |
{{e.g. WebForms .aspx}} | {{e.g. Razor Pages}} | {{caveat}} |
{{e.g. javax.servlet.*}} | {{e.g. jakarta.servlet.*}} | {{caveat}} |
Step 3 — {{e.g. "Verify"}}
- {{verification item — e.g. "solution builds with zero warnings-as-errors"}}
- {{verification item — e.g. "all tests in CI suite pass"}}
Common Pitfalls
- ⚠️ {{pitfall + how to avoid — e.g. "binding redirects are not honored in .NET 10; delete them and use the SDK-style project resolution"}}
- ⚠️ {{pitfall + how to avoid}}
References
- {{Link to official migration guide / rulebook file in this folder}}
- {{e.g.
./rules/breaking-changes.md(supporting file)}}
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

