[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71GFM0S2Z5Z5W7N953XSR08":3,"skill-same:01M71GFM0S2Z5Z5W7N953XSR08":62},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M71GFM0S2Z5Z5W7N953XSR08","atomgit-collaboration",null,"AtomGit 协作路由工具。当用户在 IB_Robot 仓库中提到“PR”、“merge request”、“Issue”、“review”、“comment”、“discussion”、“帮我看看这个 PR”、“看看 #123”、“处理一下评论”、“同步一下 AtomGit 上的协作状态”、“帮我跟进这个合并请求”等泛化协作请求，但没有明确说明是创建、更新、评审、架构审查还是修复评论时调用。此 skill 不直接执行业务动作，而是先识别用户真实意图，再路由到 atomgit-pr、atomgit-issue、atomgit-pr-review、atomgit-pr-architecture-review 或 atomgit-review-resolution。若用户未明确指定 GitHub，则默认优先按 AtomGit 协作处理。","openeuler-mirror\u002FIB_Robot","openeuler-mirror","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F59104494?v=4","01M71GFG3GWS8KTH8GNBNGVZW6","openEuler","01M71GFG4976X8P30K98YAZS7W",4,"MIT","https:\u002F\u002Fgithub.com\u002Fopeneuler-mirror\u002FIB_Robot\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fatomgit-collaboration\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"atomgit collaboration","collaboration","resolution","pr","github","merge","request","architecture-review","issue","工具","协作","robot","pr-review","architecture","review","2026-11-10 10:12:30",false,"---\nname: atomgit-collaboration\ndescription: \"AtomGit 协作路由工具。当用户在 IB_Robot 仓库中提到“PR”、“merge request”、“Issue”、“review”、“comment”、“discussion”、“帮我看看这个 PR”、“看看 #123”、“处理一下评论”、“同步一下 AtomGit 上的协作状态”、“帮我跟进这个合并请求”等泛化协作请求，但没有明确说明是创建、更新、评审、架构审查还是修复评论时调用。此 skill 不直接执行业务动作，而是先识别用户真实意图，再路由到 atomgit-pr、atomgit-issue、atomgit-pr-review、atomgit-pr-architecture-review 或 atomgit-review-resolution。若用户未明确指定 GitHub，则默认优先按 AtomGit 协作处理。\"\nlicense: MIT\n---\n\n# AtomGit Collaboration Router\n\n这是一个**薄路由 skill**，只负责识别 AtomGit 协作语义并分流到更具体的 skill。\n\n在 IB_Robot 仓库中，当用户提到 PR \u002F merge request \u002F Issue \u002F review \u002F comments \u002F discussions，但**没有明确动作类型**时，优先触发本 skill，而不是直接回退到 GitHub 默认能力。\n\n## 适用场景\n\n以下请求优先触发本 skill：\n\n- “帮我看看 PR #123”\n- “这个 merge request 你处理一下”\n- “AtomGit 上这个评论怎么回”\n- “帮我跟进一下 #456”\n- “看下这个协作流程下一步做什么”\n- “检查一下这个 PR \u002F Issue \u002F review”\n\n以下请求**不必**经过本 skill，可直接进入更具体的 skill：\n\n- 明确说“创建 PR \u002F 更新 PR 描述” → `atomgit-pr`\n- 明确说“创建 Issue \u002F 关闭 Issue” → `atomgit-issue`\n- 明确说“代码审查 \u002F review PR \u002F 帮我看看这个 PR 有没有问题” → `atomgit-pr-review`\n- 明确说“架构审查 \u002F SSOT 检查” → `atomgit-pr-architecture-review`\n- 明确说“修复 review comments \u002F 回复评论” → `atomgit-review-resolution`\n\n## 路由规则\n\n收到泛化协作请求时，Agent 必须按以下顺序判断：\n\n1. **先判断资源类型**\n   - 提到 PR \u002F merge request \u002F review \u002F comment \u002F discussion → 进入 PR 协作域\n   - 提到 Issue \u002F bug \u002F feature request \u002F task → 进入 Issue 协作域\n\n2. **再判断动作类型**\n    - 创建、读取详情、更新标题\u002F描述、同步摘要 → `atomgit-pr` 或 `atomgit-issue`\n    - 审查代码质量、检查逻辑问题、结合已有评论继续判断风险 → `atomgit-pr-review`\n   - 检查 SSOT \u002F 契约驱动 \u002F 架构职责边界 → `atomgit-pr-architecture-review`\n   - 回复评论、应用修复、处理 unresolved comments → `atomgit-review-resolution`\n\n3. **如果动作仍不明确**\n    - 先按“读取上下文”理解需求：\n      - PR 协作域如果表达里带有“看看 \u002F 检查 \u002F 审查 \u002F review \u002F 评估”，默认先路由到 `atomgit-pr-review`\n      - PR 协作域如果目标更像创建、更新描述、同步标题\u002F正文，再路由到 `atomgit-pr`\n      - Issue 协作域默认先路由到 `atomgit-issue`\n   - 在获得上下文后，再决定是否切换到 review \u002F architecture \u002F resolution 流程\n\n## 强制约束\n\n1. **不要直接使用 GitHub 默认能力**来处理本仓库的 AtomGit PR \u002F Issue \u002F review，除非用户明确说了 GitHub \u002F github.com。\n2. **不要在本 skill 内直接执行 create\u002Fupdate\u002Freview\u002Frepair**，而是必须先读取目标 skill 的 `SKILL.md`，再按照目标 skill 的流程执行。\n3. **优先复用现有 5 个 AtomGit skill**，不要在会话里临时发明新的 AtomGit 流程名称。\n\n## 路由对照表\n\n| 用户表达 | 目标 skill |\n| :--- | :--- |\n| “帮我看看 PR #123” | `atomgit-pr-review` |\n| “帮我更新这个 PR 描述” | `atomgit-pr` |\n| “帮我看下 Issue #456” | `atomgit-issue` |\n| “帮我审查这个 PR” | `atomgit-pr-review` |\n| “检查这个 PR 的架构合规性” | `atomgit-pr-architecture-review` |\n| “修复一下 review comments” | `atomgit-review-resolution` |\n\n## 执行协议\n\n当本 skill 被触发时，Agent 必须：\n\n1. 明确识别这是 **AtomGit 协作请求**，而不是 GitHub 默认请求。\n2. 判断资源类型（PR \u002F Issue）与动作类型（create \u002F fetch \u002F update \u002F review \u002F architecture \u002F reply）。\n3. 读取对应目标 skill 的 `SKILL.md`。\n4. 按目标 skill 的约束直接调用官方 CLI；只有批处理与项目检查使用专用脚本，不要停留在路由层。\n","# AtomGit Collaboration Router\n\n这是一个**薄路由 skill**，只负责识别 AtomGit 协作语义并分流到更具体的 skill。\n\n在 IB_Robot 仓库中，当用户提到 PR \u002F merge request \u002F Issue \u002F review \u002F comments \u002F discussions，但**没有明确动作类型**时，优先触发本 skill，而不是直接回退到 GitHub 默认能力。\n\n## 适用场景\n\n以下请求优先触发本 skill：\n\n- “帮我看看 PR #123”\n- “这个 merge request 你处理一下”\n- “AtomGit 上这个评论怎么回”\n- “帮我跟进一下 #456”\n- “看下这个协作流程下一步做什么”\n- “检查一下这个 PR \u002F Issue \u002F review”\n\n以下请求**不必**经过本 skill，可直接进入更具体的 skill：\n\n- 明确说“创建 PR \u002F 更新 PR 描述” → `atomgit-pr`\n- 明确说“创建 Issue \u002F 关闭 Issue” → `atomgit-issue`\n- 明确说“代码审查 \u002F review PR \u002F 帮我看看这个 PR 有没有问题” → `atomgit-pr-review`\n- 明确说“架构审查 \u002F SSOT 检查” → `atomgit-pr-architecture-review`\n- 明确说“修复 review comments \u002F 回复评论” → `atomgit-review-resolution`\n\n## 路由规则\n\n收到泛化协作请求时，Agent 必须按以下顺序判断：\n\n1. **先判断资源类型**\n   - 提到 PR \u002F merge request \u002F review \u002F comment \u002F discussion → 进入 PR 协作域\n   - 提到 Issue \u002F bug \u002F feature request \u002F task → 进入 Issue 协作域\n\n2. **再判断动作类型**\n    - 创建、读取详情、更新标题\u002F描述、同步摘要 → `atomgit-pr` 或 `atomgit-issue`\n    - 审查代码质量、检查逻辑问题、结合已有评论继续判断风险 → `atomgit-pr-review`\n   - 检查 SSOT \u002F 契约驱动 \u002F 架构职责边界 → `atomgit-pr-architecture-review`\n   - 回复评论、应用修复、处理 unresolved comments → `atomgit-review-resolution`\n\n3. **如果动作仍不明确**\n    - 先按“读取上下文”理解需求：\n      - PR 协作域如果表达里带有“看看 \u002F 检查 \u002F 审查 \u002F review \u002F 评估”，默认先路由到 `atomgit-pr-review`\n      - PR 协作域如果目标更像创建、更新描述、同步标题\u002F正文，再路由到 `atomgit-pr`\n      - Issue 协作域默认先路由到 `atomgit-issue`\n   - 在获得上下文后，再决定是否切换到 review \u002F architecture \u002F resolution 流程\n\n## 强制约束\n\n1. **不要直接使用 GitHub 默认能力**来处理本仓库的 AtomGit PR \u002F Issue \u002F review，除非用户明确说了 GitHub \u002F github.com。\n2. **不要在本 skill 内直接执行 create\u002Fupdate\u002Freview\u002Frepair**，而是必须先读取目标 skill 的 `SKILL.md`，再按照目标 skill 的流程执行。\n3. **优先复用现有 5 个 AtomGit skill**，不要在会话里临时发明新的 AtomGit 流程名称。\n\n## 路由对照表\n\n| 用户表达 | 目标 skill |\n| :--- | :--- |\n| “帮我看看 PR #123” | `atomgit-pr-review` |\n| “帮我更新这个 PR 描述” | `atomgit-pr` |\n| “帮我看下 Issue #456” | `atomgit-issue` |\n| “帮我审查这个 PR” | `atomgit-pr-review` |\n| “检查这个 PR 的架构合规性” | `atomgit-pr-architecture-review` |\n| “修复一下 review comments” | `atomgit-review-resolution` |\n\n## 执行协议\n\n当本 skill 被触发时，Agent 必须：\n\n1. 明确识别这是 **AtomGit 协作请求**，而不是 GitHub 默认请求。\n2. 判断资源类型（PR \u002F Issue）与动作类型（create \u002F fetch \u002F update \u002F review \u002F architecture \u002F reply）。\n3. 读取对应目标 skill 的 `SKILL.md`。\n4. 按目标 skill 的约束直接调用官方 CLI；只有批处理与项目检查使用专用脚本，不要停留在路由层。\n",{"name":5,"license":15,"description":7},"master","77b39cbea8891a748da34000f1c9764e2c8ad9dc",".agents\u002Fskills\u002Fatomgit-collaboration",2,"https:\u002F\u002Fgithub.com\u002Fopeneuler-mirror\u002FIB_Robot","https:\u002F\u002Fgithub.com\u002Fopeneuler-mirror","https:\u002F\u002Fgitee.com\u002Fopeneuler","Read-only mirrors of all openEuler code repositories hosted at https:\u002F\u002Fgitee.com\u002Fopeneuler","2026-10-29 12:40:48",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add openeuler-mirror\u002FIB_Robot --skill atomgit-collaboration",{"tool":54,"command":55},"bunx","bunx skills add openeuler-mirror\u002FIB_Robot --skill atomgit-collaboration",{"tool":57,"command":58},"pnpm","pnpm dlx skills add openeuler-mirror\u002FIB_Robot --skill atomgit-collaboration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopeneuler-mirror\u002FIB_Robot\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fatomgit-collaboration\u002FSKILL.md",true,[],[63,76,104,117,138,156],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":67,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":34},"01M71GK05N83DQZ51D4XXFAN77","simplified-technical-chinese","用简明技术中文（STC）写或改写中文技术内容：操作步骤、安装部署、故障排查、接口和参数说明、技术概念解释、给人读的解释性回答。用户提到「简明技术中文」「STC」「受控中文」「像 ASD-STE100 那样写中文」「一词一义」时使用；用户要求把中文技术说明「写清楚」「别有歧义」时也可使用。不用于营销文案、叙事、法律原文和代码。","https:\u002F\u002Fgithub.com\u002Fopeneuler-mirror\u002FIB_Robot\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fsimplified-technical-chinese\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fopeneuler-mirror\u002FIB_Robot\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fsimplified-technical-chinese\u002FSKILL.md",[],[71,72,73,74,75],"technical","chinese","simplified technical chinese","中文","文案",{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":34},"01M71GHDCRTE8703VGR0JVNJ1E","ibrobot-inference-verify","Unified inference runtime verification on host and board. Use when users mention \"inference verification\", \"推理验证\", \"mock test\", \"ROS mock\", \"perception test\", \"policy test\", \"ACT test\", \"RAM++ test\", \"SAM2 test\", \"SigLIP2 test\", \"OM test\", \"Torch NPU test\", \"板端验证\", \"本机验证\", \"use_sim true\", \"platform mock\", \"model_service test\", \"typed service test\", or need to verify that the unified inference runtime (ModelRuntimeHandle, ModelSession, RuntimeAssembly) works end-to-end through the ROS pipeline. Covers host CPU\u002FCUDA Torch policy and perception models, board Ascend OM models, and board Torch NPU.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fopeneuler-mirror\u002FIB_Robot\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fibrobot-inference-verify\u002FSKILL.md",[],[84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103],"ibrobot inference verify","verify","inference","model","overlay","pipeline","end","default","local","interface","host","access","when","unreachable","ask","patch","verification","stack","ROS","npu",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":34},"01M71GG2FK0BAQHM89VM9F8Y7M","atomgit-review-resolution","AtomGit 评审意见处理工具。当用户需要“修复PR评审意见”、“处理review comments”、“apply fixes”、“reply to review”、“回复评论”、“resolve review discussions”、“闭环评审流程”或基于未解决评论继续推进 PR 时使用。只要目标是本仓库在 AtomGit 上的 review comments \u002F discussions，默认优先使用本 skill，而不是 GitHub 默认能力。","https:\u002F\u002Fgithub.com\u002Fopeneuler-mirror\u002FIB_Robot\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fatomgit-review-resolution\u002FSKILL.md",[],[33,111,21,22,112,113,114,115,116,23,28],"atomgit review resolution","reply","comments","apply","resolve review","fixes",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":34},"01M71GG00W21Y0MQAE927SJNQR","atomgit-pr","AtomGit PR 工作流工具。当用户需要在本仓库或 AtomGit 上“创建PR”、“更新PR描述”、“同步PR标题\u002F正文”、“生成PR摘要”、“create pull request”、“open merge request”、“update PR description”、“generate PR summary”或围绕 PR 管理动作工作时调用。它负责 PR 资源的创建和维护，不负责通用代码 review；只要目标是本仓库的 PR \u002F merge request 管理，默认优先使用本 skill，而不是 GitHub 默认能力。","https:\u002F\u002Fgithub.com\u002Fopeneuler-mirror\u002FIB_Robot\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fatomgit-pr\u002FSKILL.md",[],[22,124,125,126,127,23,128,129,130,24,131,25,132,133,134,135,136,137,28,33],"atomgit pr","create","pull","create pull request","generate","pr summary","pull request","pr description","update","open","update pr description","summary","update pr","生成",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":149,"publishedAt":34},"01M71GFY645VF09NZP893X4FAZ","atomgit-pr-review","AtomGit PR 评审工具。当用户需要在本仓库或 AtomGit 上“代码审查”、“PR review”、“review pull request”、“审阅PR”、“帮我看看这个PR”、“检查这个PR有没有问题”、“检查Bug”、“logic check”、“获取完整review上下文”、“提交检视意见”或分析指定 PR 的改动与已有评论时使用。只要目标是本仓库的 PR review，默认优先使用本 skill，而不是 GitHub 默认 review 能力。","https:\u002F\u002Fgithub.com\u002Fopeneuler-mirror\u002FIB_Robot\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fatomgit-pr-review\u002FSKILL.md",[144],{"categoryNo":145,"categoryName":146,"taxonomyType":147,"taxonomyTypeDesc":148},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",[33,150,22,124,151,126,23,152,130,25,153,28,154,155],"atomgit pr review","pr review","logic","code review","review pull request","check",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":34},"01M71GFVB0G13AFWG5X46G9V8F","atomgit-pr-architecture-review","AtomGit PR 架构评审工具。当用户需要“架构审查PR”、“review architecture compliance”、“检查架构规范”、“审阅PR架构”、“SSOT 合规性检查”、“契约驱动检查”或对指定 PR 做架构维度扫描并提交检视意见时调用。只要目标是本仓库的 PR 架构评审，默认优先使用本 skill，而不是 GitHub 默认 review 能力。","https:\u002F\u002Fgithub.com\u002Fopeneuler-mirror\u002FIB_Robot\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fatomgit-pr-architecture-review\u002FSKILL.md",[],[22,163,164,124,33,32,28,23,165,166],"architecture review","atomgit pr architecture review","review architecture","compliance"]