conga-package-upgrader

Automate NuGet package upgrades across repositories and create draft PRs.

Updated May 19, 2026
One-click install
npx skills add https://github.com/nsakthivel-conga/copilot-skills --skill conga-package-upgrader
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conga-package-upgrader
Source: https://github.com/nsakthivel-conga/copilot-skills/tree/main/conga-package-upgrader
Command: npx skills add https://github.com/nsakthivel-conga/copilot-skills --skill conga-package-upgrader

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires NuGet MCP, Python 3.10+, .NET SDK 8.0+, Git + gh CLI, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of upgrading NuGet packages across multiple repositories, reducing manual effort and potential errors.

Core Features & Use Cases

  • Automated Package Upgrade: Scan installed packages, resolve compatible versions, apply updates, and open a draft PR in one flow.
  • Single Project or Multiple Repos: Upgrade packages in a single project or across multiple repositories.
  • Use Case: Simplify the process of updating NuGet packages in your .NET projects, ensuring compatibility and reducing the risk of manual errors.

Quick Start

Upgrade all Conga packages for Conga.Revenue.Asset.API.

Frequently Asked Questions about conga-package-upgrader

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate NuGet package upgrades across multiple .NET repositories?

Automating NuGet package upgrades across repositories involves scanning installed packages, resolving compatible versions via Artifactory OData, and opening draft PRs. This Skill handles both Conga.Platform.* and Conga.Revenue.* packages end-to-end.

What is the best way to resolve compatible NuGet versions before applying updates?

Resolving compatible NuGet package versions is handled by querying Artifactory OData and NuGet MCP. The process ensures dependency compatibility before applying version updates and automating PR creation for review.

Do I need .NET SDK 8.0+ and Git CLI to run automated package upgrades?

Yes, you need .NET SDK 8.0+, Python 3.10+, Git with gh CLI, and NuGet MCP. These dependencies provide the necessary runtime, API access, and repository control to scan and upgrade packages.

How do I upgrade all Conga.Revenue packages for a single API project?

To upgrade Conga.Revenue packages for a single project, initiate the Skill flow targeting that specific repository. It scans installed packages, applies resolved version updates, and creates a draft PR for review.

Can I apply version resolutions from Artifactory OData to prevent dependency conflicts?

Yes, version resolutions from Artifactory OData are integrated into the upgrade flow. The Skill applies these resolutions to ensure package compatibility and reduce the risk of manual dependency errors.

What are the limitations of using automated PR creation for NuGet repository upgrades?

Automated PR creation opens drafts for review rather than directly merging changes. It requires local Git and gh CLI configurations to function, and upgrades are constrained by the package versions available in Artifactory OData.