How do I install the Dart Contribute skill?

Run npx skillmds@latest add majiayu000/dart-contribute-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Dart Contribute skill do?

DART contribution workflow - branching, PRs, code review, dual-PR for bugfixes It is listed under Productivity on SkillMD.

Is Dart Contribute safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Dart Contribute?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Dart Contribute free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Dart Contribute?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Dart Contribute by majiayu000 — Agent Skill

Name: Dart Contribute
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

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

# Create branch
git checkout -b <type>/<topic> origin/main

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

# Push and create PR
git push -u origin HEAD
gh pr create --draft --milestone "DART 7.0"

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.

Milestones (Required)

Always set a milestone when creating PRs:

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

# 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:

release-6.16 - Current release
main - Next release

Steps:

Fix on release-6.16 first
Cherry-pick to main
Create separate PRs for each

CHANGELOG (After PR Created)

After creating a PR, 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 before pushing fixes

CI Loop

gh run watch <RUN_ID> --interval 30

Fix failures until green.

---name: dart-contribute-2description: DART contribution workflow - branching, PRs, code review, dual-PR for bugfixes---# DART Contribution WorkflowLoad this skill when contributing code to DART.## Full DocumentationFor 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```bash# Create branchgit checkout -b <type>/<topic> origin/main# Make changes, thenpixi run lintpixi run test-all# Push and create PRgit push -u origin HEADgh pr create --draft --milestone "DART 7.0"```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.## Milestones (Required)Always set a milestone when creating PRs:| Target Branch | Milestone || -------------- | ----------------------------- || `main` | `DART 7.0` (or next major) || `release-6.16` | `DART 6.16.x` (current patch) |```bash# Set milestone on existing PRgh pr edit <PR#> --milestone "DART 7.0"# List available milestonesgh api repos/dartsim/dart/milestones --jq '.[] | .title'```## CRITICAL: Bug Fix Dual-PRBug fixes require PRs to **BOTH** branches:1. **`release-6.16`** - Current release2. **`main`** - Next releaseSteps:1. Fix on `release-6.16` first2. Cherry-pick to `main`3. Create separate PRs for each## CHANGELOG (After PR Created)After creating a PR, 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))````bash# 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 before pushing fixes## CI Loop```bashgh run watch <RUN_ID> --interval 30```Fix failures until green.

Frequently asked questions

Dart Contribute