microsoft/guidelines
plugins/github-copilot-modernization/skills/guidelines/SKILL.md
Collection of framework-to-framework migration rules and transformation patterns (e.g., Struts→Spring MVC, JSP→Thymeleaf, EJB→Spring Boot). Triggers: "check migration guidelines", "look up transformation rules", "find Struts-to-Spring patterns", "apply migration conventions", "conversion rules for X→Y". Also consumed automatically by breaking-down-tasks and implementing-code during migration workflows. NOT for: direct execution — other skills scan this directory.
$ install --global
skillsauthnpx skillsauth add microsoft/github-copilot-modernization guidelinesInstall 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: May 14, 2026, 6:24 AM201.5s9 files scanned
SKILL.md
- name:
- guidelines
- description:
- |
- Triggers:
- check migration guidelines", "look up transformation rules", "find Struts-to-Spring patterns", "apply migration conventions", "conversion rules for X→Y".
- NOT for:
- direct execution — other skills scan this directory.
User Input
You MUST consider the user input before proceeding (if not empty).
Purpose
Guidelines are curated, domain-specific knowledge bases providing:
- Migration patterns: Technology-to-technology recipes
- Transformation rules: Concrete mappings and conversion templates
- Checklists: Step-by-step validation criteria
Directory Structure
skills/guidelines/
├── SKILL.md # This file - lookup mechanism
├── struts-to-spring/ # Struts 2 → Spring Boot 3.x
│ └── SKILL.md
└── {domain}/ # Future guideline domains
└── SKILL.md
Lookup Mechanism
When other skills need guideline lookup:
- Context Analysis: Extract technology keywords from spec/plan/code.
- Guideline Discovery: Search
skills/guidelines/subdirectories for matching patterns. - Application: Load matching SKILL.md, extract applicable rules for current phase.
Integration Points
| Workflow Step | Guideline Application | |---------------|----------------------| | Specification | Domain constraints, scope boundaries | | Planning | Technology decisions, architecture patterns | | Tasks | Transformation tasks, file-by-file changes | | Implementation | Code transformation rules, test patterns | | Completeness | Validation checklists, coverage criteria |
Creating New Guidelines
- Create directory:
skills/guidelines/{domain}/ - Create
SKILL.mdwith:- Metadata header (name, description, triggers)
- Rules organized by migration step
- Concrete transformation examples (before/after)
- Validation checklist
Documenting Applied Guidelines
When guidelines are applied, document in the relevant artifact:
## Applied Guidelines
- **Guideline**: struts-to-spring
- **Rules Used**: convert-action-to-controller, convert-validation
- **Reference**: skills/guidelines/struts-to-spring/SKILL.md
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/appmod-hooks
tools
VerifiedTrustedCommunity
Lifecycle hooks for the modernize-rearchitecture coordinator. Defines hook points, registered actions, and execution rules.
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