guidelines
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 planning and implementation skills during migration workflows. NOT for: direct execution — other skills scan this directory.
来源信息
- 仓库
- microsoft/github-copilot-modernization
- 最近来源活动
- 2026年9月22日 08:42
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 53
- Forks
- 16
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- guidelines
- description
- 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 planning and implementation skills during migration workflows. 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
## Skill Structure
```
skills/
├── guidelines/
│ └── SKILL.md # This lookup contract
├── struts-to-spring/
│ ├── SKILL.md # Independent Struts 2 → Spring Boot 3.x skill
│ └── SKILL-*.md # Supporting rule documents
└── {domain}/
└── SKILL.md # Future independent guideline skill
```
Every directory containing a `SKILL.md` is a direct child of `skills/`. Never nest one skill inside another skill.
## Lookup Mechanism
When other skills need guideline lookup:
1. **Context Analysis**: Extract technology keywords from spec/plan/code.
2. **Guideline Discovery**: Search top-level `skills/*/SKILL.md` metadata for matching source and target technologies.
3. **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
1. Create a top-level directory: `skills/{domain}/`
2. Create `SKILL.md` with:
- 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:
```markdown
## Applied Guidelines
- **Guideline**: struts-to-spring
- **Rules Used**: convert-action-to-controller, convert-validation
- **Reference**: skills/struts-to-spring/SKILL.md
```
在 GitHub 查看