Agent-Skills.md

Agent Skills: DART Contribution Workflow

DART contribution workflow - branching, PRs, code review, dual-PR for bugfixes

UncategorizedID: dartsim/dart/dart-contribute

Repository

dartsim/dart
dartsimLicense: BSD-2-Clause
1,069298

Install this agent skill to your local

pnpm dlx add-skill https://github.com/dartsim/dart/tree/HEAD/.codex/skills/dart-contribute

Skill Files

Browse the full folder contents for dart-contribute.

Download Skill

Loading file tree…

.codex/skills/dart-contribute/SKILL.md

Skill Metadata

Name
dart-contribute
Description
"DART Contribute: branching, PRs, review workflow, and dual-PR bugfixes"
<!-- AUTO-GENERATED FILE - DO NOT EDIT MANUALLY --> <!-- Source: .claude/skills/dart-contribute/SKILL.md --> <!-- Sync script: scripts/sync_ai_commands.py --> <!-- Run `pixi run sync-ai-commands` to update -->

DART Contribution Workflow

Load this skill when contributing code to DART.

Full Documentation

For complete guide: docs/onboarding/contributing.md

For code style: docs/onboarding/code-style.md

Branch Naming

  • feature/<topic> - New features
  • fix/<topic> - Bug fixes
  • refactor/<topic> - Refactoring
  • docs/<topic> - Documentation

PR Workflow

# Features, docs, and non-bugfix refactors start from main
git checkout -b <type>/<topic> origin/main

# Bug fixes that apply to the current release line start from release-6.16
git checkout -b fix/<topic>-6.16 origin/release-6.16

# Make changes, then
pixi run lint
pixi run test-all

# After explicit maintainer/user approval, push and create PR
git push -u origin HEAD
gh pr create --draft --base <target-branch> --milestone "<milestone>"

Use --base main --milestone "DART 7.0" for main PRs and --base release-6.16 --milestone "DART 6.16.x" for release-line PRs.

Rule of thumb: run pixi run lint before committing so auto-fixes are included.

Use .github/PULL_REQUEST_TEMPLATE.md and ensure the PR description covers Summary, Motivation, Changes, Testing, Breaking Changes, and Related Issues.

Use plain descriptive commit messages and PR titles. Do not prefix them with agent tags such as [codex], [claude], or [opencode].

Milestones (Required)

Always set a milestone when creating PRs after explicit maintainer/user approval:

| Target Branch | Milestone | | -------------- | ----------------------------- | | main | DART 7.0 (or next major) | | release-6.16 | DART 6.16.x (current patch) |

# After explicit maintainer/user approval, set milestone on existing PR
gh pr edit <PR#> --milestone "DART 7.0"

# List available milestones
gh api repos/dartsim/dart/milestones --jq '.[] | .title'

CRITICAL: Bug Fix Dual-PR

Bug fixes require PRs to BOTH branches:

  1. release-6.16 - Current release
  2. main - Next release

Steps:

  1. Fix on release-6.16 first
  2. Cherry-pick to main
  3. After explicit maintainer/user approval, create separate PRs for each

CHANGELOG (After Approved PR Exists)

After the approved PR exists, check if CHANGELOG.md needs updating:

| Change Type | Update CHANGELOG? | | -------------------------------- | ------------------------------------ | | Bug fixes | ✅ Yes | | New features | ✅ Yes | | Breaking changes | ✅ Yes (in Breaking Changes section) | | Documentation improvements | ✅ Yes (in Tooling and Docs) | | CI/tooling changes | ✅ Yes (in Tooling and Docs) | | Refactoring (no behavior change) | ⚠️ Maybe (if significant) | | Dependency bumps | ⚠️ Maybe (if user-facing) | | Typo fixes | ❌ No |

Format: - Description. ([#PR](https://github.com/dartsim/dart/pull/PR))

# Example entry in CHANGELOG.md under appropriate section:
- Added AI-native documentation with AGENTS.md and module-specific guides. ([#2446](https://github.com/dartsim/dart/pull/2446))

Code Review

  • Address all feedback
  • Keep changes minimal
  • Update tests if behavior changed
  • Run full validation, then ask for explicit maintainer/user approval before pushing fixes

CI Loop

gh run watch <RUN_ID> --interval 30

Fix failures until green.