Agent Skills › dartsim/dart › dart-mechanical-refactor

dart-mechanical-refactor

GitHub

执行 DART 项目的机械重构工作流，保持行为不变。通过自动化或脚本化方式修改代码，涵盖文件重组、构建配置更新及 lint/build/test 验证，确保在提交前获得审批且无行为变更。

.codex/skills/dart-mechanical-refactor/SKILL.md dartsim/dart

Trigger Scenarios

用户请求对 Dart 代码库进行非功能性的代码结构调整需要批量重命名、移动文件或统一代码风格但保持逻辑不变的场景

Install

npx skills add dartsim/dart --skill dart-mechanical-refactor -g -y

More Options

Non-standard path

npx skills add https://github.com/dartsim/dart/tree/main/.codex/skills/dart-mechanical-refactor -g -y

Use without installing

npx skills use dartsim/dart@dart-mechanical-refactor

指定 Agent (Claude Code)

npx skills add dartsim/dart --skill dart-mechanical-refactor -a claude-code -g -y

安装 repo 全部 skill

npx skills add dartsim/dart --all -g -y

预览 repo 内 skill

npx skills add dartsim/dart --list

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 currently lives in .claude/commands/, and this generated Codex skill is a first-class Codex entrypoint.

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 lint
- pixi run build
- pixi run test-unit
- pixi run test-all when feasible
- pixi run -e cuda test-all when 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.