文件最后提交记录最后更新时间
fix(atomgit): harden review and issue reliability Default generic PR review prompts to atomgit-pr-review and expand its extracted context with commits and existing comments. Retry safe AtomGit API reads on transient TLS or connection failures and validate issue labels before create or update requests so cross-repo flows fail clearly. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: XiaoqiangWu <wuxiaoqiang.rtos@huawei.com> 1 个月前
feat(atomgit): support cross-repo context and comments Add cross-repo owner, repo, and URL targeting to the generic AtomGit PR, issue, review, and review-resolution flows. Move repository context parsing into the SDK and fetch PR and issue comments by default so agents have fuller review context. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: XiaoqiangWu <wuxiaoqiang.rtos@huawei.com> 1 个月前
architecture: require readme contract review Treat package README files as local architecture contracts. Add README drift checks to architecture review prompts and context extraction. Signed-off-by: XiaoqiangWu <wuxiaoqiang.rtos@huawei.com> 1 个月前
skills: refine pr workflow rules Update the AtomGit PR and PR review skills so they check README sync based on user-facing changes and require meaningful verification for dependency or setup/build workflow updates, including dual-platform Docker validation requirements. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: XiaoqiangWu <wuxiaoqiang.rtos@huawei.com> 23 天前
skills: refine pr workflow rules Update the AtomGit PR and PR review skills so they check README sync based on user-facing changes and require meaningful verification for dependency or setup/build workflow updates, including dual-platform Docker validation requirements. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: XiaoqiangWu <wuxiaoqiang.rtos@huawei.com> 23 天前
atomgit: improve review follow-up handling Consolidate the PR review follow-up changes into one commit so the branch history stays easy to review and revert. The squashed change keeps the pagination safety fix, the improved review-thread grouping and reply handling, the added regression coverage, and the threaded default in the review-resolution skill to avoid extra top-level replies. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: liuweihong <liuweihong8@huawei.com> 29 天前
openharmony: generalize host setup guidance Document portable HDC usage by resolving hdc from PATH instead of referencing a host-specific SDK path. Update the board skills to avoid assuming a fixed TCP target and to ask the user for the board IP or confirm direct USB access when transport details are not known. Describe USB HDC as a valid direct transport, while keeping TCP as the preferred option after enabling tmode port 8710 over USB. Clarify that OH_ROOT, OH_DOWNLOAD_ROOT, and OH_CUSTOM_ROOT are host-side cross-build variables and keep pointing users to the repository docs when setup inputs are missing. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: XiaoqiangWu <wuxiaoqiang.rtos@huawei.com> 23 天前
architecture: require readme contract review Treat package README files as local architecture contracts. Add README drift checks to architecture review prompts and context extraction. Signed-off-by: XiaoqiangWu <wuxiaoqiang.rtos@huawei.com> 1 个月前
openharmony: generalize host setup guidance Document portable HDC usage by resolving hdc from PATH instead of referencing a host-specific SDK path. Update the board skills to avoid assuming a fixed TCP target and to ask the user for the board IP or confirm direct USB access when transport details are not known. Describe USB HDC as a valid direct transport, while keeping TCP as the preferred option after enabling tmode port 8710 over USB. Clarify that OH_ROOT, OH_DOWNLOAD_ROOT, and OH_CUSTOM_ROOT are host-side cross-build variables and keep pointing users to the repository docs when setup inputs are missing. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: XiaoqiangWu <wuxiaoqiang.rtos@huawei.com> 23 天前
openharmony: generalize host setup guidance Document portable HDC usage by resolving hdc from PATH instead of referencing a host-specific SDK path. Update the board skills to avoid assuming a fixed TCP target and to ask the user for the board IP or confirm direct USB access when transport details are not known. Describe USB HDC as a valid direct transport, while keeping TCP as the preferred option after enabling tmode port 8710 over USB. Clarify that OH_ROOT, OH_DOWNLOAD_ROOT, and OH_CUSTOM_ROOT are host-side cross-build variables and keep pointing users to the repository docs when setup inputs are missing. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: XiaoqiangWu <wuxiaoqiang.rtos@huawei.com> 23 天前
docs: update openEuler docker verify workflow Document the verified clean-container flow. Use a standalone clone with submodules. Run setup.sh without --skip-submodules. Signed-off-by: XiaoqiangWu <wuxiaoqiang.rtos@huawei.com> 27 天前
docs: add Docker verification skills and CONTRIBUTING guidelines - Added AI agent skills (ibrobot-docker-verify, ibrobot-docker-verify-oee) to run end-to-end setup.sh and build.sh verification in isolated containers. - Added CONTRIBUTING.md and CONTRIBUTING.en.md to clarify remote/fork setup for developers. - Updated .agents/skills/README.md to register the new verification skills. Signed-off-by: XiaoqiangWu <wuxiaoqiang.rtos@huawei.com> 28 天前
refactor(skills): update description field to if-then trigger style Update skill description fields to use conditional trigger format with bilingual keywords (Chinese/English) for better skill matching. Signed-off-by: XiaoqiangWu <wuxiaoqiang.rtos@huawei.com> 2 个月前
refactor(skills): update description field to if-then trigger style Update skill description fields to use conditional trigger format with bilingual keywords (Chinese/English) for better skill matching. Signed-off-by: XiaoqiangWu <wuxiaoqiang.rtos@huawei.com> 2 个月前
openharmony: generalize host setup guidance Document portable HDC usage by resolving hdc from PATH instead of referencing a host-specific SDK path. Update the board skills to avoid assuming a fixed TCP target and to ask the user for the board IP or confirm direct USB access when transport details are not known. Describe USB HDC as a valid direct transport, while keeping TCP as the preferred option after enabling tmode port 8710 over USB. Clarify that OH_ROOT, OH_DOWNLOAD_ROOT, and OH_CUSTOM_ROOT are host-side cross-build variables and keep pointing users to the repository docs when setup inputs are missing. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: XiaoqiangWu <wuxiaoqiang.rtos@huawei.com> 23 天前
refactor(skills): update description field to if-then trigger style Update skill description fields to use conditional trigger format with bilingual keywords (Chinese/English) for better skill matching. Signed-off-by: XiaoqiangWu <wuxiaoqiang.rtos@huawei.com> 2 个月前
skills: add lerobot patch workflow Add ibrobot-lerobot-patch so agents can export local lerobot changes. Ship a helper that resolves the active tag and allocates patch ids. Update the target series file while keeping manifest scoping manual. Signed-off-by: XiaoqiangWu <wuxiaoqiang.rtos@huawei.com> 23 天前
skills: add lerobot patch workflow Add ibrobot-lerobot-patch so agents can export local lerobot changes. Ship a helper that resolves the active tag and allocates patch ids. Update the target series file while keeping manifest scoping manual. Signed-off-by: XiaoqiangWu <wuxiaoqiang.rtos@huawei.com> 23 天前
model_utils: add RKNN model export and conversion for RK3588 NPU Add export_onnx_rknn.py to model_utils for RK3588 NPU deployment, alongside existing 310B (ATC) and 3403 export scripts. RKNN-specific optimizations: - Strip extra intermediate outputs, keeping only the action output - Enable constant folding and onnxsim simplification - Use opset 13 for best rknn-toolkit2 compatibility - Support one-click ONNX-to-RKNN conversion via dedicated .venv-rknn Also add rknn-convert agent skill with SKILL.md and convert_to_rknn.py for standalone RKNN conversion using rknn-toolkit2 2.3.2. Why a separate venv: rknn-toolkit2 requires torch<=2.4.0 and numpy<=1.26.4, which conflicts with lerobot (torch>=2.7, numpy>=2.0). The dedicated .venv-rknn isolates these dependencies. Supports two modes: - --onnx: process existing ONNX (strip + simplify + convert) - --policy_path: export from safetensors (when lerobot config compatible) Signed-off-by: XiaoqiangWu <wuxiaoqiang.rtos@huawei.com> 24 天前
skills: add lerobot patch workflow Add ibrobot-lerobot-patch so agents can export local lerobot changes. Ship a helper that resolves the active tag and allocates patch ids. Update the target series file while keeping manifest scoping manual. Signed-off-by: XiaoqiangWu <wuxiaoqiang.rtos@huawei.com> 23 天前
README.md

