cuopt-developer

Guide developers through cuOpt contribution workflows across C++, Python, server, docs, and CI.

2.8k|332|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/NVIDIA/skills --skill cuopt-developer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cuopt-developer
Source: https://github.com/NVIDIA/skills/tree/main/skills/cuopt/cuopt-developer
Command: npx skills add https://github.com/NVIDIA/skills --skill cuopt-developer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides developers who want to contribute to the cuOpt codebase across C++, Python, server, docs, and CI, helping them navigate architecture and collaboration workflows.

Core Features & Use Cases

  • Guidance on contributing to solver internals, new feature work, documentation, and CI processes.
  • Clear workflow expectations: code style, testing, signing off (DCO), and PR guidelines to align with NVIDIA cuOpt.
  • Real-world scenarios include preparing patches, submitting PRs, and understanding codebase architecture for quick onboarding.

Quick Start

Use the cuopt-developer skill to guide contributions and follow the project workflow.

Frequently Asked Questions about cuopt-developer

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

FAQPage Schema
How do I contribute to cuOpt solver internals and submit a pull request?

To contribute to cuOpt, follow existing code conventions across C++ and Python, ensure tests pass, complete pre-commit checks, sign off (DCO), and submit a pull request aligned with the project's build and CI process.

What is the cuOpt contribution workflow for modifying C++ and Python code?

The cuOpt contribution workflow requires following existing code conventions, enforcing pre-commit checks, ensuring tests pass, and signing off (DCO) when modifying C++, Python, server, or CI components.

Do I need to sign off (DCO) and run pre-commit checks for cuOpt development?

Yes, cuOpt development requires DCO sign-off and pre-commit checks. You must also ensure all tests pass and follow existing code conventions before submitting your pull request to the repository.

Can I add new features to the cuOpt server and documentation through pull requests?

Yes, you can add new features to the cuOpt server, documentation, and CI processes. The contribution workflow guides preparing patches, understanding codebase architecture, and submitting pull requests for quick onboarding.

What's the best way to understand cuOpt architecture for quick onboarding?

The best way to onboard quickly is using the cuOpt developer guidance to navigate codebase architecture across C++, Python, server, docs, and CI, which clarifies workflow expectations and real-world patch preparation scenarios.