[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71GFY645VF09NZP893X4FAZ":3,"skill-same:01M71GFY645VF09NZP893X4FAZ":86},{"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":23,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M71GFY645VF09NZP893X4FAZ","atomgit-pr-review",null,"AtomGit PR 评审工具。当用户需要在本仓库或 AtomGit 上“代码审查”、“PR review”、“review pull request”、“审阅PR”、“帮我看看这个PR”、“检查这个PR有没有问题”、“检查Bug”、“logic check”、“获取完整review上下文”、“提交检视意见”或分析指定 PR 的改动与已有评论时使用。只要目标是本仓库的 PR review，默认优先使用本 skill，而不是 GitHub 默认 review 能力。","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-pr-review\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37],"atomgit pr","pr","pr review","atomgit pr review","review","pull","github","logic","pull request","request","code review","工具","review pull request","check","2026-11-10 10:12:30",false,"---\nname: atomgit-pr-review\ndescription: \"AtomGit PR 评审工具。当用户需要在本仓库或 AtomGit 上“代码审查”、“PR review”、“review pull request”、“审阅PR”、“帮我看看这个PR”、“检查这个PR有没有问题”、“检查Bug”、“logic check”、“获取完整review上下文”、“提交检视意见”或分析指定 PR 的改动与已有评论时使用。只要目标是本仓库的 PR review，默认优先使用本 skill，而不是 GitHub 默认 review 能力。\"\nlicense: MIT\n---\n\n# AtomGit PR 评审\n\nAgent 直接使用官方 `gitcode` 获取上下文和发布评论，参数按需查 `--help`。\n本仓库 PR 默认指 AtomGit；先确认目标 owner\u002Frepo\u002F编号，每次指定 `GC_HOST=atomgit.com`\n和 `-R owner\u002Frepo`，不能把个人 fork 的 `origin` 当作目标。认证由 CLI 管理。\n\n## 三步法（默认必做）\n\n1. **问题与目标**：只读标题、正文、关联 Issue 和 commit message，说明问题、预期行为及成功标准。\n2. **独立方案**：在读 PR 实现前给出自己的最小方案；必要时只读目标分支基线的文档\u002F接口。\n3. **实现对比**：先做专项检查，再读 patch、源代码、测试和既有评论，对照方案判断正确性。\n\n前两步的简短产出必须展示给用户，再进入第三步，无需额外确认。前两步不读 patch、\n变更后源码或 review 评论，也不委派读取实现。抓取数据到文件不等于允许提前阅读。\n小 PR、快速审查和“无问题”结论也遵循此顺序。上下文已经暴露实现时说明独立性受限，\n仍先写目标与候选方案，不声称未读过实现。中断后沿用已展示的产出。\n\n## 读取与审计\n\n以下以 PR 123 为例，执行前替换为确认的目标，先创建 `tmp\u002F`。\n\n```bash\nGC_HOST=atomgit.com gitcode pr view 123 -R openEuler\u002FIB_Robot --json > tmp\u002Fpr.json\n# 第一步只读元数据，不打开整个带实现信息的文件\njq '{number,title,body,head: (.head | {sha,ref,repo})}' tmp\u002Fpr.json\nGC_HOST=atomgit.com gitcode api 'repos\u002FopenEuler\u002FIB_Robot\u002Fpulls\u002F123\u002Fcommits?page=1&per_page=100' > tmp\u002Fcommits-page1.json\n# 第三步再读取文件 diff 和已有评论\nGC_HOST=atomgit.com gitcode api 'repos\u002FopenEuler\u002FIB_Robot\u002Fpulls\u002F123\u002Ffiles?page=1&per_page=100' > tmp\u002Ffiles-page1.json\nGC_HOST=atomgit.com gitcode pr comments 123 -R openEuler\u002FIB_Robot --limit 0 --json > tmp\u002Fcomments.json\n```\n\n`api` 原生输出 JSON，**没有 `--json` 或 `--paginate` 参数**。逐页读取并将完整集合保存为\n`tmp\u002Ffiles.json` \u002F `tmp\u002Fcommits.json`，按唯一 filename\u002Fsha 核对 `pr.json` 的\n`changed_files` \u002F `commits` 总数。重复页不证明完整，失败\u002F缺字段不能当空数据。\n`pr diff --json` 是统计摘要；完整 patch 使用 files 中的 `patch.diff`。\n\n记录目标仓库\u002FPR、head 的源仓库身份与完整 SHA。源码读取必须来自该源仓库及 SHA，\n不能从目标仓库 HEAD 猜测；相关文件上下文无法完整读取时，标明未评审范围，不发布通过结论。\n\n第三步用本地审计入口处理项目检查，然后继续代码分析：\n\n```bash\nsource .shrc_local && python3 .agents\u002Fskills\u002Fatomgit-pr-review\u002Fscripts\u002Freview_gates.py \\\n  --pr-json tmp\u002Fpr.json --files-json tmp\u002Ffiles.json --commits-json tmp\u002Fcommits.json \\\n  --output tmp\u002Freview-checks.json\n```\n\n退出 0 表示审计执行完，不表示通过：`checks` 中的阻塞项必须处理或列为发现。\nDocker 指纹来自作者\u002F评审共用的本地确定性 diff（非 WIP 时 base、head 均需先 fetch 到\n本地；固定 flag 集禁用 rename 配对）；`pr.json` 的 base\u002Fhead SHA 任一不可本地解析时给出\n`docker_verification_inputs_unavailable` 阻塞项，不得用平台 files 顶替或拿任意本地 HEAD\n充当 PR head。平台 files 的 rename 配对与本地 git 可能不同（PR460 实测平台 61、本地默认\n62、`--no-renames` 65）；计数差异不能只引用该现象放行——逐路径比对并以 base\u002Fhead 树核对\n确认差异确为 rename 配对，核对后仍无法解释的差异按清单不完整处理。\n\n专项检查：LeRobot gitlink\u002Fpatch 管理、README 联动、非 WIP 的 Docker 证据、DCO\u002FAI 披露、\n大型 PR 的复用自查；具体判定见 [专项检查](references\u002Fibrobot-mandatory-checks.md)。\n只做 review 默认静态分析，不重复执行 lint\u002Fbuild\u002FDocker；用户明确要求验证时按对应 skill 执行。\n\n## 结论与发布\n\n先展示具体发现，包含严重性、文件\u002F行号、触发条件、影响和修复方向，附简短方案对比及\n验证\u002F未覆盖范围。没有发现也说明对比结果，不能仅写 LGTM。\n**发布必须有针对具体审查结果的人类确认**；单纯“review PR”不等于授权发表评论。\n\n发布前重新 `pr view`，核对目标、源仓库和完整 head SHA 与审查时一致；版本变化或身份\n不可证明时停止并重新评审。行内位置必须在当前 diff 的 new 侧可见，删除行不猜定位。\n跨文件问题可明确发 PR 级评论；无法定位的行内问题不能静默降级。\n\n```bash\nGC_HOST=atomgit.com gitcode pr comment 123 -R openEuler\u002FIB_Robot --body-file tmp\u002Freview.md --json --no-interactive\nGC_HOST=atomgit.com gitcode pr comment 123 -R openEuler\u002FIB_Robot --path src\u002Fexample.py \\\n  --position 42 --body-file tmp\u002Ffinding.md --json --no-interactive\n```\n\n评论末尾标注 `🤖 generated by ai@\u003C真实模型名>`，格式见\n[读取与评论说明](references\u002Fapi-and-issues-format.md)。发布后回读核对；注意回读不返回\n`path`\u002F`position`——缺定位只能记为「定位未知」，不能据此断言 PR 级，需定位核验时在网页\n确认。发布响应与列表的 id 类型可能不同（本次观察到十六进制与数字并存），按各响应保留\n原值、不互转，线程关联用 `discussion_id`；超时\u002F非零退出可能已发表，不自动重发。修复和线程跟进走 `atomgit-review-resolution`；\nSSOT\u002F包职责专题使用 `atomgit-pr-architecture-review`。\n","# AtomGit PR 评审\n\nAgent 直接使用官方 `gitcode` 获取上下文和发布评论，参数按需查 `--help`。\n本仓库 PR 默认指 AtomGit；先确认目标 owner\u002Frepo\u002F编号，每次指定 `GC_HOST=atomgit.com`\n和 `-R owner\u002Frepo`，不能把个人 fork 的 `origin` 当作目标。认证由 CLI 管理。\n\n## 三步法（默认必做）\n\n1. **问题与目标**：只读标题、正文、关联 Issue 和 commit message，说明问题、预期行为及成功标准。\n2. **独立方案**：在读 PR 实现前给出自己的最小方案；必要时只读目标分支基线的文档\u002F接口。\n3. **实现对比**：先做专项检查，再读 patch、源代码、测试和既有评论，对照方案判断正确性。\n\n前两步的简短产出必须展示给用户，再进入第三步，无需额外确认。前两步不读 patch、\n变更后源码或 review 评论，也不委派读取实现。抓取数据到文件不等于允许提前阅读。\n小 PR、快速审查和“无问题”结论也遵循此顺序。上下文已经暴露实现时说明独立性受限，\n仍先写目标与候选方案，不声称未读过实现。中断后沿用已展示的产出。\n\n## 读取与审计\n\n以下以 PR 123 为例，执行前替换为确认的目标，先创建 `tmp\u002F`。\n\n```bash\nGC_HOST=atomgit.com gitcode pr view 123 -R openEuler\u002FIB_Robot --json > tmp\u002Fpr.json\n# 第一步只读元数据，不打开整个带实现信息的文件\njq '{number,title,body,head: (.head | {sha,ref,repo})}' tmp\u002Fpr.json\nGC_HOST=atomgit.com gitcode api 'repos\u002FopenEuler\u002FIB_Robot\u002Fpulls\u002F123\u002Fcommits?page=1&per_page=100' > tmp\u002Fcommits-page1.json\n# 第三步再读取文件 diff 和已有评论\nGC_HOST=atomgit.com gitcode api 'repos\u002FopenEuler\u002FIB_Robot\u002Fpulls\u002F123\u002Ffiles?page=1&per_page=100' > tmp\u002Ffiles-page1.json\nGC_HOST=atomgit.com gitcode pr comments 123 -R openEuler\u002FIB_Robot --limit 0 --json > tmp\u002Fcomments.json\n```\n\n`api` 原生输出 JSON，**没有 `--json` 或 `--paginate` 参数**。逐页读取并将完整集合保存为\n`tmp\u002Ffiles.json` \u002F `tmp\u002Fcommits.json`，按唯一 filename\u002Fsha 核对 `pr.json` 的\n`changed_files` \u002F `commits` 总数。重复页不证明完整，失败\u002F缺字段不能当空数据。\n`pr diff --json` 是统计摘要；完整 patch 使用 files 中的 `patch.diff`。\n\n记录目标仓库\u002FPR、head 的源仓库身份与完整 SHA。源码读取必须来自该源仓库及 SHA，\n不能从目标仓库 HEAD 猜测；相关文件上下文无法完整读取时，标明未评审范围，不发布通过结论。\n\n第三步用本地审计入口处理项目检查，然后继续代码分析：\n\n```bash\nsource .shrc_local && python3 .agents\u002Fskills\u002Fatomgit-pr-review\u002Fscripts\u002Freview_gates.py \\\n  --pr-json tmp\u002Fpr.json --files-json tmp\u002Ffiles.json --commits-json tmp\u002Fcommits.json \\\n  --output tmp\u002Freview-checks.json\n```\n\n退出 0 表示审计执行完，不表示通过：`checks` 中的阻塞项必须处理或列为发现。\nDocker 指纹来自作者\u002F评审共用的本地确定性 diff（非 WIP 时 base、head 均需先 fetch 到\n本地；固定 flag 集禁用 rename 配对）；`pr.json` 的 base\u002Fhead SHA 任一不可本地解析时给出\n`docker_verification_inputs_unavailable` 阻塞项，不得用平台 files 顶替或拿任意本地 HEAD\n充当 PR head。平台 files 的 rename 配对与本地 git 可能不同（PR460 实测平台 61、本地默认\n62、`--no-renames` 65）；计数差异不能只引用该现象放行——逐路径比对并以 base\u002Fhead 树核对\n确认差异确为 rename 配对，核对后仍无法解释的差异按清单不完整处理。\n\n专项检查：LeRobot gitlink\u002Fpatch 管理、README 联动、非 WIP 的 Docker 证据、DCO\u002FAI 披露、\n大型 PR 的复用自查；具体判定见 [专项检查](references\u002Fibrobot-mandatory-checks.md)。\n只做 review 默认静态分析，不重复执行 lint\u002Fbuild\u002FDocker；用户明确要求验证时按对应 skill 执行。\n\n## 结论与发布\n\n先展示具体发现，包含严重性、文件\u002F行号、触发条件、影响和修复方向，附简短方案对比及\n验证\u002F未覆盖范围。没有发现也说明对比结果，不能仅写 LGTM。\n**发布必须有针对具体审查结果的人类确认**；单纯“review PR”不等于授权发表评论。\n\n发布前重新 `pr view`，核对目标、源仓库和完整 head SHA 与审查时一致；版本变化或身份\n不可证明时停止并重新评审。行内位置必须在当前 diff 的 new 侧可见，删除行不猜定位。\n跨文件问题可明确发 PR 级评论；无法定位的行内问题不能静默降级。\n\n```bash\nGC_HOST=atomgit.com gitcode pr comment 123 -R openEuler\u002FIB_Robot --body-file tmp\u002Freview.md --json --no-interactive\nGC_HOST=atomgit.com gitcode pr comment 123 -R openEuler\u002FIB_Robot --path src\u002Fexample.py \\\n  --position 42 --body-file tmp\u002Ffinding.md --json --no-interactive\n```\n\n评论末尾标注 `🤖 generated by ai@\u003C真实模型名>`，格式见\n[读取与评论说明](references\u002Fapi-and-issues-format.md)。发布后回读核对；注意回读不返回\n`path`\u002F`position`——缺定位只能记为「定位未知」，不能据此断言 PR 级，需定位核验时在网页\n确认。发布响应与列表的 id 类型可能不同（本次观察到十六进制与数字并存），按各响应保留\n原值、不互转，线程关联用 `discussion_id`；超时\u002F非零退出可能已发表，不自动重发。修复和线程跟进走 `atomgit-review-resolution`；\nSSOT\u002F包职责专题使用 `atomgit-pr-architecture-review`。\n",{"name":5,"license":15,"description":7},"master","77b39cbea8891a748da34000f1c9764e2c8ad9dc",".agents\u002Fskills\u002Fatomgit-pr-review",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":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add openeuler-mirror\u002FIB_Robot --skill atomgit-pr-review",{"tool":58,"command":59},"bunx","bunx skills add openeuler-mirror\u002FIB_Robot --skill atomgit-pr-review",{"tool":61,"command":62},"pnpm","pnpm dlx skills add openeuler-mirror\u002FIB_Robot --skill atomgit-pr-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopeneuler-mirror\u002FIB_Robot\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fatomgit-pr-review\u002FSKILL.md",true,[66,72,76,82],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fapi-and-issues-format.md","REFERENCE","参考文档",4115,"https:\u002F\u002Fgithub.com\u002Fopeneuler-mirror\u002FIB_Robot\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fatomgit-pr-review\u002Freferences\u002Fapi-and-issues-format.md",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fibrobot-mandatory-checks.md",14737,"https:\u002F\u002Fgithub.com\u002Fopeneuler-mirror\u002FIB_Robot\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fatomgit-pr-review\u002Freferences\u002Fibrobot-mandatory-checks.md",{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"scripts\u002Freview_gates.py","SCRIPT","脚本",21331,"https:\u002F\u002Fgithub.com\u002Fopeneuler-mirror\u002FIB_Robot\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fatomgit-pr-review\u002Fscripts\u002Freview_gates.py",{"path":83,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":84,"sourceHtmlUrl":85},"tests\u002Ftest_review_gates.py",17234,"https:\u002F\u002Fgithub.com\u002Fopeneuler-mirror\u002FIB_Robot\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fatomgit-pr-review\u002Ftests\u002Ftest_review_gates.py",[87,100,128,142,161,173],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":38},"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",[],[95,96,97,98,99],"simplified technical chinese","chinese","technical","中文","文案",{"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":104,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":38},"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",[],[108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127],"ibrobot inference verify","verify","inference","model","overlay","access","pipeline","end","npu","ROS","default","local","interface","host","stack","verification","patch","ask","unreachable","when",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":38},"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",[],[135,136,28,35,25,30,137,138,139,140,141],"resolution","atomgit review resolution","fixes","resolve review","apply","comments","reply",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":38},"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",[],[25,24,149,35,150,151,152,153,154,155,33,28,156,32,157,158,30,159,160,29],"pr description","生成","update pr","summary","update pr description","open","update","merge","pr summary","generate","create","create pull request",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":38},"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",[],[28,168,169,170,25,24,171,30,35,172],"architecture","atomgit pr architecture review","architecture review","review architecture","compliance",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":179,"publishedAt":38},"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",[],[180,181,182,183,184,185,35,186,187,155,33,188,30,189,190,159],"atomgit issue","issue","bug","report bug","create issue","feature request","update issue","report","feature","fetch","info"]