AI Agent 技能库 (Skills)

此目录包含了专为 AI Agent(如 Claude Code)设计的技能插件,用于自动化 IB-Robot 项目中的各种开发工作流。每个技能都定义了精准的触发条件(Description),并提供了执行复杂任务所需的工具和上下文。

技能清单

技能名称 分类 主要触发场景 (Triggers)
intro 引导 「介绍」「有哪些功能」「help」「入门」「intro」等,作为所有 skill 的导航入口。
ibrobot-env 环境 加载 .shrc_local、设置 ROS_DOMAIN_ID、解决 ModuleNotFoundError 等。
ibrobot-build 操作 执行项目编译 (colcon build)、构建特定 package 或修复编译错误。
ibrobot-launch 操作 启动机器人系统、运行仿真、测试 ACT 推理或进行遥操作调试。
ibrobot-hdc 板端 连接 BQ3588HM 开发板,执行 HDC shell / file send / file recv。
ibrobot-bq3588hm-oh 板端 记录 BQ3588HM 板上的 OpenHarmony ROS / Python / RKNN 运行时事实。
bq3588-oh-rknn 板端 在 BQ3588HM 上拉起 cloud_inference.launch.py 的 RKNN 推理路径。
rknn-convert 模型 将 ONNX 转成 RKNN,并维护主 venv 导出 ONNX、.venv-rknn 转 RKNN 的流程边界。
ibrobot-architecture 知识 理解 SSOT 模式、修改 robot_config、解释数据流或契约设计。
ibrobot-lerobot-patch 工作流 libs/lerobot 的本地改动导出为 third_party/patches/lerobot/<tag>/*.patch,并通过辅助脚本同步 series/manifest/test
ibrobot-git-flow 工作流 提交代码、推送至个人仓库、确保符合 openEuler DCO/Commit 规范。
ibrobot-docker-verify 验证 在干净 Ubuntu 22.04 Docker 容器中端到端验证 setup.sh + build.sh。
ibrobot-docker-verify-oee 验证 在 openEuler Embedded (aarch64) Docker 容器中端到端验证 setup.sh + build.sh。
atomgit-collaboration AtomGit 拦截泛化的 PR / Issue / review / comment 请求,并路由到具体 AtomGit skill。
atomgit-pr AtomGit 管理 PR 生命周期:创建、读取上下文、更新标题/描述、生成摘要。
atomgit-issue AtomGit 管理 Issue 生命周期:创建、读取详情、更新内容、关闭/重开。
atomgit-pr-review AtomGit 对 PR 进行代码质量审查、逻辑检查、发现潜在 Bug 并提交检视意见。
atomgit-pr-architecture-review AtomGit 验证 PR 是否符合 SSOT、契约驱动设计等项目架构支柱。
atomgit-review-resolution AtomGit 处理评审意见:获取未解决评论、修复代码、回复并闭环 review。

技能分类说明

🧭 引导入口

  • 技能导航 (intro): 所有 skill 的统一入口,展示分类列表与使用示例,并根据仓库状态智能推荐最合适的 skill。

🤖 IB-Robot 核心操作

这些技能旨在处理 IB-Robot 软件栈特有的日常开发任务。

  • 环境管理 (ibrobot-env): 确保 shell 上下文正确继承了项目特有的环境变量。
  • 编译构建 (ibrobot-build): 封装了 ROS 2 复杂的编译参数,确保构建的一致性。
  • 系统启动 (ibrobot-launch): 机器人系统的总入口,支持一键拉起复杂的节点拓扑。
  • 板端连接 (ibrobot-hdc): 统一封装 BQ3588HM 的 HDC over TCP 访问与文件传输。
  • 板端事实 (ibrobot-bq3588hm-oh): 汇总 BQ3588HM 板上的 OpenHarmony、ROS、Python、RKNN 运行时事实。
  • 板端 RKNN 运行 (bq3588-oh-rknn): 专门处理 cloud_inference.launch.py device:=rknn 的板端环境叠加与启动。
  • RKNN 转换 (rknn-convert): 明确 ONNX 导出与 RKNN 转换的边界,避免主 venv.venv-rknn 污染。
  • 架构顾问 (ibrobot-architecture): 充当项目的架构师,解答一切关于设计模式和配置规范的问题。
  • LeRobot 补丁纳管 (ibrobot-lerobot-patch): 把 libs/lerobot 的本地改动回收为受管 patch 栈,而不是直接提交子模块 gitlink。
  • 工程规范 (ibrobot-git-flow): 自动化执行开源社区繁琐的提交规范校验。
  • 容器验证 (ibrobot-docker-verify): 在全新 Ubuntu 22.04 Docker 容器中运行 setup.sh 和 build.sh 的完整端到端验证,确保修改不会破坏首次安装体验。
  • openEuler 容器验证 (ibrobot-docker-verify-oee): 在 openEuler Embedded aarch64 Docker 容器(qemu-user 模拟 chroot)中端到端验证 setup.sh + build.sh,以 root 用户模拟真实开发板操作环境。

🌐 AtomGit 自动化工具

这些技能通过集成 AtomGit API,实现了 PR / Issue 生命周期和代码审查的自动化。

⚠️ 前置条件:配置 AtomGit Token

使用 AtomGit 相关技能前,必须先配置 Personal Access Token:

  1. 访问 https://atomgit.com 并登录
  2. 点击右上角头像 → 个人设置
  3. 找到「访问令牌」选项
  4. 点击「新建访问令牌」,勾选 repopull_request 权限
  5. 立即复制保存 Token(只显示一次)

设置环境变量:

export ATOMGIT_TOKEN="your_token_here"

Token 配置存储在项目根目录的 config.json 中,通过环境变量 $ATOMGIT_TOKEN 引用。

  • PR 工作流 (atomgit-pr): 面向 PR 资源本身,覆盖创建、读取管理上下文、更新描述等全生命周期动作;如果目标是通用 review,应改用 atomgit-pr-review
  • Issue 工作流 (atomgit-issue): 面向 Issue 资源本身,覆盖创建、读取、更新与状态流转,支持 --owner / --repo / --url 进行跨仓库调用。
  • 通用评审 (atomgit-pr-review): 利用 LLM 充当第一道代码防线,默认提取变更、提交和已有评论,支持直接从 PR 链接解析目标仓库与编号。
  • 架构扫描 (atomgit-pr-architecture-review): 专门检查是否违背了 SSOT 等核心架构原则。
  • 意见处理 (atomgit-review-resolution): 实现从“发现问题”到“修复代码/回复评论”的自动化闭环,支持直接从 PR 链接解析目标仓库与编号。
  • 协作路由 (atomgit-collaboration): 面向“看看这个 PR / 帮我跟进这个评论”这类泛化协作请求,先识别意图,再分流到具体 AtomGit skill。

边界说明: atomgit-pr-architecture-review 仍然是 IB_Robot 专用 能力;本次跨仓库能力只开放给通用 PR / Issue / review / review-resolution 流程。

命名与拆分原则(Agent Skill Best Practice)

  1. 优先按资源/工作流命名,不按单个动作命名:用 atomgit-pratomgit-issue,不要用 atomgit-submit-pr 这类只覆盖一个动词的名字。Agent 看到资源名,更容易把 create / fetch / update / summarize 归到同一个 skill,而不是回退到 GitHub 默认能力。
  2. description 要覆盖完整生命周期动词:同一个 skill 的 description 应同时包含 create / get / fetch / update / close / reply 等常见动作,避免名字很宽、触发词很窄。
  3. 先按“平台 + 资源”拆,再按“专业能力”细分atomgit-pratomgit-issue 负责资源生命周期;atomgit-pr-reviewatomgit-pr-architecture-review 负责不同评审维度;atomgit-review-resolution 负责 review follow-up。只有当执行流程、输入输出和成功标准明显不同,才继续拆 skill。
  4. 显式写出平台优先级:在本仓库里,只要目标是 PR / Issue / review comment 且用户未明确指定 GitHub,就应优先触发 AtomGit skill。
  5. 为泛化协作请求保留一个薄路由层:当用户只说“帮我看看这个 PR / 评论 / 协作状态”而未说明动作时,用 atomgit-collaboration 先识别资源与意图,再转入具体 skill,避免直接落到 GitHub 默认能力。

如何增加新技能

若要向本项目添加新技能,请遵循以下步骤:

  1. .agents/skills/ 下创建一个新目录。
  2. 添加 SKILL.md 文件,确保 description 字段采用 if-then 条件触发风格(包含中英双语关键词),并在涉及第三方平台时明确写出平台优先级。
  3. 编写技能所需的配套脚本(Python/Bash)或库文件。
  4. 更新此 README.md 文件,将新技能添加到清单表格中。