dart-ci
Dart-ci assists in monitoring, viewing, and rerunning failed DART CI/CD jobs on GitHub Actions.
Install
mkdir -p .claude/skills/dart-ci && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/6926" && unzip -o skill.zip -d .claude/skills/dart-ci && rm skill.zipInstalls to .claude/skills/dart-ci
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
DART CI: GitHub Actions, cache debugging, and platform-specific failuresKey capabilities
- →Monitor PR checks
- →Debug failed CI runs
- →Rerun failed GitHub Actions jobs
- →Analyze platform-specific failures
How it works
The skill interacts with GitHub Actions to inspect logs, analyze failures, and manage job reruns.
Inputs & outputs
When to use dart-ci
- →Monitor PR check status
- →Debug failed CI runs
- →Rerun failed GitHub Actions jobs
- →Analyze platform-specific CI failures
About this skill
DART CI/CD Troubleshooting
Load this skill when debugging CI failures or working with GitHub Actions.
When the failing claim depends on model/scene structure, physics behavior, or
OSG output, also load dart-verify-sim and reproduce it with a text oracle plus
assessed visual evidence. Document a visual exception when OSG/Xvfb is
unavailable or not applicable in the failing environment.
Quick Commands
# Monitor PR checks
gh pr checks <PR_NUMBER>
gh pr view <PR_NUMBER> --json headRefOid,mergeStateStatus,statusCheckRollup
# View run details
gh run list --branch <BRANCH> -e pull_request -L 20
gh run view <RUN_ID> --json status,conclusion,url
# Debug failures
gh run view <RUN_ID> --job <JOB_ID> --log-failed
gh run view <RUN_ID> --json jobs --jq '.jobs[] | {name, databaseId}'
# Rerun failed jobs only after explicit maintainer/user approval
gh run rerun <RUN_ID> --failed
gh run rerun <RUN_ID> --job <DATABASE_ID>
Full Documentation
For complete CI/CD guide: docs/onboarding/ci-cd.md
Common Failure Modes
| Failure Type | Solution |
|---|---|
| Formatting fails | pixi run lint; push only after approval |
| Codecov patch fails | Add tests for uncovered lines |
| FreeBSD RTTI fails | Use type enums + static_cast instead of dynamic_cast |
| macOS ARM64 SEGFAULT | Replace alloca()/VLAs with std::vector<T> |
| RTD build fails | Use defensive .get(key, default) patterns |
| gz-physics fails | Reproduce with pixi run -e gazebo test-gz |
Workflow Architecture
The CI workflows that a failing PR check belongs to (full 12-workflow index:
docs/onboarding/ci-cd.md § "Workflow Index"):
| Workflow | Purpose | Platforms |
|---|---|---|
ci_ubuntu.yml | AI checks, lint, build, test, coverage | Ubuntu |
ci_macos.yml | Lint, build, test | macOS |
ci_windows.yml | Lint, build, test | Windows |
ci_freebsd.yml | Build + test (VM) | FreeBSD |
ci_simd.yml | SIMD x86 instruction-level matrix | Ubuntu x86_64 |
ci_toolchain.yml | Alternate toolchain build + test | Ubuntu |
ci_gz_physics.yml | Gazebo integration | Ubuntu |
api_doc.yml | Doxygen API docs build | Ubuntu |
Downstream Compatibility Policy
Package, exported-target, collision, constraint, and dependency changes can
affect Gazebo/gz-physics even when local unit tests pass. Reproduce those
failures with the Gazebo Pixi environment when practical:
pixi run -e gazebo test-gz.
Fast Iteration Loop
- Identify failing step from job logs
- Reproduce locally with same build toggles
- Fix the smallest failing test
- Push only after explicit maintainer/user approval, then monitor:
gh run view <RUN_ID> --json status,conclusion,url
Caching And Duration
Treat the current run and job logs as authoritative. Inspect cache restore/save steps and job timestamps before changing a key; do not rely on fixed duration or cache-speed estimates in this skill.
When not to use it
- →Untrusted fork-PR code on GPU runners
Prerequisites
Limitations
- →GPU runner must never run untrusted fork-PR code
- →Requires explicit approval for reruns
How it compares
It provides specialized troubleshooting commands for DART CI/CD workflows rather than generic CI commands.
Compared to similar skills
dart-ci side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| dart-ci (this skill) | 1 | 4mo | Review | Intermediate |
| e2e-testing-patterns | 8 | 4mo | No flags | Intermediate |
| testing-workflow | 16 | 11mo | Review | Intermediate |
| perf-lighthouse | 13 | 7mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
e2e-testing-patterns
wshobson
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
testing-workflow
amo-tech-ai
Comprehensive testing workflow for E2E, integration, and unit tests. Use when testing applications layer-by-layer, validating user journeys, or running test suites.
perf-lighthouse
tech-leads-club
Run Lighthouse audits locally via CLI or Node API, parse and interpret reports, set performance budgets. Use when measuring site performance, understanding Lighthouse scores, setting up budgets, or integrating audits into CI. Triggers on: lighthouse, run lighthouse, lighthouse score, performance audit, performance budget.
xcodebuildmcp
cameroncooke
Official skill for XcodeBuildMCP. Use when doing iOS/macOS/watchOS/tvOS/visionOS work (build, test, run, debug, log, UI automation).
verify
Use when you want to validate changes before committing, or when you need to check all React contribution requirements.
playwright-pro
alirezarezvani
Production-grade Playwright testing toolkit. Use when the user mentions Playwright tests, end-to-end testing, browser automation, fixing flaky tests, test migration, CI/CD testing, or test suites. Generate tests, fix flaky failures, migrate from Cypress/Selenium, sync with TestRail, run on BrowserStack. 55 templates, 3 agents, smart reporting.