dotnet-upgrade

작성자: github

다중 프로젝트 솔루션 전반에 걸친 .NET 프레임워크 업그레이드의 분석, 계획 및 실행을 위한 포괄적인 프롬프트입니다. 프로젝트 검색 및 분류, 종속성 분석, 프레임워크 대상 지정, 코드 현대화, 호환성 변경 감지 등 전체 업그레이드 수명 주기를 다룹니다. 전략, CI/CD 파이프라인 업데이트, 테스트 검증, 버전 관리 관행을 아우르는 9개 범주로 구성된 24개 이상의 즉시 사용 가능한 프롬프트를 제공합니다. .NET 업그레이드 어시스턴트 사용에 대한 지침을 제공합니다...

npx skills add https://github.com/github/awesome-copilot --skill dotnet-upgrade

Project Discovery & Assessment

  • name: "Project Classification Analysis" prompt: "Identify all projects in the solution and classify them by type (.NET Framework, .NET Core, .NET Standard). Analyze each .csproj for its current TargetFramework and SDK usage."

  • name: "Dependency Compatibility Review" prompt: "Review external and internal dependencies for framework compatibility. Determine the upgrade complexity based on dependency graph depth."

  • name: "Legacy Package Detection" prompt: "Identify legacy packages.config projects needing migration to PackageReference format."

Upgrade Strategy & Sequencing

  • name: "Project Upgrade Ordering" prompt: "Recommend a project upgrade order from least to most dependent components. Suggest how to isolate class library upgrades before API or Azure Function migrations."

  • name: "Incremental Strategy Planning" prompt: "Propose an incremental upgrade strategy with rollback checkpoints. Evaluate the use of Upgrade Assistant or manual upgrades based on project structure."

  • name: "Progress Tracking Setup" prompt: "Generate an upgrade checklist for tracking build, test, and deployment readiness across all projects."

Framework Targeting & Code Adjustments

  • name: "Target Framework Selection" prompt: "Suggest the correct TargetFramework for each project (e.g., net8.0). Review and update deprecated SDK or build configurations."

  • name: "Code Modernization Analysis" prompt: "Identify code patterns needing modernization (e.g., WebHostBuilderHostBuilder). Suggest replacements for deprecated .NET APIs and third-party libraries."

  • name: "Async Pattern Conversion" prompt: "Recommend conversion of synchronous calls to async where appropriate for improved performance and scalability."

NuGet & Dependency Management

  • name: "Package Compatibility Analysis" prompt: "Analyze outdated or incompatible NuGet packages and suggest compatible versions. Identify third-party libraries that lack .NET 8 support and provide migration paths."

  • name: "Shared Dependency Strategy" prompt: "Recommend strategies for handling shared dependency upgrades across projects. Evaluate usage of legacy packages and suggest alternatives in Microsoft-supported namespaces."

  • name: "Transitive Dependency Review" prompt: "Review transitive dependencies and potential version conflicts after upgrade. Suggest resolution strategies for dependency conflicts."

CI/CD & Build Pipeline Updates

  • name: "Pipeline Configuration Analysis" prompt: "Analyze YAML build definitions for SDK version pinning and recommend updates. Suggest modifications for UseDotNet@2 and NuGetToolInstaller tasks."

  • name: "Build Pipeline Modernization" prompt: "Generate updated build pipeline snippets for .NET 8 migration. Recommend validation builds on feature branches before merging to main."

  • name: "CI Automation Enhancement" prompt: "Identify opportunities to automate test and build verification in CI pipelines. Suggest strategies for continuous integration validation."

Testing & Validation

  • name: "Build Validation Strategy" prompt: "Propose validation checks to ensure the upgraded solution builds and runs successfully. Recommend automated test execution for unit and integration suites post-upgrade."

  • name: "Service Integration Verification" prompt: "Generate validation steps to verify logging, telemetry, and service connectivity. Suggest strategies for verifying backward compatibility and runtime behavior."

  • name: "Deployment Readiness Check" prompt: "Recommend UAT deployment verification steps before production rollout. Create comprehensive testing scenarios for upgraded components."

Breaking Change Analysis

  • name: "API Deprecation Detection" prompt: "Identify deprecated APIs or removed namespaces between target versions. Suggest automated scanning using .NET Upgrade Assistant and API Analyzer."

  • name: "API Replacement Strategy" prompt: "Recommend replacement APIs or libraries for known breaking areas. Review configuration changes such as Startup.csProgram.cs refactoring."

  • name: "Regression Testing Focus" prompt: "Suggest regression testing scenarios focused on upgraded API endpoints or services. Create test plans for critical functionality validation."

