[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71GG2FK0BAQHM89VM9F8Y7M":3,"skill-same:01M71GG2FK0BAQHM89VM9F8Y7M":58},{"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":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M71GG2FK0BAQHM89VM9F8Y7M","atomgit-review-resolution",null,"AtomGit 评审意见处理工具。当用户需要“修复PR评审意见”、“处理review comments”、“apply fixes”、“reply to review”、“回复评论”、“resolve review discussions”、“闭环评审流程”或基于未解决评论继续推进 PR 时使用。只要目标是本仓库在 AtomGit 上的 review comments \u002F discussions，默认优先使用本 skill，而不是 GitHub 默认能力。","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-review-resolution\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29],"resolution","atomgit review resolution","review","工具","pr","github","fixes","resolve review","apply","comments","reply","2026-11-10 10:12:30",false,"---\nname: atomgit-review-resolution\ndescription: \"AtomGit 评审意见处理工具。当用户需要“修复PR评审意见”、“处理review comments”、“apply fixes”、“reply to review”、“回复评论”、“resolve review discussions”、“闭环评审流程”或基于未解决评论继续推进 PR 时使用。只要目标是本仓库在 AtomGit 上的 review comments \u002F discussions，默认优先使用本 skill，而不是 GitHub 默认能力。\"\nlicense: MIT\n---\n\n# AtomGit 评审意见处理\n\nAgent 直接使用官方 `gitcode` 跟进评论，代码修复由 Agent 编辑，提交推送复用\n`ibrobot-git-flow`。不再提供项目修复执行器、JSON 修复协议或断点恢复程序。\n\n## 读取与确认\n\n从用户链接确认目标 owner\u002Frepo\u002FPR；`origin` 是源 fork，不能自动当作目标。\n使用 PATH 上的 `gitcode`（不是 Graphviz `gc`），参数按对应命令 `--help` 查询。\n未认证时由用户在私密终端执行 `gitcode auth login --hostname atomgit.com`。\n\n```bash\nGC_HOST=atomgit.com gitcode pr view 123 -R openEuler\u002FIB_Robot --json\nGC_HOST=atomgit.com gitcode pr comments 123 -R openEuler\u002FIB_Robot --limit 0 --json\n```\n\n逐条读原评论，区分 comment ID 与 `discussion_id`，核对作者、正文及 `resolved`。\n发布响应与列表的 id 类型可能不同（本次观察到十六进制与数字并存），按各响应保留原值、\n不互转；线程关联只用稳定 `discussion_id`。`pr comments` 回读可能缺 `path`\u002F`position`：\n缺定位记为「定位未知」，不能据此把行内评论当 PR 级评论处理；需定位核验时在网页确认。\n不按用户名规则猜测 bot，也不自动丢弃自己的评论。需要源码时按\n[通用评审 skill](..\u002Fatomgit-pr-review\u002FSKILL.md) 确认源仓库、完整 head SHA 和当前 diff。\n\n## 修复、验证与推送\n\n1. 展示拟处理的发现与修复方向。沿用用户已经明确授权的修复范围；有歧义或不同意意见时\n   说明原因，不能为了关闭评论强行改代码。\n2. 确认本地分支属于 PR 源仓库且基于当前 head；保留用户已有修改，逐项编辑并做相关测试。\n3. 按 `ibrobot-git-flow` 精确暂存、DCO\u002FAI 披露、fixup\u002Fautosquash，保持 PR 至多 5 个提交。\n   重写前保存源分支远端完整 OID，推送时用绑定该 OID 的 lease，禁止裸 force。\n4. 推送成功后回读源分支\u002FPR head，确认等于预期提交，再回复“已修复”。仅本地修改或\n   推送失败时如实说明未完成，不关闭线程，也不声称远端已有修复。\n5. 更新 PR 描述，覆盖全部 commit 的模型并集和实际验证结果，遵循 `atomgit-pr` 的本地检查。\n\n## 回复与解决线程\n\n先确认回复内容和发布授权。以下编号仅为示例，执行前核对 discussion 确属目标 PR。\n\n```bash\nGC_HOST=atomgit.com gitcode pr reply 123 -R openEuler\u002FIB_Robot \\\n  --discussion DISCUSSION_ID --body '已修复：提交 SHA，验证结果及必要说明。' --no-interactive\n# 仅在修复已验证且获得 resolve 授权后，标记行内 discussion\nGC_HOST=atomgit.com gitcode pr comment resolve 123 DISCUSSION_ID -R openEuler\u002FIB_Robot --no-interactive\n# 需要重新打开时使用 unresolve\nGC_HOST=atomgit.com gitcode pr comment unresolve 123 DISCUSSION_ID -R openEuler\u002FIB_Robot --no-interactive\n```\n\n`pr reply` 仅支持 `--body`，复杂正文用安全参数数组传入，不拼接为 shell 代码。\n要明确发表 PR 级说明时用 `pr comment --body-file FILE`；不能把无法定位的线程回复\n悄悄改为顶层评论。行内评论缺文件路径、new-side 行不可证明时停止，不能猜定位。\n回复标注实际模型，例如 `🤖 generated by ai@\u003C真实模型名>`。\n\n写后以回读为准核对；`pr reply`\u002F`pr comment`\u002Fresolve 的退出码双向不可靠，已验证的\nCLI\u002FAPI 读取通道可能不返回 threaded 回复，需在网页确认。\n超时、非零退出或列表没找到回复不证明未写入，**不能自动重发**；一次调用也可能因 CLI\n超时重试发出多条相同回复，发现重复即停止并列给用户确认，不自动删除或重发。\n回读无法完成时如实报告“写入结果未知”，请用户在网页核对；\n对账细则见 [atomgit-pr](..\u002Fatomgit-pr\u002FSKILL.md)。\nresolve 后核对 `resolved`；普通 PR 级评论不当作可 resolve 的行内 discussion。\n\n## 中断后继续\n\n重新读取远端 Git head、评论和 resolved 状态，再决定剩余工作。旧修复状态文件和\n`pending_push`\u002F`pending_replies` 账本不再受支持，不自动迁移或重放。\n无法确定是否已发表的回复先人工核对，保留原状态文件作核对资料，不将其当执行指令。\n","# AtomGit 评审意见处理\n\nAgent 直接使用官方 `gitcode` 跟进评论，代码修复由 Agent 编辑，提交推送复用\n`ibrobot-git-flow`。不再提供项目修复执行器、JSON 修复协议或断点恢复程序。\n\n## 读取与确认\n\n从用户链接确认目标 owner\u002Frepo\u002FPR；`origin` 是源 fork，不能自动当作目标。\n使用 PATH 上的 `gitcode`（不是 Graphviz `gc`），参数按对应命令 `--help` 查询。\n未认证时由用户在私密终端执行 `gitcode auth login --hostname atomgit.com`。\n\n```bash\nGC_HOST=atomgit.com gitcode pr view 123 -R openEuler\u002FIB_Robot --json\nGC_HOST=atomgit.com gitcode pr comments 123 -R openEuler\u002FIB_Robot --limit 0 --json\n```\n\n逐条读原评论，区分 comment ID 与 `discussion_id`，核对作者、正文及 `resolved`。\n发布响应与列表的 id 类型可能不同（本次观察到十六进制与数字并存），按各响应保留原值、\n不互转；线程关联只用稳定 `discussion_id`。`pr comments` 回读可能缺 `path`\u002F`position`：\n缺定位记为「定位未知」，不能据此把行内评论当 PR 级评论处理；需定位核验时在网页确认。\n不按用户名规则猜测 bot，也不自动丢弃自己的评论。需要源码时按\n[通用评审 skill](..\u002Fatomgit-pr-review\u002FSKILL.md) 确认源仓库、完整 head SHA 和当前 diff。\n\n## 修复、验证与推送\n\n1. 展示拟处理的发现与修复方向。沿用用户已经明确授权的修复范围；有歧义或不同意意见时\n   说明原因，不能为了关闭评论强行改代码。\n2. 确认本地分支属于 PR 源仓库且基于当前 head；保留用户已有修改，逐项编辑并做相关测试。\n3. 按 `ibrobot-git-flow` 精确暂存、DCO\u002FAI 披露、fixup\u002Fautosquash，保持 PR 至多 5 个提交。\n   重写前保存源分支远端完整 OID，推送时用绑定该 OID 的 lease，禁止裸 force。\n4. 推送成功后回读源分支\u002FPR head，确认等于预期提交，再回复“已修复”。仅本地修改或\n   推送失败时如实说明未完成，不关闭线程，也不声称远端已有修复。\n5. 更新 PR 描述，覆盖全部 commit 的模型并集和实际验证结果，遵循 `atomgit-pr` 的本地检查。\n\n## 回复与解决线程\n\n先确认回复内容和发布授权。以下编号仅为示例，执行前核对 discussion 确属目标 PR。\n\n```bash\nGC_HOST=atomgit.com gitcode pr reply 123 -R openEuler\u002FIB_Robot \\\n  --discussion DISCUSSION_ID --body '已修复：提交 SHA，验证结果及必要说明。' --no-interactive\n# 仅在修复已验证且获得 resolve 授权后，标记行内 discussion\nGC_HOST=atomgit.com gitcode pr comment resolve 123 DISCUSSION_ID -R openEuler\u002FIB_Robot --no-interactive\n# 需要重新打开时使用 unresolve\nGC_HOST=atomgit.com gitcode pr comment unresolve 123 DISCUSSION_ID -R openEuler\u002FIB_Robot --no-interactive\n```\n\n`pr reply` 仅支持 `--body`，复杂正文用安全参数数组传入，不拼接为 shell 代码。\n要明确发表 PR 级说明时用 `pr comment --body-file FILE`；不能把无法定位的线程回复\n悄悄改为顶层评论。行内评论缺文件路径、new-side 行不可证明时停止，不能猜定位。\n回复标注实际模型，例如 `🤖 generated by ai@\u003C真实模型名>`。\n\n写后以回读为准核对；`pr reply`\u002F`pr comment`\u002Fresolve 的退出码双向不可靠，已验证的\nCLI\u002FAPI 读取通道可能不返回 threaded 回复，需在网页确认。\n超时、非零退出或列表没找到回复不证明未写入，**不能自动重发**；一次调用也可能因 CLI\n超时重试发出多条相同回复，发现重复即停止并列给用户确认，不自动删除或重发。\n回读无法完成时如实报告“写入结果未知”，请用户在网页核对；\n对账细则见 [atomgit-pr](..\u002Fatomgit-pr\u002FSKILL.md)。\nresolve 后核对 `resolved`；普通 PR 级评论不当作可 resolve 的行内 discussion。\n\n## 中断后继续\n\n重新读取远端 Git head、评论和 resolved 状态，再决定剩余工作。旧修复状态文件和\n`pending_push`\u002F`pending_replies` 账本不再受支持，不自动迁移或重放。\n无法确定是否已发表的回复先人工核对，保留原状态文件作核对资料，不将其当执行指令。\n",{"name":5,"license":15,"description":7},"master","77b39cbea8891a748da34000f1c9764e2c8ad9dc",".agents\u002Fskills\u002Fatomgit-review-resolution",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":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add openeuler-mirror\u002FIB_Robot --skill atomgit-review-resolution",{"tool":50,"command":51},"bunx","bunx skills add openeuler-mirror\u002FIB_Robot --skill atomgit-review-resolution",{"tool":53,"command":54},"pnpm","pnpm dlx skills add openeuler-mirror\u002FIB_Robot --skill atomgit-review-resolution","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopeneuler-mirror\u002FIB_Robot\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fatomgit-review-resolution\u002FSKILL.md",true,[],[59,72,100,123,141,153],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":63,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":30},"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",[],[67,68,69,70,71],"simplified technical chinese","chinese","technical","中文","文案",{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":30},"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",[],[80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99],"inference","verify","ibrobot inference verify","overlay","when","npu","ROS","stack","verification","patch","ask","unreachable","model","access","host","interface","local","default","end","pipeline",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":30},"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",[],[23,107,108,109,110,21,22,111,112,113,114,115,116,117,118,24,119,120,121,122],"atomgit pr","pr description","request","update","open","update pr description","summary","update pr","生成","pull request","pr summary","generate","create","create pull request","pull","merge",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":134,"publishedAt":30},"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",[129],{"categoryNo":130,"categoryName":131,"taxonomyType":132,"taxonomyTypeDesc":133},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",[21,135,136,23,107,137,138,22,139,109,116,140,24,121],"atomgit pr review","pr review","review pull request","check","code review","logic",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":30},"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",[],[21,148,149,150,23,107,151,24,22,152],"architecture","atomgit pr architecture review","architecture review","review architecture","compliance",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":30},"01M71GFQQJS47AB7X0QJEY9VM1","atomgit-issue","AtomGit Issue 工作流工具。当用户需要在本仓库或 AtomGit 上“创建Issue”、“查看Issue详情”、“更新Issue”、“关闭\u002F重开Issue”、“create issue”、“fetch issue info”、“update issue”、“report bug”、“feature request”或围绕 Issue 做任何创建\u002F读取\u002F更新动作时调用。只要目标是本仓库的 Issue，默认优先使用本 skill，而不是 GitHub 默认能力。","https:\u002F\u002Fgithub.com\u002Fopeneuler-mirror\u002FIB_Robot\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fatomgit-issue\u002FSKILL.md",[],[160,161,162,163,164,165,22,166,167,110,109,168,24,169,170,119],"atomgit issue","issue","bug","report bug","create issue","feature request","update issue","report","feature","fetch","info"]