[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CX2VT6991XZKPVBFJWM6RS":3,"skill-same:01M7CX2VT6991XZKPVBFJWM6RS":63},{"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":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":6,"ownerDescription":42,"updatedAt":43,"install":44,"resources":56},"01M7CX2VT6991XZKPVBFJWM6RS","conventional-git",null,"Conventional Commits v1.0.0 branch naming, worktree naming, and commit message standards for GitHub and GitLab projects. Use when creating branches, naming worktrees, writing commits, generating commit messages, reviewing branch conventions, or setting up changelog automation. Apply when your project needs consistent git history, SemVer-driven releases, parseable changelog generation, or automatic issue closing. Trigger when the user asks how to name a worktree, create a git worktree, or organize worktrees alongside branches.","om-scogo\u002Fskillsh-scraper","om-scogo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160466840?v=4","01M79AWB6DFVCQ7RK70CS34B96","Om Achrekar","01M79AWB6ZM9SKR8KDH1WSSM22",0,"MIT","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fsamber-cc-skills\u002Fconventional-git\u002FSkill.md",[],[],"2026-11-15 14:19:17",false,"---\nname: conventional-git\ndescription: Conventional Commits v1.0.0 branch naming, worktree naming, and commit message standards for GitHub and GitLab projects. Use when creating branches, naming worktrees, writing commits, generating commit messages, reviewing branch conventions, or setting up changelog automation. Apply when your project needs consistent git history, SemVer-driven releases, parseable changelog generation, or automatic issue closing. Trigger when the user asks how to name a worktree, create a git worktree, or organize worktrees alongside branches.\nuser-invocable: true\nlicense: MIT\ncompatibility: Designed for Claude Code or similar AI coding agents. Requires git.\nmetadata:\n  author: samber\n  version: \"1.2.0\"\n  openclaw:\n    emoji: \"📝\"\n    homepage: https:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills\n    requires:\n      bins:\n        - git\nallowed-tools: Read Edit Write Glob Grep Bash(git:*) Bash(gh:*)\n---\n\n# Conventional Commits & Branch Naming\n\nFollow Conventional Commits v1.0.0 for both branch names and commit messages — consistent naming lets tools auto-generate changelogs, enforce SemVer bumps, and filter history by concern.\n\n## Branch Naming\n\nFormat: `\u003Ctype>\u002F[issue-]\u003Cdescription>` — lowercase, hyphens only, no special chars except `\u002F`.\n\n```\nfeat\u002Fuser-authentication\nfeat\u002F42-user-authentication\nfix\u002Flogin-race-condition\nfix\u002F87-login-race-condition\ndocs\u002Fapi-reference-update\nrefactor\u002Fpayment-module\n```\n\nPrefix with the issue number when one exists — GitHub and GitLab auto-link it and it makes `git log` immediately traceable to the tracker. Keep the description under 50 characters — most git UIs truncate branch names in lists around that length. Match the type to the work you're doing — this is the contract readers use to understand the branch purpose at a glance.\n\nNEVER include `worktree` in a branch name — git worktrees are a local checkout mechanism, not a branch concept; the name would leak implementation details into the remote and confuse other contributors.\n\n## Worktree Naming\n\nWorktrees are local checkout directories — they never appear in the remote. Place them under `.claude\u002Fworktrees\u002F` and name them by replacing the branch `\u002F` separator with `-`.\n\n```\ngit worktree add .claude\u002Fworktrees\u002Ffeat-user-authentication feat\u002Fuser-authentication\ngit worktree add .claude\u002Fworktrees\u002Ffix-87-login-race-condition fix\u002F87-login-race-condition\n```\n\nThe directory name mirrors the branch name so `git worktree list` stays readable and each worktree is immediately traceable to its branch without inspecting the checkout. Run `git worktree list` before creating a new one — reuse an existing worktree if it already covers the same branch.\n\nKeep worktrees scoped to a single branch. Doing unrelated work inside someone else's worktree obscures which changes belong where and makes cleanup error-prone.\n\nRemove the worktree once its branch is merged — either after a local merge or after the pull\u002Fmerge request is closed on the remote. Stale worktrees accumulate and make `git worktree list` unreadable.\n\n```bash\ngit worktree remove .claude\u002Fworktrees\u002Ffeat-user-authentication   # branch merged locally\ngit worktree prune                                                # remove refs to already-deleted directories\n```\n\n## Commit Message Format\n\n```\n\u003Ctype>[optional scope]: \u003Cdescription>\n[optional body]\n[optional footer(s)]\n```\n\n**Types:**\n\n| Type       | SemVer | When                         |\n| ---------- | ------ | ---------------------------- |\n| `feat`     | MINOR  | New feature                  |\n| `fix`      | PATCH  | Bug fix                      |\n| `docs`     | —      | Docs only                    |\n| `style`    | —      | Formatting, no logic change  |\n| `refactor` | —      | Restructure, no feature\u002Ffix  |\n| `perf`     | —      | Performance improvement      |\n| `test`     | —      | Add\u002Ffix tests                |\n| `build`    | —      | Build system, deps           |\n| `ci`       | —      | CI config                    |\n| `chore`    | —      | Anything else (not src\u002Ftest) |\n| `revert`   | —      | Reverts a previous commit    |\n\n**Rules:**\n\n- Subject line ≤ 72 characters — git log and GitHub\u002FGitLab UIs silently truncate longer subjects\n- Imperative mood: \"add\" not \"added\" — reads as an instruction, not a history log\n- No capital letter, no trailing period — enforces uniform parsing by changelog tools\n- Body separated by blank line — parsers split header\u002Fbody at the first blank line\n- Breaking changes: use `!` after type\u002Fscope, or add `BREAKING CHANGE:` footer (triggers MAJOR bump) — body-only descriptions are invisible to changelog tools\n- `revert` commits SHOULD include `This reverts commit \u003Chash>.` in the body — `git revert` generates this automatically; don't strip it\n- NEVER add a Claude signature, AI agent attribution, or `Co-authored-by` trailer for Claude or any other AI agent to commits\n\n**Examples:**\n\n```\nfeat(auth): add JWT token refresh\n```\n\n```\nfix: prevent race condition on concurrent requests\n\nIntroduce request ID and reference to latest request.\nDismiss responses from stale requests.\n```\n\n```\nrefactor!: drop support for Go 1.18\n\nBREAKING CHANGE: Go 1.18 no longer supported; uses stdlib APIs from 1.21+\n```\n\n## Closing Issues via Commit Messages\n\nBoth GitHub and GitLab detect keywords in commit messages and automatically close the referenced issue when the commit lands on the default branch. Place the reference in the **footer** (preferred — keeps the subject line clean).\n\n**Keywords:** `close`, `closes`, `closed`, `fix`, `fixes`, `fixed`, `resolve`, `resolves`, `resolved` — case-insensitive.\n\n**GitHub:**\n\n```\nfix(auth): prevent token expiry race condition\n\nCloses #42\nCloses owner\u002Frepo#99\n```\n\n- Triggers when merged into the **default branch** (usually `main`)\n- Cross-repo: `Closes owner\u002Frepo#42`\n- Close multiple: `Closes #42, closes #43`\n- Works in PR descriptions too\n\n**GitLab:**\n\n```\nfeat: add dark mode support\n\nResolves #101\nCloses group\u002Fproject#42\n```\n\n- Triggers when merged into the **default branch** (configurable per project)\n- Cross-project: `Closes group\u002Fproject#42`\n- Close multiple: `Closes #101, closes #102`\n- Works in MR descriptions too\n\n**Tip:** Pair with the commit type — `fix:` closing a bug issue, `feat:` closing a feature request — keeps the changelog semantically coherent.\n\n## Common Mistakes\n\n| Mistake | Fix |\n| --- | --- |\n| `feat: Added login page` | `feat: add login page` — imperative, no capital |\n| `fix: fix bug.` | `fix: fix bug` — no trailing period |\n| Subject over 72 chars | Shorten; move detail to body |\n| Breaking change only in body | Add `!` or `BREAKING CHANGE:` footer — tools won't detect body-only |\n| `feat(adding-auth): ...` | `feat(auth): ...` — scope is a noun, not a verb |\n| Closes #42 in subject line | Move to footer — keeps subject clean and parseable |\n\n## Best Practices\n\n- Align branch type and commit type — `feat\u002Fauth-*` branch → `feat(auth):` commits\n- One concern per branch — mixing fixes into feature branches obscures the changelog\n- Use scope consistently within a branch — `feat(auth):` throughout, not `feat(user):` mid-way\n- **Squash merge:** when squash-merging a PR\u002FMR, the branch commits are collapsed into one — the PR\u002FMR title becomes the commit message. If the title doesn't follow conventional commits format, changelog generation breaks silently. Always set the PR title before squashing.\n","# Conventional Commits & Branch Naming\n\nFollow Conventional Commits v1.0.0 for both branch names and commit messages — consistent naming lets tools auto-generate changelogs, enforce SemVer bumps, and filter history by concern.\n\n## Branch Naming\n\nFormat: `\u003Ctype>\u002F[issue-]\u003Cdescription>` — lowercase, hyphens only, no special chars except `\u002F`.\n\n```\nfeat\u002Fuser-authentication\nfeat\u002F42-user-authentication\nfix\u002Flogin-race-condition\nfix\u002F87-login-race-condition\ndocs\u002Fapi-reference-update\nrefactor\u002Fpayment-module\n```\n\nPrefix with the issue number when one exists — GitHub and GitLab auto-link it and it makes `git log` immediately traceable to the tracker. Keep the description under 50 characters — most git UIs truncate branch names in lists around that length. Match the type to the work you're doing — this is the contract readers use to understand the branch purpose at a glance.\n\nNEVER include `worktree` in a branch name — git worktrees are a local checkout mechanism, not a branch concept; the name would leak implementation details into the remote and confuse other contributors.\n\n## Worktree Naming\n\nWorktrees are local checkout directories — they never appear in the remote. Place them under `.claude\u002Fworktrees\u002F` and name them by replacing the branch `\u002F` separator with `-`.\n\n```\ngit worktree add .claude\u002Fworktrees\u002Ffeat-user-authentication feat\u002Fuser-authentication\ngit worktree add .claude\u002Fworktrees\u002Ffix-87-login-race-condition fix\u002F87-login-race-condition\n```\n\nThe directory name mirrors the branch name so `git worktree list` stays readable and each worktree is immediately traceable to its branch without inspecting the checkout. Run `git worktree list` before creating a new one — reuse an existing worktree if it already covers the same branch.\n\nKeep worktrees scoped to a single branch. Doing unrelated work inside someone else's worktree obscures which changes belong where and makes cleanup error-prone.\n\nRemove the worktree once its branch is merged — either after a local merge or after the pull\u002Fmerge request is closed on the remote. Stale worktrees accumulate and make `git worktree list` unreadable.\n\n```bash\ngit worktree remove .claude\u002Fworktrees\u002Ffeat-user-authentication   # branch merged locally\ngit worktree prune                                                # remove refs to already-deleted directories\n```\n\n## Commit Message Format\n\n```\n\u003Ctype>[optional scope]: \u003Cdescription>\n[optional body]\n[optional footer(s)]\n```\n\n**Types:**\n\n| Type       | SemVer | When                         |\n| ---------- | ------ | ---------------------------- |\n| `feat`     | MINOR  | New feature                  |\n| `fix`      | PATCH  | Bug fix                      |\n| `docs`     | —      | Docs only                    |\n| `style`    | —      | Formatting, no logic change  |\n| `refactor` | —      | Restructure, no feature\u002Ffix  |\n| `perf`     | —      | Performance improvement      |\n| `test`     | —      | Add\u002Ffix tests                |\n| `build`    | —      | Build system, deps           |\n| `ci`       | —      | CI config                    |\n| `chore`    | —      | Anything else (not src\u002Ftest) |\n| `revert`   | —      | Reverts a previous commit    |\n\n**Rules:**\n\n- Subject line ≤ 72 characters — git log and GitHub\u002FGitLab UIs silently truncate longer subjects\n- Imperative mood: \"add\" not \"added\" — reads as an instruction, not a history log\n- No capital letter, no trailing period — enforces uniform parsing by changelog tools\n- Body separated by blank line — parsers split header\u002Fbody at the first blank line\n- Breaking changes: use `!` after type\u002Fscope, or add `BREAKING CHANGE:` footer (triggers MAJOR bump) — body-only descriptions are invisible to changelog tools\n- `revert` commits SHOULD include `This reverts commit \u003Chash>.` in the body — `git revert` generates this automatically; don't strip it\n- NEVER add a Claude signature, AI agent attribution, or `Co-authored-by` trailer for Claude or any other AI agent to commits\n\n**Examples:**\n\n```\nfeat(auth): add JWT token refresh\n```\n\n```\nfix: prevent race condition on concurrent requests\n\nIntroduce request ID and reference to latest request.\nDismiss responses from stale requests.\n```\n\n```\nrefactor!: drop support for Go 1.18\n\nBREAKING CHANGE: Go 1.18 no longer supported; uses stdlib APIs from 1.21+\n```\n\n## Closing Issues via Commit Messages\n\nBoth GitHub and GitLab detect keywords in commit messages and automatically close the referenced issue when the commit lands on the default branch. Place the reference in the **footer** (preferred — keeps the subject line clean).\n\n**Keywords:** `close`, `closes`, `closed`, `fix`, `fixes`, `fixed`, `resolve`, `resolves`, `resolved` — case-insensitive.\n\n**GitHub:**\n\n```\nfix(auth): prevent token expiry race condition\n\nCloses #42\nCloses owner\u002Frepo#99\n```\n\n- Triggers when merged into the **default branch** (usually `main`)\n- Cross-repo: `Closes owner\u002Frepo#42`\n- Close multiple: `Closes #42, closes #43`\n- Works in PR descriptions too\n\n**GitLab:**\n\n```\nfeat: add dark mode support\n\nResolves #101\nCloses group\u002Fproject#42\n```\n\n- Triggers when merged into the **default branch** (configurable per project)\n- Cross-project: `Closes group\u002Fproject#42`\n- Close multiple: `Closes #101, closes #102`\n- Works in MR descriptions too\n\n**Tip:** Pair with the commit type — `fix:` closing a bug issue, `feat:` closing a feature request — keeps the changelog semantically coherent.\n\n## Common Mistakes\n\n| Mistake | Fix |\n| --- | --- |\n| `feat: Added login page` | `feat: add login page` — imperative, no capital |\n| `fix: fix bug.` | `fix: fix bug` — no trailing period |\n| Subject over 72 chars | Shorten; move detail to body |\n| Breaking change only in body | Add `!` or `BREAKING CHANGE:` footer — tools won't detect body-only |\n| `feat(adding-auth): ...` | `feat(auth): ...` — scope is a noun, not a verb |\n| Closes #42 in subject line | Move to footer — keeps subject clean and parseable |\n\n## Best Practices\n\n- Align branch type and commit type — `feat\u002Fauth-*` branch → `feat(auth):` commits\n- One concern per branch — mixing fixes into feature branches obscures the changelog\n- Use scope consistently within a branch — `feat(auth):` throughout, not `feat(user):` mid-way\n- **Squash merge:** when squash-merging a PR\u002FMR, the branch commits are collapsed into one — the PR\u002FMR title becomes the commit message. If the title doesn't follow conventional commits format, changelog generation breaks silently. Always set the PR title before squashing.\n",{"name":5,"license":15,"metadata":24,"description":7,"allowed-tools":33,"compatibility":34,"user-invocable":35},{"author":25,"version":26,"openclaw":27},"samber","1.2.0",{"emoji":28,"homepage":29,"requires":30},"📝","https:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills",{"bins":31},[32],"git","Read Edit Write Glob Grep Bash(git:*) Bash(gh:*)","Designed for Claude Code or similar AI coding agents. Requires git.",true,"main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fsamber-cc-skills\u002Fconventional-git",1,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper","https:\u002F\u002Fgithub.com\u002Fom-scogo","SDE-1 @ Scogo ","2026-07-18 12:22:46",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":35},[46,49,52],{"tool":47,"command":48},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill conventional-git",{"tool":50,"command":51},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill conventional-git",{"tool":53,"command":54},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill conventional-git","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fsamber-cc-skills\u002Fconventional-git\u002FSkill.md",[57],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"metadata.json","REFERENCE","参考文档",429,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fsamber-cc-skills\u002Fconventional-git\u002Fmetadata.json",[64,71,76,83,88,95],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7D6MC9FAAEV4CMNYX8W7JTG","arxiv-search","Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002Fskills\u002Farxiv-search\u002FSKILL.md",[],[],{"skillNo":72,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7D4ZTCS4DR3CE4JY06X84T2","working-with-legacy-code","Safely change and test untested codebases using Feathers' \"Working Effectively with Legacy Code\". Use when the user mentions \"legacy code\", \"no tests\", \"untested codebase\", \"how do I test this\", \"seams\", \"characterization tests\", \"golden master\", \"sprout method\", \"afraid to change this code\", \"monster method\", \"dependency breaking\", or \"inherited a messy codebase\". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout\u002Fwrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002Fworking-with-legacy-code\u002FSKILL.md",[],[],{"skillNo":84,"name":78,"nameZh":6,"description":79,"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},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\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},"01M7D4ZB4CJBFW5JE67CPH2QRV","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", \"typographic scale\", or \"the text is hard to read\". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":96,"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":97,"categories":98,"keywords":99,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]