Version Control & Commit Strategy

  • name: "Branching Strategy Planning" prompt: "Recommend branching strategy for safe upgrade with rollback capability. Generate commit templates for partial and complete project upgrades."

  • name: "PR Structure Optimization" prompt: "Suggest best practices for creating structured PRs (Upgrade to .NET [Version]). Identify tagging strategies for PRs involving breaking changes."

  • name: "Code Review Guidelines" prompt: "Recommend peer review focus areas (build, test, and dependency validation). Create checklists for effective upgrade reviews."

Documentation & Communication

  • name: "Upgrade Documentation Strategy" prompt: "Suggest how to document each project's framework change in the PR. Propose automated release note generation summarizing upgrades and test results."

  • name: "Stakeholder Communication" prompt: "Recommend communicating version upgrades and migration timelines to consumers. Generate documentation templates for dependency updates and validation results."

  • name: "Progress Tracking Systems" prompt: "Suggest maintaining an upgrade summary dashboard or markdown checklist. Create templates for tracking upgrade progress across multiple projects."

Tools & Automation

  • name: "Upgrade Tool Selection" prompt: "Recommend when and how to use: .NET Upgrade Assistant, dotnet list package --outdated, dotnet migrate, and graph.json dependency visualization."

  • name: "Analysis Script Generation" prompt: "Generate scripts or prompts for analyzing dependency graphs before upgrading. Propose AI-assisted prompts for Copilot to identify upgrade issues automatically."

  • name: "Multi-Repository Validation" prompt: "Suggest how to validate automation output across multiple repositories. Create standardized validation workflows for enterprise-scale upgrades."

Final Validation & Delivery

  • name: "Final Solution Validation" prompt: "Generate validation steps to confirm the final upgraded solution passes all validation checks. Suggest production deployment verification steps post-upgrade."

  • name: "Deployment Readiness Confirmation" prompt: "Recommend generating final test results and build artifacts. Create a checklist summarizing completion across projects (builds/tests/deployment)."

  • name: "Release Documentation" prompt: "Generate a release note summarizing framework changes and CI/CD updates. Create comprehensive upgrade summary documentation."


github의 다른 스킬

console-rendering
github
Go에서 struct 태그 기반 콘솔 렌더링 시스템 사용 지침
official
acquire-codebase-knowledge
github
사용자가 기존 코드베이스에 대한 매핑, 문서화, 또는 온보딩을 명시적으로 요청할 때 이 스킬을 사용하세요. "이 코드베이스를 매핑해줘", "문서화해줘"와 같은 프롬프트에서 트리거됩니다.
official
acreadiness-assess
github
현재 리포
official
acreadiness-generate-instructions
github
AgentRC 명령어를 통해 맞춤형 AI 에이전트 지침 파일을 생성합니다. .github/copilot-instructions.md 파일을 생성합니다(기본값, VS Code의 Copilot에 권장됨).
official
acreadiness-policy
github
사용자가 AgentRC 정책을 선택, 작성 또는 적용할 수 있도록 지원합니다. 정책은 관련 없는 검사를 비활성화하고, 영향/수준을 재정의하며, 설정을 통해 준비 상태 점수를 사용자 지정합니다.
official
add-educational-comments
github
코드 파일에 교육용 주석을 추가하여 효과적인 학습 자료로 변환합니다. 설명의 깊이와 어조를 세 가지 설정 가능한 지식 수준(초급, 중급, 고급)에 맞게 조정합니다. 파일이 제공되지 않으면 자동으로 요청하며, 빠른 선택을 위해 번호 목록 매칭을 제공합니다. 교육용 주석만을 사용하여 파일을 최대 125%까지 확장합니다(엄격한 제한: 새 줄 400개, 1,000줄 초과 파일의 경우 300개). 파일 인코딩, 들여쓰기 스타일, 구문 정확성 등을 유지합니다.
official
adobe-illustrator-scripting
github
Adobe Illustrator 자동화 스크립트를 ExtendScript(JavaScript/JSX)로 작성, 디버깅 및 최적화합니다. 스크립트를 생성하거나 수정하여 조작할 때 사용합니다.
official
agent-governance
github
선언적 정책, 의도 분류, AI 에이전트 도구 접근 및 행동 제어를 위한 감사 추적. 구성 가능한 거버넌스 정책은 허용/차단된 도구, 콘텐츠 필터, 속도 제한, 승인 요구 사항을 정의하며, 코드가 아닌 구성으로 저장됨. 의미론적 의도 분류는 패턴 기반 신호를 사용하여 도구 실행 전에 위험한 프롬프트(데이터 유출, 권한 상승, 프롬프트 인젝션)를 탐지함. 도구 수준 거버넌스 데코레이터는 함수에서 정책을 적용함...
official