How does this skill handle code linting?

The skill instructs Claude to run 'pixi run lint' before committing, ensuring that auto-fixes for code style are included in your contribution automatically.

Which milestone should I use for my Pull Request?

PRs targeting the main branch typically use the next major milestone (e.g., DART 7.0), while PRs for release branches use the current patch milestone (e.g., DART 6.16.x).

When should I update the CHANGELOG.md?

Updates are required for bug fixes, new features, breaking changes, and significant documentation or tooling improvements. Minor typo fixes do not require a changelog entry.

What is the dual-PR requirement in DART?

Bug fixes in DART require two separate Pull Requests: one for the current stable release branch (e.g., release-6.16) and one cherry-picked to the main branch for the next major release.

DART Contribution Workflow

Name: DART Contribution Workflow
Author: dartsim

bydartsim

•

1,047

Herramientas de Colaboración

Streamlines the contribution process for the DART physics engine by enforcing branching standards, PR requirements, and dual-PR bugfix protocols.

Acerca de

This skill provides specialized guidance for developers contributing to the DART (Dynamic Animation and Robotics Toolkit) project, a C++20 physics engine. It automates and enforces the repository's specific contribution workflow, including branch naming conventions, mandatory linting via Pixi, and the critical dual-PR requirement for bug fixes across release and main branches. By integrating with the GitHub CLI, it helps contributors manage milestones, PR templates, and CHANGELOG updates, ensuring all contributions meet the project's rigorous maintenance standards.

Características Principales

Context-aware CHANGELOG maintenance based on the nature of the changes
Pre-commit linting and testing automation using the Pixi task runner
Dual-PR workflow management for backporting bug fixes to release branches
1,047 GitHub stars
Automated branch naming enforcement for features, fixes, and refactors
Standardized PR creation with automated milestone and template application

Casos de Uso

Submitting new features or architectural refactors to the DART main branch
Implementing and backporting critical bug fixes to stable release branches
Standardizing open-source contributions to ensure CI/CD compliance and code quality

Acerca de

Características Principales

Context-aware CHANGELOG maintenance based on the nature of the changes
Pre-commit linting and testing automation using the Pixi task runner
Dual-PR workflow management for backporting bug fixes to release branches
1,047 GitHub stars
Automated branch naming enforcement for features, fixes, and refactors
Standardized PR creation with automated milestone and template application

Casos de Uso

Submitting new features or architectural refactors to the DART main branch
Implementing and backporting critical bug fixes to stable release branches
Standardizing open-source contributions to ensure CI/CD compliance and code quality