Agent Skills
› dartsim/dart
› dart-mechanical-refactor
dart-mechanical-refactor
GitHub用于执行 DART 项目的机械式重构工作流，保持行为不变前提下进行代码结构调整。
Trigger Scenarios
用户请求对 Dart 项目进行非功能性的代码重构
需要自动化或脚本化处理重复性代码变更
Install
npx skills add dartsim/dart --skill dart-mechanical-refactor -g -y
SKILL.md
Frontmatter
{
"name": "dart-mechanical-refactor",
"description": "DART Mechanical Refactor: perform a behavior-preserving mechanical refactor"
}
dart-mechanical-refactor
Use this skill in Codex to run the DART dart-mechanical-refactor workflow. The editable
workflow source lives in .claude/commands/; this file is its generated adapter
in the shared .agents/skills/ catalog.
Invocation
- Claude Code/OpenCode:
/dart-mechanical-refactor <arguments> - Codex:
$dart-mechanical-refactor <arguments>
Treat the text after the skill name as $ARGUMENTS. When the workflow
references $1, $2, etc., map those to the positional values supplied by the
user.
Command Body
Perform mechanical refactor: $ARGUMENTS
Required Reading
@AGENTS.md @CONTRIBUTING.md @docs/onboarding/code-style.md
Workflow
- Define the exact transformation and scope before editing.
- Create a branch from the target branch, usually
origin/main. - Prefer scriptable or automated edits when the transformation is repetitive.
- Keep behavior unchanged; do not mix in feature work or cleanup outside scope.
- If reorganizing files, update CMake, pixi tasks, generated indexes, and docs.
- Run focused checks first, then broader checks according to risk:
pixi run lintpixi run buildpixi run test-unitpixi run test-allwhen feasiblepixi run -e cuda test-allwhen feasible on Linux CUDA hosts
- Ask for explicit maintainer/user approval before pushing or opening a PR. After approval, open a PR with a clear scope statement and no behavior-change claim unless tested.
Output
- Transformation summary
- Files or areas changed
- Verification run
- Any residual risk
Version History
- b9fbefc Current 2026-07-19 11:29
