[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M756D95GSVDT9601RYGJQMJR":3,"skill-same:01M756D95GSVDT9601RYGJQMJR":73},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M756D95GSVDT9601RYGJQMJR","e2e-business-flow-tracker",null,"全链路业务流程跟踪代理。模拟用户从注册登录→认证→任务发布→订单流转→管理端审查的完整业务流程，进行 1.0 发布前最终验证。确保所有代码可运行、无 MEDIUM 及以上 Bug、前端 UI 渲染正常。","Ikeu-1030\u002FiRun","Ikeu-1030","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F229719040?v=4","01M756CMM1YGXYJFY5C8ABR8Y1","ikeu","01M756CMMSQXPZW8JGYCRGYEK9",5,"MIT","https:\u002F\u002Fgithub.com\u002FIkeu-1030\u002FiRun\u002Fblob\u002Fmain\u002F.agent\u002Fe2e-business-flow-tracker\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"e2e-business-flow-tracker\"\ndescription: \"全链路业务流程跟踪代理。模拟用户从注册登录→认证→任务发布→订单流转→管理端审查的完整业务流程，进行 1.0 发布前最终验证。确保所有代码可运行、无 MEDIUM 及以上 Bug、前端 UI 渲染正常。\"\nmodel: sonnet\nmemory: user\n---\n\n# E2E Business Flow Tracker\n\n端到端业务流程全链路跟踪，模拟真实用户操作验证系统完整性和正确性。\n\n## When to use this skill\n\n**触发场景（必须触发）：**\n- 1.0 版本发布前最终验证\n- 重大重构或架构变更后\n- 数据库 schema 变更后\n- 安全机制（JWT\u002F限流\u002F权限）变更后\n- 状态机逻辑修改后\n- 支付\u002F退款流程变更后\n- 用户明确要求\"全链路测试\"、\"端到端验证\"、\"发布前检查\"\n\n**DO NOT use when:**\n- 仅修改文档或注释 → 无运行影响\n- 仅修改 CSS\u002F样式 → 前端代码审查即可\n- 单接口 Bug 修复 → 使用 `docker-test-agent` 针对性测试\n- 纯 UI 调整 → 使用 `frontend-code-reviewer`\n\n## How to use this skill\n\n```\n\u002Fagent:e2e-business-flow-tracker --scope \u003Cfull|phase1-7|quick> --env \u003Clocal|docker>\n```\n\n### 执行模式\n\n| 模式 | 覆盖范围 | 预估耗时 |\n|------|---------|---------|\n| `full` | 全部 7 个 Phase，26 个 Step | 15-20 min |\n| `quick` | Phase 1-2-5 核心路径（认证+任务+订单） | 5-8 min |\n| `phase\u003CN>` | 指定 Phase 1-7 | 2-5 min\u002Fphase |\n\n### 执行流程\n\n```\nPhase 0: Pre-flight Check（编译+环境就绪）\nPhase 1: 认证与注册（6 steps）\nPhase 2: 用户资料与认证（4 steps）\nPhase 3: 跑腿员认证（3 steps）\nPhase 4: 任务发布（5 steps）\nPhase 5: 订单全生命周期（8 steps）\nPhase 6: 管理端全功能（4 steps）\nPhase 7: 边界与异常（集成在各 Step 断言中）\nReport: 汇总通过\u002F失败\u002F阻塞清单\n```\n\n## Agent 工作流\n\n### Step 0: Pre-flight Check\n\n```bash\n# 1. 编译后端\ncd F:\u002Fikeu_runningerrands\u002Fbackend\n.\u002Frunningerrands-server\u002Fmvnw compile -q -DskipTests\n\n# 2. 前端类型检查\ncd F:\u002Fikeu_runningerrands\u002Fadmin\nnpx vue-tsc --noEmit\n\n# 3. 环境健康检查\ncurl -s http:\u002F\u002Flocalhost:8080\u002Fapi\u002Factuator\u002Fhealth\n# 或 Docker: docker compose ps\n```\n\n### Step 1: 环境准备\n\n1. 清理测试数据（删除上次运行产生的用户\u002F任务\u002F订单）\n2. 注入 SMS 验证码到 Redis\n3. 确认测试账号可用\n4. 获取 admin JWT（用于管理端操作）\n\n### Step 2: 按 Phase 顺序执行\n\n每个 Step 包含：\n1. **API 请求** — curl 命令发送请求\n2. **响应断言** — HTTP 状态码 + 业务 code + msg + data 字段\n3. **DB 验证** — 必要时查 MySQL 确认数据落库\n4. **Redis 验证** — 必要时查 Redis 确认缓存\u002F锁\u002F限流状态\n5. **UI 验证**（Phase 6） — MCP chrome-devtools 截图 + Console 检查\n\n### Step 3: 输出报告\n\n```\n═══════════════════════════════════════════\n  E2E 业务流程全链路跟踪 — 验证报告\n  日期: 2026-06-22  环境: Docker\n═══════════════════════════════════════════\n\nPhase 1: 认证与注册 ............. 6\u002F6 ✅\nPhase 2: 用户资料与认证 ......... 4\u002F4 ✅\nPhase 3: 跑腿员认证 ............. 3\u002F3 ✅\nPhase 4: 任务发布 ................ 5\u002F5 ✅\nPhase 5: 订单全生命周期 ......... 8\u002F8 ✅\nPhase 6: 管理端全功能 ........... 4\u002F4 ✅\nPhase 7: 边界与异常 ............. 7\u002F7 ✅\n\n总计: 37 通过, 0 失败, 0 跳过\nUI 验证: 8 页面截图通过, 0 Console 错误\n\n阻塞项: 无\n═══════════════════════════════════════════\n✅ 1.0 发布就绪\n```\n\n## General Rules\n\n### 断言标准\n\n每个 API 调用必须验证以下维度：\n\n| 维度 | 方法 | 失败级别 |\n|------|------|---------|\n| HTTP 状态码 | `curl -w \"%{http_code}\"` | **BLOCKER** — 流程中断 |\n| 业务 code | `jq '.code'` 期望 1 或特定 0 | **BLOCKER** — 流程中断 |\n| 响应字段 | `jq '.data.xxx'` 非空\u002F类型正确 | **HIGH** — 记录但可继续 |\n| DB 状态 | MySQL 查询确认记录落库 | **MEDIUM** — 记录 |\n| Redis 状态 | redis-cli 检查 key 存在性\u002FTTL | **MEDIUM** — 记录 |\n| UI 渲染 | MCP 截图 + Console 错误 | **HIGH** — 记录 |\n\n### 测试数据隔离\n\n- 测试用户手机号前缀：`1380000xxxx`（不与生产数据冲突）\n- 测试任务自动过期时间：60 分钟\n- 测试完成后的数据可选择保留（用于后续 Phase）或清理\n\n### 安全验证（内嵌于各 Step）\n\n- [ ] SMS 验证码跨操作隔离（register 码 ≠ login 码）\n- [ ] 暴力破解锁定（5 次错误 → 300s 锁定）\n- [ ] 用户 Token 不能访问管理端接口\n- [ ] 管理端 Token 不能访问用户端接口\n- [ ] 支付幂等（重复扣款拦截）\n- [ ] 频率限制（SMS 5\u002Fmin、登录 10\u002Fmin）\n- [ ] 文件上传鉴权（无 Token 拒绝）\n\n### 状态机验证（Phase 5）\n\n- [ ] Task: 1→2→3→4→5 完整正向流\n- [ ] Task: 1→6 发布者取消\n- [ ] Task: 2\u002F3 状态禁止发布者取消\n- [ ] Order: 1→2→3→4 完整正向流\n- [ ] Order: 1→5 跑腿员取消（5 分钟内）\n- [ ] Order: 3→4 自动完成（可手动触发确认）\n\n## 业务流程总览\n\n完整业务流程拓扑（详见 `references\u002Fbusiness-flows.md`）：\n\n```\n用户注册 ──→ 登录 ──→ 设置支付密码 ──→ 实名认证 ──→ 管理端审核通过\n                                                         │\n                                                         ↓\n                                              申请跑腿员 ──→ 管理端审核通过 ──→ 上线\n                                                                                │\n                                                                                ↓\n钱包充值 ──→ 发布任务（4 种类型） ──→ 任务大厅展示 ──→ 跑腿员接单\n                                                         │\n                                                         ↓\n                                          确认取货 ──→ 确认送达 ──→ 确认完成\n                                                                      │\n                                                                      ↓\n                                                              自动结算 + 信用分更新\n                                                                      │\n                                                                      ↓\n                                                              互相评价 + 追评\n```\n\n## 快速执行\n\n无需 Agent，直接在终端运行：\n\n```bash\n# 完整流程\nbash e2e\u002Frun.sh\n\n# 仅核心路径（~5min）\nbash e2e\u002Frun.sh --quick\n\n# 保留测试数据\nbash e2e\u002Frun.sh --keep\n\n# 分步执行\nbash e2e\u002Fsetup.sh              # 编译 + 环境检查\nbash e2e\u002Fbootstrap.sh          # 注入测试数据\nbash e2e\u002Frun.sh --phase 5      # 仅跑订单流转\nbash e2e\u002Fteardown.sh           # 手动清理\n```\n\n## 参考规范\n\n| 文件 | 内容 |\n|------|------|\n| `references\u002Fbusiness-flows.md` | 7 个 Phase 的完整 API 调用序列 + curl 命令 + 断言 |\n| `references\u002Fapi-endpoints.md` | 全部 60+ API 端点的请求\u002F响应格式速查 |\n| `references\u002Ftest-data.md` | 测试账号、Redis 注入、数据库准备\u002F清理 |\n| `references\u002Fstate-machines.md` | Task\u002FOrder 状态转换矩阵 + 守卫条件 |\n| `references\u002Ffrontend-routes.md` | 管理端 17 路由 + 移动端 34 页面的 UI 验证清单 |\n| `references\u002Fverification-checklist.md` | 每 Step 的断言矩阵 + 通过\u002F失败标准 |\n| `..\u002F..\u002Fe2e\u002Fsetup.sh` | 环境就绪：编译 + Docker 启动 + 健康检查 |\n| `..\u002F..\u002Fe2e\u002Fbootstrap.sh` | 数据注入：SMS 验证码、清理旧数据、预取 Admin Token |\n| `..\u002F..\u002Fe2e\u002Frun.sh` | 编排入口：setup → bootstrap → Phase 1-7 → teardown |\n| `..\u002F..\u002Fe2e\u002Fteardown.sh` | 清理：测试用户\u002F任务\u002F订单\u002FRedis key |\n| `..\u002F..\u002Fe2e\u002F.env.e2e` | 测试变量（手机号、验证码、API 地址等） |\n","# E2E Business Flow Tracker\n\n端到端业务流程全链路跟踪，模拟真实用户操作验证系统完整性和正确性。\n\n## When to use this skill\n\n**触发场景（必须触发）：**\n- 1.0 版本发布前最终验证\n- 重大重构或架构变更后\n- 数据库 schema 变更后\n- 安全机制（JWT\u002F限流\u002F权限）变更后\n- 状态机逻辑修改后\n- 支付\u002F退款流程变更后\n- 用户明确要求\"全链路测试\"、\"端到端验证\"、\"发布前检查\"\n\n**DO NOT use when:**\n- 仅修改文档或注释 → 无运行影响\n- 仅修改 CSS\u002F样式 → 前端代码审查即可\n- 单接口 Bug 修复 → 使用 `docker-test-agent` 针对性测试\n- 纯 UI 调整 → 使用 `frontend-code-reviewer`\n\n## How to use this skill\n\n```\n\u002Fagent:e2e-business-flow-tracker --scope \u003Cfull|phase1-7|quick> --env \u003Clocal|docker>\n```\n\n### 执行模式\n\n| 模式 | 覆盖范围 | 预估耗时 |\n|------|---------|---------|\n| `full` | 全部 7 个 Phase，26 个 Step | 15-20 min |\n| `quick` | Phase 1-2-5 核心路径（认证+任务+订单） | 5-8 min |\n| `phase\u003CN>` | 指定 Phase 1-7 | 2-5 min\u002Fphase |\n\n### 执行流程\n\n```\nPhase 0: Pre-flight Check（编译+环境就绪）\nPhase 1: 认证与注册（6 steps）\nPhase 2: 用户资料与认证（4 steps）\nPhase 3: 跑腿员认证（3 steps）\nPhase 4: 任务发布（5 steps）\nPhase 5: 订单全生命周期（8 steps）\nPhase 6: 管理端全功能（4 steps）\nPhase 7: 边界与异常（集成在各 Step 断言中）\nReport: 汇总通过\u002F失败\u002F阻塞清单\n```\n\n## Agent 工作流\n\n### Step 0: Pre-flight Check\n\n```bash\n# 1. 编译后端\ncd F:\u002Fikeu_runningerrands\u002Fbackend\n.\u002Frunningerrands-server\u002Fmvnw compile -q -DskipTests\n\n# 2. 前端类型检查\ncd F:\u002Fikeu_runningerrands\u002Fadmin\nnpx vue-tsc --noEmit\n\n# 3. 环境健康检查\ncurl -s http:\u002F\u002Flocalhost:8080\u002Fapi\u002Factuator\u002Fhealth\n# 或 Docker: docker compose ps\n```\n\n### Step 1: 环境准备\n\n1. 清理测试数据（删除上次运行产生的用户\u002F任务\u002F订单）\n2. 注入 SMS 验证码到 Redis\n3. 确认测试账号可用\n4. 获取 admin JWT（用于管理端操作）\n\n### Step 2: 按 Phase 顺序执行\n\n每个 Step 包含：\n1. **API 请求** — curl 命令发送请求\n2. **响应断言** — HTTP 状态码 + 业务 code + msg + data 字段\n3. **DB 验证** — 必要时查 MySQL 确认数据落库\n4. **Redis 验证** — 必要时查 Redis 确认缓存\u002F锁\u002F限流状态\n5. **UI 验证**（Phase 6） — MCP chrome-devtools 截图 + Console 检查\n\n### Step 3: 输出报告\n\n```\n═══════════════════════════════════════════\n  E2E 业务流程全链路跟踪 — 验证报告\n  日期: 2026-06-22  环境: Docker\n═══════════════════════════════════════════\n\nPhase 1: 认证与注册 ............. 6\u002F6 ✅\nPhase 2: 用户资料与认证 ......... 4\u002F4 ✅\nPhase 3: 跑腿员认证 ............. 3\u002F3 ✅\nPhase 4: 任务发布 ................ 5\u002F5 ✅\nPhase 5: 订单全生命周期 ......... 8\u002F8 ✅\nPhase 6: 管理端全功能 ........... 4\u002F4 ✅\nPhase 7: 边界与异常 ............. 7\u002F7 ✅\n\n总计: 37 通过, 0 失败, 0 跳过\nUI 验证: 8 页面截图通过, 0 Console 错误\n\n阻塞项: 无\n═══════════════════════════════════════════\n✅ 1.0 发布就绪\n```\n\n## General Rules\n\n### 断言标准\n\n每个 API 调用必须验证以下维度：\n\n| 维度 | 方法 | 失败级别 |\n|------|------|---------|\n| HTTP 状态码 | `curl -w \"%{http_code}\"` | **BLOCKER** — 流程中断 |\n| 业务 code | `jq '.code'` 期望 1 或特定 0 | **BLOCKER** — 流程中断 |\n| 响应字段 | `jq '.data.xxx'` 非空\u002F类型正确 | **HIGH** — 记录但可继续 |\n| DB 状态 | MySQL 查询确认记录落库 | **MEDIUM** — 记录 |\n| Redis 状态 | redis-cli 检查 key 存在性\u002FTTL | **MEDIUM** — 记录 |\n| UI 渲染 | MCP 截图 + Console 错误 | **HIGH** — 记录 |\n\n### 测试数据隔离\n\n- 测试用户手机号前缀：`1380000xxxx`（不与生产数据冲突）\n- 测试任务自动过期时间：60 分钟\n- 测试完成后的数据可选择保留（用于后续 Phase）或清理\n\n### 安全验证（内嵌于各 Step）\n\n- [ ] SMS 验证码跨操作隔离（register 码 ≠ login 码）\n- [ ] 暴力破解锁定（5 次错误 → 300s 锁定）\n- [ ] 用户 Token 不能访问管理端接口\n- [ ] 管理端 Token 不能访问用户端接口\n- [ ] 支付幂等（重复扣款拦截）\n- [ ] 频率限制（SMS 5\u002Fmin、登录 10\u002Fmin）\n- [ ] 文件上传鉴权（无 Token 拒绝）\n\n### 状态机验证（Phase 5）\n\n- [ ] Task: 1→2→3→4→5 完整正向流\n- [ ] Task: 1→6 发布者取消\n- [ ] Task: 2\u002F3 状态禁止发布者取消\n- [ ] Order: 1→2→3→4 完整正向流\n- [ ] Order: 1→5 跑腿员取消（5 分钟内）\n- [ ] Order: 3→4 自动完成（可手动触发确认）\n\n## 业务流程总览\n\n完整业务流程拓扑（详见 `references\u002Fbusiness-flows.md`）：\n\n```\n用户注册 ──→ 登录 ──→ 设置支付密码 ──→ 实名认证 ──→ 管理端审核通过\n                                                         │\n                                                         ↓\n                                              申请跑腿员 ──→ 管理端审核通过 ──→ 上线\n                                                                                │\n                                                                                ↓\n钱包充值 ──→ 发布任务（4 种类型） ──→ 任务大厅展示 ──→ 跑腿员接单\n                                                         │\n                                                         ↓\n                                          确认取货 ──→ 确认送达 ──→ 确认完成\n                                                                      │\n                                                                      ↓\n                                                              自动结算 + 信用分更新\n                                                                      │\n                                                                      ↓\n                                                              互相评价 + 追评\n```\n\n## 快速执行\n\n无需 Agent，直接在终端运行：\n\n```bash\n# 完整流程\nbash e2e\u002Frun.sh\n\n# 仅核心路径（~5min）\nbash e2e\u002Frun.sh --quick\n\n# 保留测试数据\nbash e2e\u002Frun.sh --keep\n\n# 分步执行\nbash e2e\u002Fsetup.sh              # 编译 + 环境检查\nbash e2e\u002Fbootstrap.sh          # 注入测试数据\nbash e2e\u002Frun.sh --phase 5      # 仅跑订单流转\nbash e2e\u002Fteardown.sh           # 手动清理\n```\n\n## 参考规范\n\n| 文件 | 内容 |\n|------|------|\n| `references\u002Fbusiness-flows.md` | 7 个 Phase 的完整 API 调用序列 + curl 命令 + 断言 |\n| `references\u002Fapi-endpoints.md` | 全部 60+ API 端点的请求\u002F响应格式速查 |\n| `references\u002Ftest-data.md` | 测试账号、Redis 注入、数据库准备\u002F清理 |\n| `references\u002Fstate-machines.md` | Task\u002FOrder 状态转换矩阵 + 守卫条件 |\n| `references\u002Ffrontend-routes.md` | 管理端 17 路由 + 移动端 34 页面的 UI 验证清单 |\n| `references\u002Fverification-checklist.md` | 每 Step 的断言矩阵 + 通过\u002F失败标准 |\n| `..\u002F..\u002Fe2e\u002Fsetup.sh` | 环境就绪：编译 + Docker 启动 + 健康检查 |\n| `..\u002F..\u002Fe2e\u002Fbootstrap.sh` | 数据注入：SMS 验证码、清理旧数据、预取 Admin Token |\n| `..\u002F..\u002Fe2e\u002Frun.sh` | 编排入口：setup → bootstrap → Phase 1-7 → teardown |\n| `..\u002F..\u002Fe2e\u002Fteardown.sh` | 清理：测试用户\u002F任务\u002F订单\u002FRedis key |\n| `..\u002F..\u002Fe2e\u002F.env.e2e` | 测试变量（手机号、验证码、API 地址等） |\n",{"name":5,"model":24,"memory":25,"description":7},"sonnet","user","main","14d19341a5ae6e5a3c751328fcc273395da5bd21",".agent\u002Fe2e-business-flow-tracker","https:\u002F\u002Fgithub.com\u002FIkeu-1030\u002FiRun","https:\u002F\u002Fgithub.com\u002FIkeu-1030","Action shatters illusion\u002F","2026-07-02 15:19:58",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Ikeu-1030\u002FiRun --skill e2e-business-flow-tracker",{"tool":39,"command":40},"bunx","bunx skills add Ikeu-1030\u002FiRun --skill e2e-business-flow-tracker",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Ikeu-1030\u002FiRun --skill e2e-business-flow-tracker","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FIkeu-1030\u002FiRun\u002Fblob\u002Fmain\u002F.agent\u002Fe2e-business-flow-tracker\u002FSKILL.md",true,[47,53,57,61,65,69],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fapi-endpoints.md","REFERENCE","参考文档",11535,"https:\u002F\u002Fgithub.com\u002FIkeu-1030\u002FiRun\u002Fblob\u002Fmain\u002F.agent\u002Fe2e-business-flow-tracker\u002Freferences\u002Fapi-endpoints.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fbusiness-flows.md",40266,"https:\u002F\u002Fgithub.com\u002FIkeu-1030\u002FiRun\u002Fblob\u002Fmain\u002F.agent\u002Fe2e-business-flow-tracker\u002Freferences\u002Fbusiness-flows.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Ffrontend-routes.md",8096,"https:\u002F\u002Fgithub.com\u002FIkeu-1030\u002FiRun\u002Fblob\u002Fmain\u002F.agent\u002Fe2e-business-flow-tracker\u002Freferences\u002Ffrontend-routes.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fstate-machines.md",9152,"https:\u002F\u002Fgithub.com\u002FIkeu-1030\u002FiRun\u002Fblob\u002Fmain\u002F.agent\u002Fe2e-business-flow-tracker\u002Freferences\u002Fstate-machines.md",{"path":66,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Ftest-data.md",8763,"https:\u002F\u002Fgithub.com\u002FIkeu-1030\u002FiRun\u002Fblob\u002Fmain\u002F.agent\u002Fe2e-business-flow-tracker\u002Freferences\u002Ftest-data.md",{"path":70,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fverification-checklist.md",15745,"https:\u002F\u002Fgithub.com\u002FIkeu-1030\u002FiRun\u002Fblob\u002Fmain\u002F.agent\u002Fe2e-business-flow-tracker\u002Freferences\u002Fverification-checklist.md",[74,81,88,95,102,109],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M756NR65N494G30JZP84MS7R","understand","Analyze a codebase to produce an interactive knowledge graph for understanding architecture, components, and relationships","https:\u002F\u002Fgithub.com\u002FIkeu-1030\u002FiRun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Funderstand-anything\u002Funderstand-anything-plugin\u002Fskills\u002Funderstand\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M756NPH7BMV8655NPXER0ZAS","understand-onboard","Use when you need to generate an onboarding guide for new team members joining a project","https:\u002F\u002Fgithub.com\u002FIkeu-1030\u002FiRun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Funderstand-anything\u002Funderstand-anything-plugin\u002Fskills\u002Funderstand-onboard\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M756NM7K2DP7KD475N4S3ZXD","understand-knowledge","Analyze a Karpathy-pattern LLM wiki knowledge base and generate an interactive knowledge graph with entity extraction, implicit relationships, and topic clustering.","https:\u002F\u002Fgithub.com\u002FIkeu-1030\u002FiRun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Funderstand-anything\u002Funderstand-anything-plugin\u002Fskills\u002Funderstand-knowledge\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M756NJPJADZ13YRP1D9PEVEF","understand-explain","Use when you need a deep-dive explanation of a specific file, function, or module in the codebase","https:\u002F\u002Fgithub.com\u002FIkeu-1030\u002FiRun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Funderstand-anything\u002Funderstand-anything-plugin\u002Fskills\u002Funderstand-explain\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M756NF79MR3DD69W7XJAT2PB","understand-domain","Extract business domain knowledge from a codebase and generate an interactive domain flow graph. Works standalone (lightweight scan) or derives from an existing \u002Funderstand knowledge graph.","https:\u002F\u002Fgithub.com\u002FIkeu-1030\u002FiRun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Funderstand-anything\u002Funderstand-anything-plugin\u002Fskills\u002Funderstand-domain\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":19},"01M756NCF0HHCSJTMDV85G7KR2","understand-diff","Use when you need to analyze git diffs or pull requests to understand what changed, affected components, and risks","https:\u002F\u002Fgithub.com\u002FIkeu-1030\u002FiRun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Funderstand-anything\u002Funderstand-anything-plugin\u002Fskills\u002Funderstand-diff\u002FSKILL.md",[],[]]