Agent Skills
› dartsim/dart
› dart-docs-update
dart-docs-update
GitHub用于更新DART项目文档及AI指令可见性，无需修改代码。涵盖常规文档与AI工作流源文件的编辑、同步、验证及PR准备流程。
Trigger Scenarios
需要更新项目文档时
调整AI指令或工作流可见性时
Install
npx skills add dartsim/dart --skill dart-docs-update -g -y
SKILL.md
Frontmatter
{
"name": "dart-docs-update",
"description": "DART Docs Update: update docs or AI instruction visibility without code changes"
}
dart-docs-update
Use this skill in Codex to run the DART dart-docs-update workflow. The editable
workflow source currently lives in .claude/commands/, and this generated
Codex skill is a generated Codex adapter entrypoint.
Invocation
- Claude Code/OpenCode:
/dart-docs-update <arguments> - Codex:
$dart-docs-update <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
Update documentation: $ARGUMENTS
Required Reading
@AGENTS.md @docs/README.md @docs/AGENTS.md @docs/information-architecture.md @docs/ai/principles.md @docs/ai/verification.md @docs/onboarding/ai-tools.md @docs/onboarding/changelog.md
Workflow
- Create a branch from the target branch:
git checkout -b docs/<topic> origin/main - Edit docs and AI workflow sources only:
- Regular docs:
docs/**,README.md,AGENTS.md,CONTRIBUTING.md, andCHANGELOG.mdwhendart-changelogrequires a release-note entry - AI source files:
.claude/commands/**,.claude/skills/**
- Regular docs:
- For AI workflow changes, run
pixi run sync-ai-commands; do not hand-edit generated.opencode/or.codex/files - Classify new or moved docs by lifecycle first, then audience, then topic,
using
docs/information-architecture.md. For AI docs, keep always-loaded entrypoints compact: improve owner placement or pointers instead of duplicating procedures. - Update indexes and cross-references that point to changed docs
- Use
docs/ai/verification.mdto select the docs-only or AI docs/adapters gate set, then runpixi run lintbefore committing - Invoke the
dart-changelogroutine for theCHANGELOG.mddecision and any required entry. - Ask for explicit maintainer/user approval before pushing or opening the PR.
After approval, use
.github/PULL_REQUEST_TEMPLATE.mdand the proper milestone.
Output
- Docs and AI workflow sources changed
- Sync and verification commands run
- Changelog decision
- PR readiness, noting any external mutation that was explicitly approved
Version History
-
51b2d25
Current 2026-07-11 18:25
应用文档信息架构到代理工作流；澄清AI代理原则和可见性；明确AI工作流术语。
- e0d13fd 2026-07-05 10:37
