[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DWH2Z36WV3RZBKM9JB0ETE":3,"skill-same:01M6DWH2Z36WV3RZBKM9JB0ETE":78},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M6DWH2Z36WV3RZBKM9JB0ETE","git-workflow",null,"Git commit message conventions, branch naming and clean-history workflow. Use when committing, branching, rebasing, tagging or reviewing git history.","Muvon\u002Foctomind-tap","Muvon","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F25336907?v=4","01M6DWA4KTRX4J73CW5CECKAD0","01M6DWA4QSWFGYE6WDMAMFF1WE",6,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FMuvon\u002Foctomind-tap\u002Fblob\u002Fmaster\u002Fskills\u002Fgit-workflow\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"git workflow","git","workflow","tagging","with","use","branching","when","file","commit message","git commit","commits","history","developer","versioning","message","commit","branches","clean","project","branch","2026-11-10 10:12:30",false,"---\nname: git-workflow\ntitle: \"Git Workflow: Commits, Branches, Rebasing\"\ndescription: \"Git commit message conventions, branch naming and clean-history workflow. Use when committing, branching, rebasing, tagging or reviewing git history.\"\nlicense: Apache-2.0\ncompatibility: \"Requires git. Works with any git-based project.\"\ncapabilities: versioning\ndomains: developer devops\nrules:\n  - file(.git)\n---\n\n## Overview\n\nThis skill encodes git commit conventions (Conventional Commits), branch naming rules, and workflow best practices. Activate it when you need to commit changes, name a branch, clean up history, or review git practices in a project.\n\n## Instructions\n\n### Commit Message Format\n\nFollow [Conventional Commits 1.0.0](https:\u002F\u002Fwww.conventionalcommits.org\u002Fen\u002Fv1.0.0\u002F):\n\n```\n\u003Ctype>(\u003Cscope>): \u003Cshort summary>\n\n[optional body]\n\n[optional footer]\n```\n\nTypes: the spec itself defines only `feat` (maps to a SemVer MINOR) and `fix` (PATCH). The common extended set comes from commitlint's `config-conventional`:\n- `feat` — new feature\n- `fix` — bug fix\n- `refactor` — code change that neither fixes a bug nor adds a feature\n- `perf` — performance improvement\n- `test` — adding or updating tests\n- `docs` — documentation only\n- `style` — formatting, no behavior change\n- `build` — build system or dependencies\n- `ci` — CI\u002FCD changes\n- `chore` — other maintenance\n- `revert` — reverts a previous commit\n\nIf the repo already enforces a type list (commitlint config, CONTRIBUTING), that list wins.\n\nBreaking changes (MAJOR): add `!` right before the colon — `feat(api)!: drop v1 endpoints` — and\u002For a footer `BREAKING CHANGE: \u003Cwhat breaks and how to migrate>`. The footer token is uppercase; `BREAKING-CHANGE` is equivalent.\n\nRules:\n- Summary line: imperative mood (\"add\" not \"added\"), aim for ~50 characters, hard limit 72\n- No period at end of summary\n- Body: wrap at 72 characters, explain why not what\n- Footers use `Token: value` with hyphenated tokens (`Reviewed-by:`, `Co-authored-by:`, `Signed-off-by:`); reference issues as `Fixes #123` \u002F `Closes #456` so the forge auto-closes them\n\n### Branch Naming\n\n```\n\u003Ctype>\u002F\u003Cshort-description>\n```\n\n- `feat\u002Fuser-profile-page`\n- `fix\u002Flogin-redirect-loop`\n- `refactor\u002Fextract-auth-middleware`\n- `chore\u002Fupgrade-tokio-1.47`\n\nUse kebab-case. Keep it short but descriptive. Match the commit type.\n\n### Workflow Rules\n\n1. Never commit directly to `main` — always use a short-lived branch\n2. Keep commits atomic — one logical change per commit\n3. Update your branch by rebasing onto the fresh remote: `git fetch origin && git rebase origin\u002Fmain`. Rebase only branches nobody else has built on\n4. After rewriting a pushed branch, push with `git push --force-with-lease --force-if-includes` — never plain `--force`\n5. Clean up before opening a PR: make corrections as `git commit --fixup=\u003Csha>`, then fold them with `git rebase --autosquash origin\u002Fmain` (Git 2.44+ applies autosquash without `-i`, so it runs non-interactively)\n6. Stacked branches: `git rebase --update-refs` moves every branch in the stack in one pass\n7. Tag releases with semantic versioning (`v1.2.3`), annotated (`-a`) or signed (`-s`)\n\n## Examples\n\n### Good commit message\n\n```\nfeat(auth): add JWT refresh token rotation\n\nPrevents token reuse after logout by invalidating the previous\nrefresh token on each use.\n\nCloses #89\n```\n\n### Bad commit message → fix it\n\n```\n# Bad\nfixed stuff\nupdate\nWIP\n```\n\n```\n# Good\nfix(api): handle empty response body in error parser\n\nThe parser panicked when the server returned a 500 with no body.\nAdded a fallback to use the status text instead.\n```\n\n### Common commands\n\n```bash\n# Start a feature (git switch replaces checkout for branches)\ngit switch -c feat\u002Fmy-feature\n\n# Stage only relevant changes (interactive; agents stage explicit paths instead)\ngit add -p\n\n# Amend last commit (before push)\ngit commit --amend --no-edit\n\n# Fix an earlier commit, then fold it in without an editor\ngit commit --fixup=\u003Csha>\ngit rebase --autosquash origin\u002Fmain\n\n# Check what will be committed\ngit diff --staged\n\n# Tag a release\ngit tag -a v1.2.3 -m \"Release v1.2.3\"\ngit push origin v1.2.3\n```\n\n## References\n\n- [Conventional Commits 1.0.0](https:\u002F\u002Fwww.conventionalcommits.org\u002Fen\u002Fv1.0.0\u002F)\n- [Semantic Versioning 2.0.0](https:\u002F\u002Fsemver.org\u002F)\n- [git-rebase documentation](https:\u002F\u002Fgit-scm.com\u002Fdocs\u002Fgit-rebase)\n","## Overview\n\nThis skill encodes git commit conventions (Conventional Commits), branch naming rules, and workflow best practices. Activate it when you need to commit changes, name a branch, clean up history, or review git practices in a project.\n\n## Instructions\n\n### Commit Message Format\n\nFollow [Conventional Commits 1.0.0](https:\u002F\u002Fwww.conventionalcommits.org\u002Fen\u002Fv1.0.0\u002F):\n\n```\n\u003Ctype>(\u003Cscope>): \u003Cshort summary>\n\n[optional body]\n\n[optional footer]\n```\n\nTypes: the spec itself defines only `feat` (maps to a SemVer MINOR) and `fix` (PATCH). The common extended set comes from commitlint's `config-conventional`:\n- `feat` — new feature\n- `fix` — bug fix\n- `refactor` — code change that neither fixes a bug nor adds a feature\n- `perf` — performance improvement\n- `test` — adding or updating tests\n- `docs` — documentation only\n- `style` — formatting, no behavior change\n- `build` — build system or dependencies\n- `ci` — CI\u002FCD changes\n- `chore` — other maintenance\n- `revert` — reverts a previous commit\n\nIf the repo already enforces a type list (commitlint config, CONTRIBUTING), that list wins.\n\nBreaking changes (MAJOR): add `!` right before the colon — `feat(api)!: drop v1 endpoints` — and\u002For a footer `BREAKING CHANGE: \u003Cwhat breaks and how to migrate>`. The footer token is uppercase; `BREAKING-CHANGE` is equivalent.\n\nRules:\n- Summary line: imperative mood (\"add\" not \"added\"), aim for ~50 characters, hard limit 72\n- No period at end of summary\n- Body: wrap at 72 characters, explain why not what\n- Footers use `Token: value` with hyphenated tokens (`Reviewed-by:`, `Co-authored-by:`, `Signed-off-by:`); reference issues as `Fixes #123` \u002F `Closes #456` so the forge auto-closes them\n\n### Branch Naming\n\n```\n\u003Ctype>\u002F\u003Cshort-description>\n```\n\n- `feat\u002Fuser-profile-page`\n- `fix\u002Flogin-redirect-loop`\n- `refactor\u002Fextract-auth-middleware`\n- `chore\u002Fupgrade-tokio-1.47`\n\nUse kebab-case. Keep it short but descriptive. Match the commit type.\n\n### Workflow Rules\n\n1. Never commit directly to `main` — always use a short-lived branch\n2. Keep commits atomic — one logical change per commit\n3. Update your branch by rebasing onto the fresh remote: `git fetch origin && git rebase origin\u002Fmain`. Rebase only branches nobody else has built on\n4. After rewriting a pushed branch, push with `git push --force-with-lease --force-if-includes` — never plain `--force`\n5. Clean up before opening a PR: make corrections as `git commit --fixup=\u003Csha>`, then fold them with `git rebase --autosquash origin\u002Fmain` (Git 2.44+ applies autosquash without `-i`, so it runs non-interactively)\n6. Stacked branches: `git rebase --update-refs` moves every branch in the stack in one pass\n7. Tag releases with semantic versioning (`v1.2.3`), annotated (`-a`) or signed (`-s`)\n\n## Examples\n\n### Good commit message\n\n```\nfeat(auth): add JWT refresh token rotation\n\nPrevents token reuse after logout by invalidating the previous\nrefresh token on each use.\n\nCloses #89\n```\n\n### Bad commit message → fix it\n\n```\n# Bad\nfixed stuff\nupdate\nWIP\n```\n\n```\n# Good\nfix(api): handle empty response body in error parser\n\nThe parser panicked when the server returned a 500 with no body.\nAdded a fallback to use the status text instead.\n```\n\n### Common commands\n\n```bash\n# Start a feature (git switch replaces checkout for branches)\ngit switch -c feat\u002Fmy-feature\n\n# Stage only relevant changes (interactive; agents stage explicit paths instead)\ngit add -p\n\n# Amend last commit (before push)\ngit commit --amend --no-edit\n\n# Fix an earlier commit, then fold it in without an editor\ngit commit --fixup=\u003Csha>\ngit rebase --autosquash origin\u002Fmain\n\n# Check what will be committed\ngit diff --staged\n\n# Tag a release\ngit tag -a v1.2.3 -m \"Release v1.2.3\"\ngit push origin v1.2.3\n```\n\n## References\n\n- [Conventional Commits 1.0.0](https:\u002F\u002Fwww.conventionalcommits.org\u002Fen\u002Fv1.0.0\u002F)\n- [Semantic Versioning 2.0.0](https:\u002F\u002Fsemver.org\u002F)\n- [git-rebase documentation](https:\u002F\u002Fgit-scm.com\u002Fdocs\u002Fgit-rebase)\n",{"name":5,"rules":49,"title":51,"domains":52,"license":14,"description":7,"capabilities":37,"compatibility":53},[50],"file(.git)","Git Workflow: Commits, Branches, Rebasing","developer devops","Requires git. Works with any git-based project.","master","e9e4a19559669b1627b1ac5ed3f77b8e36cfad95","skills\u002Fgit-workflow",0,"https:\u002F\u002Fgithub.com\u002FMuvon\u002Foctomind-tap","https:\u002F\u002Foctomind.run\u002Ftap\u002F","https:\u002F\u002Fgithub.com\u002FMuvon","https:\u002F\u002Fmuvon.io","We bring ideas to life","2026-11-14 13:21:16",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add Muvon\u002Foctomind-tap --skill git-workflow",{"tool":70,"command":71},"bunx","bunx skills add Muvon\u002Foctomind-tap --skill git-workflow",{"tool":73,"command":74},"pnpm","pnpm dlx skills add Muvon\u002Foctomind-tap --skill git-workflow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMuvon\u002Foctomind-tap\u002Fblob\u002Fmaster\u002Fskills\u002Fgit-workflow\u002FSKILL.md",true,[],[79,117,144,164,188,212],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":96,"publishedAt":44},"01M70SFC5CTHRKA9B97N1ARVZ2","seo-content-refresh","Finds decaying pages, picks update, merge, redirect or remove, and briefs each refresh. Use to prioritize existing content and judge whether it helped.","https:\u002F\u002Fgithub.com\u002FMuvon\u002Foctomind-tap\u002Fblob\u002Fmaster\u002Fskills\u002Fseo-content-refresh\u002FSKILL.md",[85,88,93],{"categoryNo":86,"categoryName":87,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",{"categoryNo":94,"categoryName":95,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000036","内容创作者",[97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116],"seo content refresh","seo","seo content","content refresh","refresh","content","posts","remove","web search","performance","search","traffic","access","drop","websearch","revamp","merge","diagnosis","update","decay",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":125,"publishedAt":44},"01M70SBWQCHGH7HGS51Y0GTKKW","marketing-review-program","Plans how to ask real customers for honest public reviews: site choice, invitation copy, incentive and disclosure rules. Use to start a review program.","https:\u002F\u002Fgithub.com\u002FMuvon\u002Foctomind-tap\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketing-review-program\u002FSKILL.md",[123,124],{"categoryNo":86,"categoryName":87,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},[126,127,128,129,130,131,105,107,132,133,134,135,136,137,138,139,140,141,142,143],"program","review","marketing review program","marketing","reviews","get","campaign","choice","how to","only","generated","ask","plan","product","generate","customer","how","request",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":44},"01M70SBB65Z2FC71Q7DEAXGJBG","geo-source-actions","Turns AI citation findings into ranked per-source actions for Reddit threads, listicles, review sites and videos. Records only. Use after a GEO audit.","https:\u002F\u002Fgithub.com\u002FMuvon\u002Foctomind-tap\u002Fblob\u002Fmaster\u002Fskills\u002Fgeo-source-actions\u002FSKILL.md",[],[151,152,153,154,155,131,105,107,156,157,135,111,127,158,159,160,139,161,162,163],"actions","geo source actions","source","geo","sources","copilot","domains","llms","threads","youtube","audit","action","data",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":173,"publishedAt":44},"01M70S99D3Y6GF097GTXWBXHPW","commerce-ai-readiness","Audits product feeds, markup and live pages for AI shopping assistants, then lists exact fixes. Use to make a store catalog readable to AI shoppers.","https:\u002F\u002Fgithub.com\u002FMuvon\u002Foctomind-tap\u002Fblob\u002Fmaster\u002Fskills\u002Fcommerce-ai-readiness\u002FSKILL.md",[170],{"categoryNo":171,"categoryName":172,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000031","产品经理",[174,175,176,177,178,179,180,181,182,183,107,184,156,135,109,185,186,139,161,187],"ai readiness","commerce ai readiness","commerce","readiness","feeds","ready","show","shopping","discover","checkout","up","ecommerce","documentation","recommend",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":195,"publishedAt":44},"01M6DWSX45J42KTK6XASKJRGPA","tap-model-training","Train, evaluate and publish the octomind-embed model behind capability auto-activation. Use when capability triggers or skill semantic() phrases change.","https:\u002F\u002Fgithub.com\u002FMuvon\u002Foctomind-tap\u002Fblob\u002Fmaster\u002Fskills\u002Ftap-model-training\u002FSKILL.md",[194],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[196,197,198,199,200,184,201,202,203,204,205,206,207,208,209,142,210,211,30,115],"model","training","tap","tap model training","scope","eval","uv","auto","dataset","activate","api","capabilities","publish","change","embedding","re",{"skillNo":213,"name":214,"nameZh":6,"description":215,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":216,"categories":217,"keywords":219,"publishedAt":44},"01M6DWSQB7NSW53Z86XM81R1W1","tap-deps-authoring","Write dep scripts for the octomind-tap registry: header comments, platform.sh, mcp vs dep types, npx\u002Fuvx pattern. Use when editing deps\u002F\u003Corg>\u002F\u003Ctool>.sh.","https:\u002F\u002Fgithub.com\u002FMuvon\u002Foctomind-tap\u002Fblob\u002Fmaster\u002Fskills\u002Ftap-deps-authoring\u002FSKILL.md",[218],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[220,198,221,222,223,224,225,226,227,228,229,230,231,232,233,234,30,235,236,237],"deps","tap deps authoring","authoring","DEP","MCP","run","scripts","pattern","install","registry","platform","repo","editing","tool","types","write","org","for"]