[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6RVKQH06HPDSTACKHGQFWGV":3,"skill-same:01M6RVKQH06HPDSTACKHGQFWGV":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":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":45,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":47,"install":48,"resources":61},"01M6RVKQH06HPDSTACKHGQFWGV","chinese-commit-conventions",null,"中文 commit 与 changelog 配置参考——Conventional Commits 中文适配、commitlint\u002Fhusky\u002Fcommitizen 中文模板、conventional-changelog 中文配置。仅在用户显式 \u002Fchinese-commit-conventions 时调用，不要根据上下文自动触发。","rzx007\u002FVykor","rzx007","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F22313722?v=4","01M6RVGB3GJ05PGEFHQ34TV6T0","Danovan","01M6RVGB7F20SDKPMEN9RS3N0N",3,"MIT","https:\u002F\u002Fgithub.com\u002Frzx007\u002FVykor\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fchinese-commit-conventions\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30],"commit","chinese","conventions","commit conventions","chinese commit conventions","git","changelog","commits","中文","commitlint","conventional commits","husky","2026-11-10 10:12:30",false,"---\nname: chinese-commit-conventions\ndescription: 中文 commit 与 changelog 配置参考——Conventional Commits 中文适配、commitlint\u002Fhusky\u002Fcommitizen 中文模板、conventional-changelog 中文配置。仅在用户显式 \u002Fchinese-commit-conventions 时调用，不要根据上下文自动触发。\nversion: \"1.0.0\"\nlicense: MIT\nmetadata:\n  hermes:\n    tags: [git, chinese]\n---\n\n# 中文 Git 提交规范\n\n## 1. Conventional Commits 中文适配\n\n基于 Conventional Commits 1.0.0 规范，针对中文团队的实际使用习惯进行适配。\n\n### 类型（type）定义\n\n| 类型       | 说明                         | 示例场景                   |\n| ---------- | ---------------------------- | -------------------------- |\n| `feat`     | 新功能                       | 添加用户注册模块           |\n| `fix`      | 修复缺陷                     | 修复登录页白屏问题         |\n| `docs`     | 文档变更                     | 更新 API 接口文档          |\n| `style`    | 代码格式（不影响逻辑）       | 调整缩进、补充分号         |\n| `refactor` | 重构（非新功能、非修复）     | 拆分过长的服务类           |\n| `perf`     | 性能优化                     | 优化首页列表查询速度       |\n| `test`     | 测试相关                     | 补充用户模块单元测试       |\n| `chore`    | 构建\u002F工具\u002F依赖变更           | 升级 webpack 到 v5         |\n| `ci`       | 持续集成配置                 | 修改 GitHub Actions 流程   |\n| `revert`   | 回滚提交                     | 回滚 v2.1.0 的登录重构     |\n\n### 原则\n\n- type 保留英文关键字（工具链兼容性好）\n- scope 和 description 使用中文\n- body 使用中文完整描述\n\n## 2. 中文 commit message 模板\n\n```\n\u003Ctype>(\u003Cscope>): \u003Csubject>\n\n\u003Cbody>\n\n\u003Cfooter>\n```\n\n### 完整示例\n\n```\nfeat(用户模块): 添加手机号一键登录功能\n\n- 接入运营商一键登录 SDK\n- 支持移动、联通、电信三网\n- 登录失败自动降级到短信验证码\n\nCloses #128\n```\n\n```\nfix(订单): 修复并发下单导致库存超卖的问题\n\n在高并发场景下，原有的库存扣减逻辑存在竞态条件。\n改用 Redis 分布式锁 + 数据库乐观锁双重保障。\n\n影响范围：订单服务、库存服务\n测试确认：已通过 500 并发压测验证\n\nCloses #256\n```\n\n## 3. Subject 行规范\n\n### 格式\n\n```\n\u003Ctype>(\u003Cscope>): \u003Cdescription>\n```\n\n### 规则\n\n- **type**: 必填，从上方类型表中选取\n- **scope**: 选填，表示影响范围，使用中文模块名\n  - 示例：`用户模块`、`订单`、`支付`、`基础组件`\n- **description**: 必填，中文简述，不超过 50 个字符\n  - 使用动宾短语：「添加 xxx」「修复 xxx」「优化 xxx」\n  - 不加句号结尾\n  - 不要写「修改了代码」这种无意义描述\n\n### 好的示例\n\n```\nfeat(权限): 添加基于 RBAC 的细粒度权限控制\nfix(支付): 修复微信支付回调签名验证失败的问题\nperf(列表页): 优化大数据量表格的虚拟滚动渲染\nrefactor(网关): 将单体网关拆分为独立微服务\n```\n\n### 反面示例\n\n```\n# 以下写法应避免\nfix: 修了一个 bug\nfeat: 更新代码\nchore: 改了点东西\n```\n\n## 4. Body 编写规范\n\nBody 用于详细说明本次变更的动机、方案和影响。\n\n### 编写要点\n\n- 说明**为什么**要做这个改动（背景\u002F原因）\n- 说明**怎么做**的（技术方案摘要）\n- 说明**影响范围**（哪些模块、接口受影响）\n- 每行不超过 72 个字符（中文约 36 个汉字）\n- 正文与标题之间空一行\n\n### Body 模板\n\n```\n\u003C改动背景和原因>\n\n技术方案：\n- \u003C方案要点 1>\n- \u003C方案要点 2>\n\n影响范围：\u003C受影响的模块或服务>\n```\n\n## 5. Breaking Changes 标注\n\n当提交包含不兼容变更时，必须在 footer 中标注。\n\n### 格式一：footer 标注\n\n```\nfeat(接口): 重构用户信息返回结构\n\n将用户接口返回的扁平结构改为嵌套结构，前端需同步调整字段取值路径。\n\nBREAKING CHANGE: \u002Fapi\u002Fuser\u002Finfo 返回结构变更\n- avatar 字段移入 profile 对象\n- 移除已废弃的 nickname 字段，统一使用 displayName\n```\n\n### 格式二：type 后加感叹号\n\n```\nfeat(接口)!: 重构用户信息返回结构\n```\n\n### 团队约定\n\n- 涉及数据库表结构变更 -> 必须标注 BREAKING CHANGE\n- 涉及公共 API 参数\u002F返回值变更 -> 必须标注\n- 涉及配置文件格式变更 -> 必须标注\n- 标注时须写明迁移方法或升级步骤\n\n## 6. Issue 关联\n\n### GitHub 格式\n\n```\nCloses #128\nRefs #129, #130\n```\n\n### Gitee 格式\n\n```\nCloses #I5ABC1\n相关需求: https:\u002F\u002Fgitee.com\u002Forg\u002Frepo\u002Fissues\u002FI5ABC1\n```\n\n### Coding 格式\n\n```\n关联 Coding 缺陷 #12345\nfixed=project-2024\u002Fissues\u002F678\n```\n\n### 通用写法\n\n```\n# footer 中关联多个平台\nCloses #128\nJira: PROJ-456\n禅道: #789\n```\n\n## 7. Changelog 自动生成配置\n\n### 安装 conventional-changelog\n\n```bash\nnpm install -D conventional-changelog-cli conventional-changelog-conventionalcommits\n```\n\n### package.json 脚本\n\n```json\n{\n  \"scripts\": {\n    \"changelog\": \"conventional-changelog -p conventionalcommits -i CHANGELOG.md -s\",\n    \"changelog:all\": \"conventional-changelog -p conventionalcommits -i CHANGELOG.md -s -r 0\",\n    \"release\": \"standard-version\"\n  }\n}\n```\n\n### .versionrc.js 中文配置\n\n```javascript\nmodule.exports = {\n  types: [\n    { type: 'feat', section: '新功能' },\n    { type: 'fix', section: '缺陷修复' },\n    { type: 'perf', section: '性能优化' },\n    { type: 'refactor', section: '代码重构' },\n    { type: 'docs', section: '文档更新' },\n    { type: 'test', section: '测试' },\n    { type: 'chore', section: '构建\u002F工具', hidden: true },\n    { type: 'ci', section: '持续集成', hidden: true },\n    { type: 'style', section: '代码格式', hidden: true }\n  ],\n  commitUrlFormat: '{{host}}\u002F{{owner}}\u002F{{repository}}\u002Fcommit\u002F{{hash}}',\n  compareUrlFormat: '{{host}}\u002F{{owner}}\u002F{{repository}}\u002Fcompare\u002F{{previousTag}}...{{currentTag}}'\n}\n```\n\n## 8. commitlint 中文配置\n\n### 安装\n\n```bash\nnpm install -D @commitlint\u002Fcli @commitlint\u002Fconfig-conventional\n```\n\n### commitlint.config.js\n\n```javascript\nmodule.exports = {\n  extends: ['@commitlint\u002Fconfig-conventional'],\n  rules: {\n    'type-enum': [2, 'always', [\n      'feat', 'fix', 'docs', 'style', 'refactor',\n      'perf', 'test', 'chore', 'ci', 'revert'\n    ]],\n    'type-case': [2, 'always', 'lower-case'],\n    'type-empty': [2, 'never'],\n    'subject-empty': [2, 'never'],\n    'subject-max-length': [2, 'always', 100],\n    \u002F\u002F 允许中文字符，关闭 subject-case 限制\n    'subject-case': [0],\n    \u002F\u002F 关闭 header-max-length 或放宽（中文占宽较大）\n    'header-max-length': [2, 'always', 120],\n    'body-max-line-length': [1, 'always', 200],\n    'footer-max-line-length': [1, 'always', 200]\n  },\n  prompt: {\n    messages: {\n      type: '选择提交类型:',\n      scope: '输入影响范围（可选）:',\n      subject: '填写简短描述:',\n      body: '填写详细描述（可选，使用 \"|\" 换行）:',\n      breaking: '列出不兼容变更（可选）:',\n      footer: '关联的 Issue（可选，例如 #123）:',\n      confirmCommit: '确认提交以上信息？'\n    }\n  }\n}\n```\n\n## 9. husky + lint-staged 集成\n\n### 安装与初始化\n\n```bash\nnpm install -D husky lint-staged\nnpx husky init\n```\n\n### 配置 commit-msg 钩子\n\n```bash\n# .husky\u002Fcommit-msg\nnpx --no -- commitlint --edit \"$1\"\n```\n\n### 配置 pre-commit 钩子\n\n```bash\n# .husky\u002Fpre-commit\nnpx lint-staged\n```\n\n### lint-staged 配置（package.json）\n\n```json\n{\n  \"lint-staged\": {\n    \"*.{js,ts,jsx,tsx,vue}\": [\n      \"eslint --fix\",\n      \"prettier --write\"\n    ],\n    \"*.{css,scss,less}\": [\n      \"stylelint --fix\",\n      \"prettier --write\"\n    ],\n    \"*.md\": [\n      \"prettier --write\"\n    ]\n  }\n}\n```\n\n### 交互式提交（可选）\n\n```bash\nnpm install -D commitizen cz-conventional-changelog\n\n# package.json 中添加\n{\n  \"config\": {\n    \"commitizen\": {\n      \"path\": \"cz-conventional-changelog\"\n    }\n  },\n  \"scripts\": {\n    \"commit\": \"cz\"\n  }\n}\n```\n\n运行 `npm run commit` 即可进入交互式提交引导。\n\n## 10. 团队规范检查清单\n\n### 提交前自查\n\n- [ ] type 是否正确选择（feat\u002Ffix\u002Fdocs\u002F...）\n- [ ] scope 是否准确描述了影响模块\n- [ ] subject 是否为动宾短语且不超过 50 字符\n- [ ] subject 末尾是否去掉了句号\n- [ ] body 是否说明了变更原因和方案\n- [ ] 不兼容变更是否标注了 BREAKING CHANGE\n- [ ] 相关 Issue 是否已关联\n- [ ] 一次提交是否只做了一件事（原子性）\n\n### 团队落地步骤\n\n1. **工具链配置**：按上述步骤配置 commitlint + husky，让规范可执行\n2. **模板共享**：将 `.commitlintrc`、`.husky\u002F` 等配置提交到仓库\n3. **团队培训**：组织 15 分钟的规范说明会，演示工具使用\n4. **Code Review**：Review 时关注 commit message 质量\n5. **持续迭代**：每季度回顾规范执行情况，根据团队反馈调整\n\n### 常见问题\n\n**Q: 中英文混排时空格怎么处理？**\nA: 中文与英文\u002F数字之间加一个空格，如「添加 Redis 缓存」。\n\n**Q: scope 用中文还是英文？**\nA: 团队内统一即可。推荐中文（可读性好），但需在 commitlint 中关闭 scope-case 检查。\n\n**Q: 多人协作时如何保证规范一致？**\nA: 靠工具而非靠自觉。配置好 husky + commitlint，不符合规范的提交会被拦截。\n","# 中文 Git 提交规范\n\n## 1. Conventional Commits 中文适配\n\n基于 Conventional Commits 1.0.0 规范，针对中文团队的实际使用习惯进行适配。\n\n### 类型（type）定义\n\n| 类型       | 说明                         | 示例场景                   |\n| ---------- | ---------------------------- | -------------------------- |\n| `feat`     | 新功能                       | 添加用户注册模块           |\n| `fix`      | 修复缺陷                     | 修复登录页白屏问题         |\n| `docs`     | 文档变更                     | 更新 API 接口文档          |\n| `style`    | 代码格式（不影响逻辑）       | 调整缩进、补充分号         |\n| `refactor` | 重构（非新功能、非修复）     | 拆分过长的服务类           |\n| `perf`     | 性能优化                     | 优化首页列表查询速度       |\n| `test`     | 测试相关                     | 补充用户模块单元测试       |\n| `chore`    | 构建\u002F工具\u002F依赖变更           | 升级 webpack 到 v5         |\n| `ci`       | 持续集成配置                 | 修改 GitHub Actions 流程   |\n| `revert`   | 回滚提交                     | 回滚 v2.1.0 的登录重构     |\n\n### 原则\n\n- type 保留英文关键字（工具链兼容性好）\n- scope 和 description 使用中文\n- body 使用中文完整描述\n\n## 2. 中文 commit message 模板\n\n```\n\u003Ctype>(\u003Cscope>): \u003Csubject>\n\n\u003Cbody>\n\n\u003Cfooter>\n```\n\n### 完整示例\n\n```\nfeat(用户模块): 添加手机号一键登录功能\n\n- 接入运营商一键登录 SDK\n- 支持移动、联通、电信三网\n- 登录失败自动降级到短信验证码\n\nCloses #128\n```\n\n```\nfix(订单): 修复并发下单导致库存超卖的问题\n\n在高并发场景下，原有的库存扣减逻辑存在竞态条件。\n改用 Redis 分布式锁 + 数据库乐观锁双重保障。\n\n影响范围：订单服务、库存服务\n测试确认：已通过 500 并发压测验证\n\nCloses #256\n```\n\n## 3. Subject 行规范\n\n### 格式\n\n```\n\u003Ctype>(\u003Cscope>): \u003Cdescription>\n```\n\n### 规则\n\n- **type**: 必填，从上方类型表中选取\n- **scope**: 选填，表示影响范围，使用中文模块名\n  - 示例：`用户模块`、`订单`、`支付`、`基础组件`\n- **description**: 必填，中文简述，不超过 50 个字符\n  - 使用动宾短语：「添加 xxx」「修复 xxx」「优化 xxx」\n  - 不加句号结尾\n  - 不要写「修改了代码」这种无意义描述\n\n### 好的示例\n\n```\nfeat(权限): 添加基于 RBAC 的细粒度权限控制\nfix(支付): 修复微信支付回调签名验证失败的问题\nperf(列表页): 优化大数据量表格的虚拟滚动渲染\nrefactor(网关): 将单体网关拆分为独立微服务\n```\n\n### 反面示例\n\n```\n# 以下写法应避免\nfix: 修了一个 bug\nfeat: 更新代码\nchore: 改了点东西\n```\n\n## 4. Body 编写规范\n\nBody 用于详细说明本次变更的动机、方案和影响。\n\n### 编写要点\n\n- 说明**为什么**要做这个改动（背景\u002F原因）\n- 说明**怎么做**的（技术方案摘要）\n- 说明**影响范围**（哪些模块、接口受影响）\n- 每行不超过 72 个字符（中文约 36 个汉字）\n- 正文与标题之间空一行\n\n### Body 模板\n\n```\n\u003C改动背景和原因>\n\n技术方案：\n- \u003C方案要点 1>\n- \u003C方案要点 2>\n\n影响范围：\u003C受影响的模块或服务>\n```\n\n## 5. Breaking Changes 标注\n\n当提交包含不兼容变更时，必须在 footer 中标注。\n\n### 格式一：footer 标注\n\n```\nfeat(接口): 重构用户信息返回结构\n\n将用户接口返回的扁平结构改为嵌套结构，前端需同步调整字段取值路径。\n\nBREAKING CHANGE: \u002Fapi\u002Fuser\u002Finfo 返回结构变更\n- avatar 字段移入 profile 对象\n- 移除已废弃的 nickname 字段，统一使用 displayName\n```\n\n### 格式二：type 后加感叹号\n\n```\nfeat(接口)!: 重构用户信息返回结构\n```\n\n### 团队约定\n\n- 涉及数据库表结构变更 -> 必须标注 BREAKING CHANGE\n- 涉及公共 API 参数\u002F返回值变更 -> 必须标注\n- 涉及配置文件格式变更 -> 必须标注\n- 标注时须写明迁移方法或升级步骤\n\n## 6. Issue 关联\n\n### GitHub 格式\n\n```\nCloses #128\nRefs #129, #130\n```\n\n### Gitee 格式\n\n```\nCloses #I5ABC1\n相关需求: https:\u002F\u002Fgitee.com\u002Forg\u002Frepo\u002Fissues\u002FI5ABC1\n```\n\n### Coding 格式\n\n```\n关联 Coding 缺陷 #12345\nfixed=project-2024\u002Fissues\u002F678\n```\n\n### 通用写法\n\n```\n# footer 中关联多个平台\nCloses #128\nJira: PROJ-456\n禅道: #789\n```\n\n## 7. Changelog 自动生成配置\n\n### 安装 conventional-changelog\n\n```bash\nnpm install -D conventional-changelog-cli conventional-changelog-conventionalcommits\n```\n\n### package.json 脚本\n\n```json\n{\n  \"scripts\": {\n    \"changelog\": \"conventional-changelog -p conventionalcommits -i CHANGELOG.md -s\",\n    \"changelog:all\": \"conventional-changelog -p conventionalcommits -i CHANGELOG.md -s -r 0\",\n    \"release\": \"standard-version\"\n  }\n}\n```\n\n### .versionrc.js 中文配置\n\n```javascript\nmodule.exports = {\n  types: [\n    { type: 'feat', section: '新功能' },\n    { type: 'fix', section: '缺陷修复' },\n    { type: 'perf', section: '性能优化' },\n    { type: 'refactor', section: '代码重构' },\n    { type: 'docs', section: '文档更新' },\n    { type: 'test', section: '测试' },\n    { type: 'chore', section: '构建\u002F工具', hidden: true },\n    { type: 'ci', section: '持续集成', hidden: true },\n    { type: 'style', section: '代码格式', hidden: true }\n  ],\n  commitUrlFormat: '{{host}}\u002F{{owner}}\u002F{{repository}}\u002Fcommit\u002F{{hash}}',\n  compareUrlFormat: '{{host}}\u002F{{owner}}\u002F{{repository}}\u002Fcompare\u002F{{previousTag}}...{{currentTag}}'\n}\n```\n\n## 8. commitlint 中文配置\n\n### 安装\n\n```bash\nnpm install -D @commitlint\u002Fcli @commitlint\u002Fconfig-conventional\n```\n\n### commitlint.config.js\n\n```javascript\nmodule.exports = {\n  extends: ['@commitlint\u002Fconfig-conventional'],\n  rules: {\n    'type-enum': [2, 'always', [\n      'feat', 'fix', 'docs', 'style', 'refactor',\n      'perf', 'test', 'chore', 'ci', 'revert'\n    ]],\n    'type-case': [2, 'always', 'lower-case'],\n    'type-empty': [2, 'never'],\n    'subject-empty': [2, 'never'],\n    'subject-max-length': [2, 'always', 100],\n    \u002F\u002F 允许中文字符，关闭 subject-case 限制\n    'subject-case': [0],\n    \u002F\u002F 关闭 header-max-length 或放宽（中文占宽较大）\n    'header-max-length': [2, 'always', 120],\n    'body-max-line-length': [1, 'always', 200],\n    'footer-max-line-length': [1, 'always', 200]\n  },\n  prompt: {\n    messages: {\n      type: '选择提交类型:',\n      scope: '输入影响范围（可选）:',\n      subject: '填写简短描述:',\n      body: '填写详细描述（可选，使用 \"|\" 换行）:',\n      breaking: '列出不兼容变更（可选）:',\n      footer: '关联的 Issue（可选，例如 #123）:',\n      confirmCommit: '确认提交以上信息？'\n    }\n  }\n}\n```\n\n## 9. husky + lint-staged 集成\n\n### 安装与初始化\n\n```bash\nnpm install -D husky lint-staged\nnpx husky init\n```\n\n### 配置 commit-msg 钩子\n\n```bash\n# .husky\u002Fcommit-msg\nnpx --no -- commitlint --edit \"$1\"\n```\n\n### 配置 pre-commit 钩子\n\n```bash\n# .husky\u002Fpre-commit\nnpx lint-staged\n```\n\n### lint-staged 配置（package.json）\n\n```json\n{\n  \"lint-staged\": {\n    \"*.{js,ts,jsx,tsx,vue}\": [\n      \"eslint --fix\",\n      \"prettier --write\"\n    ],\n    \"*.{css,scss,less}\": [\n      \"stylelint --fix\",\n      \"prettier --write\"\n    ],\n    \"*.md\": [\n      \"prettier --write\"\n    ]\n  }\n}\n```\n\n### 交互式提交（可选）\n\n```bash\nnpm install -D commitizen cz-conventional-changelog\n\n# package.json 中添加\n{\n  \"config\": {\n    \"commitizen\": {\n      \"path\": \"cz-conventional-changelog\"\n    }\n  },\n  \"scripts\": {\n    \"commit\": \"cz\"\n  }\n}\n```\n\n运行 `npm run commit` 即可进入交互式提交引导。\n\n## 10. 团队规范检查清单\n\n### 提交前自查\n\n- [ ] type 是否正确选择（feat\u002Ffix\u002Fdocs\u002F...）\n- [ ] scope 是否准确描述了影响模块\n- [ ] subject 是否为动宾短语且不超过 50 字符\n- [ ] subject 末尾是否去掉了句号\n- [ ] body 是否说明了变更原因和方案\n- [ ] 不兼容变更是否标注了 BREAKING CHANGE\n- [ ] 相关 Issue 是否已关联\n- [ ] 一次提交是否只做了一件事（原子性）\n\n### 团队落地步骤\n\n1. **工具链配置**：按上述步骤配置 commitlint + husky，让规范可执行\n2. **模板共享**：将 `.commitlintrc`、`.husky\u002F` 等配置提交到仓库\n3. **团队培训**：组织 15 分钟的规范说明会，演示工具使用\n4. **Code Review**：Review 时关注 commit message 质量\n5. **持续迭代**：每季度回顾规范执行情况，根据团队反馈调整\n\n### 常见问题\n\n**Q: 中英文混排时空格怎么处理？**\nA: 中文与英文\u002F数字之间加一个空格，如「添加 Redis 缓存」。\n\n**Q: scope 用中文还是英文？**\nA: 团队内统一即可。推荐中文（可读性好），但需在 commitlint 中关闭 scope-case 检查。\n\n**Q: 多人协作时如何保证规范一致？**\nA: 靠工具而非靠自觉。配置好 husky + commitlint，不符合规范的提交会被拦截。\n",{"name":5,"license":15,"version":36,"metadata":37,"description":7},"1.0.0",{"hermes":38},{"tags":39},[24,20],"main","11fa3057bb1aff51d77b97648803dec2b2ea62d9",".agents\u002Fskills\u002Fchinese-commit-conventions",2,"https:\u002F\u002Fgithub.com\u002Frzx007\u002FVykor","https:\u002F\u002Frzx007.github.io\u002FVykor\u002F","https:\u002F\u002Fgithub.com\u002Frzx007","2026-11-13 23:57:39",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add rzx007\u002FVykor --skill chinese-commit-conventions",{"tool":54,"command":55},"bunx","bunx skills add rzx007\u002FVykor --skill chinese-commit-conventions",{"tool":57,"command":58},"pnpm","pnpm dlx skills add rzx007\u002FVykor --skill chinese-commit-conventions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frzx007\u002FVykor\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fchinese-commit-conventions\u002FSKILL.md",true,[],[63,83,95,118,130,143],{"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":6,"sourceHtmlUrl":67,"categories":68,"keywords":79,"publishedAt":31},"01M6RVYYTPGG9WWWV4QAY0YEY3","writing-skills","当创建新技能、编辑现有技能或在部署前验证技能是否有效时使用","https:\u002F\u002Fgithub.com\u002Frzx007\u002FVykor\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[69,74],{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[80,81,82],"writing skills","writing","documentation",{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":91,"publishedAt":31},"01M6RVYE486HE8NQ2M4G5DNG63","writing-plans","当你有规格说明或需求用于多步骤任务时使用，在动手写代码之前","https:\u002F\u002Fgithub.com\u002Frzx007\u002FVykor\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[89,90],{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},[92,93,81,94,82],"plans","writing plans","planning",{"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":104,"publishedAt":31},"01M6RVY778PEDPWQ0DCM25QW3A","workflow-runner","在 Claude Code \u002F OpenClaw \u002F Cursor 中直接运行 agency-orchestrator YAML 工作流——无需 API key，使用当前会话的 LLM 作为执行引擎。当用户提供 .yaml 工作流文件或要求多角色协作完成任务时触发。","https:\u002F\u002Fgithub.com\u002Frzx007\u002FVykor\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fworkflow-runner\u002FSKILL.md",[101],{"categoryNo":102,"categoryName":103,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000023","Skill与智能体开发",[105,106,107,108,109,110,111,112,113,114,115,116,117],"workflow runner","runner","workflow","协作","文件","agency","orchestrator","cursor","api","execution","yaml","code","openclaw",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":31},"01M6RVY4NR6RRPV174AB706A13","verification-before-completion","在宣称工作完成、已修复或测试通过之前使用，在提交或创建 PR 之前——必须运行验证命令并确认输出后才能声称成功；始终用证据支撑断言","https:\u002F\u002Fgithub.com\u002Frzx007\u002FVykor\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[125,126,127,128,129],"verification before completion","verification","quality","pr","testing",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":31},"01M6RVY1ZQ6ADVCZGBS371HD88","using-superpowers","在开始任何对话时使用——确立如何查找和使用技能，要求在任何响应（包括澄清性问题）之前调用 Skill 工具","https:\u002F\u002Fgithub.com\u002Frzx007\u002FVykor\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fusing-superpowers\u002FSKILL.md",[],[137,138,139,140,141,142],"superpowers","using superpowers","对话","Meta","工具","getting-started",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":31},"01M6RVXJFEQ00P7XBQ8FBEKKJ2","using-git-worktrees","当需要开始与当前工作区隔离的功能开发，或在执行实现计划之前使用——通过原生工具或 git worktree 回退机制确保隔离工作区存在","https:\u002F\u002Fgithub.com\u002Frzx007\u002FVykor\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fusing-git-worktrees\u002FSKILL.md",[],[150,24,151,152,153,107,154,155,141],"using git worktrees","git worktrees","worktrees","Using git","worktree","git worktree"]