[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QJ00Y3MRRNMFCP7KSTP55Y":3,"skill-same:01M6QJ00Y3MRRNMFCP7KSTP55Y":66},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":28,"commitSha":48,"skillDirectory":49,"forksCount":13,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":52,"install":53,"resources":65},"01M6QJ00Y3MRRNMFCP7KSTP55Y","git-commit",null,"Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions \"\u002Fcommit\". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type\u002Fscope\u002Fdescription overrides, (4) Intelligent file staging for logical grouping","ImaginerLabs\u002Fskill-manager","ImaginerLabs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F214277308?v=4","01M6QGGDPNF15RMMT1RCFDH9FN","01M6QGGDTH5BY64DQ123NR8M33",0,"MIT","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fcoding\u002Fgit-commit\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"git commit","git","commit","diff","for","true","tree","detecting","scope","grouping","main","commit changes","auto","use","Bash","analysis","messages","file","commit message","copilot","2026-11-10 10:12:30",false,"---\nname: git-commit\ndescription: >-\n  Execute git commit with conventional commit message analysis, intelligent\n  staging, and message generation. Use when user asks to commit changes, create\n  a git commit, or mentions \"\u002Fcommit\". Supports: (1) Auto-detecting type and\n  scope from changes, (2) Generating conventional commit messages from diff, (3)\n  Interactive commit with optional type\u002Fscope\u002Fdescription overrides, (4)\n  Intelligent file staging for logical grouping\nlicense: MIT\nallowed-tools: Bash\nsource: awesome-copilot\nsourceUrl: \"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Ftree\u002Fmain\u002Fskills\u002Fgit-commit\"\nsourceRepo: \"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\"\nreadonly: true\ncategory: coding\n---\n\n# Git Commit with Conventional Commits\n\n## Overview\n\nCreate standardized, semantic git commits using the Conventional Commits specification. Analyze the actual diff to determine appropriate type, scope, and message.\n\n## Conventional Commit Format\n\n```\n\u003Ctype>[optional scope]: \u003Cdescription>\n\n[optional body]\n\n[optional footer(s)]\n```\n\n## Commit Types\n\n| Type       | Purpose                        |\n| ---------- | ------------------------------ |\n| `feat`     | New feature                    |\n| `fix`      | Bug fix                        |\n| `docs`     | Documentation only             |\n| `style`    | Formatting\u002Fstyle (no logic)    |\n| `refactor` | Code refactor (no feature\u002Ffix) |\n| `perf`     | Performance improvement        |\n| `test`     | Add\u002Fupdate tests               |\n| `build`    | Build system\u002Fdependencies      |\n| `ci`       | CI\u002Fconfig changes              |\n| `chore`    | Maintenance\u002Fmisc               |\n| `revert`   | Revert commit                  |\n\n## Breaking Changes\n\n```\n# Exclamation mark after type\u002Fscope\nfeat!: remove deprecated endpoint\n\n# BREAKING CHANGE footer\nfeat: allow config to extend other configs\n\nBREAKING CHANGE: `extends` key behavior changed\n```\n\n## Workflow\n\n### 1. Analyze Diff\n\n```bash\n# If files are staged, use staged diff\ngit diff --staged\n\n# If nothing staged, use working tree diff\ngit diff\n\n# Also check status\ngit status --porcelain\n```\n\n### 2. Stage Files (if needed)\n\nIf nothing is staged or you want to group changes differently:\n\n```bash\n# Stage specific files\ngit add path\u002Fto\u002Ffile1 path\u002Fto\u002Ffile2\n\n# Stage by pattern\ngit add *.test.*\ngit add src\u002Fcomponents\u002F*\n\n# Interactive staging\ngit add -p\n```\n\n**Never commit secrets** (.env, credentials.json, private keys).\n\n### 3. Generate Commit Message\n\nAnalyze the diff to determine:\n\n- **Type**: What kind of change is this?\n- **Scope**: What area\u002Fmodule is affected?\n- **Description**: One-line summary of what changed (present tense, imperative mood, \u003C72 chars)\n\n### 4. Execute Commit\n\n```bash\n# Single line\ngit commit -m \"\u003Ctype>[scope]: \u003Cdescription>\"\n\n# Multi-line with body\u002Ffooter\ngit commit -m \"$(cat \u003C\u003C'EOF'\n\u003Ctype>[scope]: \u003Cdescription>\n\n\u003Coptional body>\n\n\u003Coptional footer>\nEOF\n)\"\n```\n\n## Best Practices\n\n- One logical change per commit\n- Present tense: \"add\" not \"added\"\n- Imperative mood: \"fix bug\" not \"fixes bug\"\n- Reference issues: `Closes #123`, `Refs #456`\n- Keep description under 72 characters\n\n## Git Safety Protocol\n\n- NEVER update git config\n- NEVER run destructive commands (--force, hard reset) without explicit request\n- NEVER skip hooks (--no-verify) unless user asks\n- NEVER force push to main\u002Fmaster\n- If commit fails due to hooks, fix and create NEW commit (don't amend)\n","# Git Commit with Conventional Commits\n\n## Overview\n\nCreate standardized, semantic git commits using the Conventional Commits specification. Analyze the actual diff to determine appropriate type, scope, and message.\n\n## Conventional Commit Format\n\n```\n\u003Ctype>[optional scope]: \u003Cdescription>\n\n[optional body]\n\n[optional footer(s)]\n```\n\n## Commit Types\n\n| Type       | Purpose                        |\n| ---------- | ------------------------------ |\n| `feat`     | New feature                    |\n| `fix`      | Bug fix                        |\n| `docs`     | Documentation only             |\n| `style`    | Formatting\u002Fstyle (no logic)    |\n| `refactor` | Code refactor (no feature\u002Ffix) |\n| `perf`     | Performance improvement        |\n| `test`     | Add\u002Fupdate tests               |\n| `build`    | Build system\u002Fdependencies      |\n| `ci`       | CI\u002Fconfig changes              |\n| `chore`    | Maintenance\u002Fmisc               |\n| `revert`   | Revert commit                  |\n\n## Breaking Changes\n\n```\n# Exclamation mark after type\u002Fscope\nfeat!: remove deprecated endpoint\n\n# BREAKING CHANGE footer\nfeat: allow config to extend other configs\n\nBREAKING CHANGE: `extends` key behavior changed\n```\n\n## Workflow\n\n### 1. Analyze Diff\n\n```bash\n# If files are staged, use staged diff\ngit diff --staged\n\n# If nothing staged, use working tree diff\ngit diff\n\n# Also check status\ngit status --porcelain\n```\n\n### 2. Stage Files (if needed)\n\nIf nothing is staged or you want to group changes differently:\n\n```bash\n# Stage specific files\ngit add path\u002Fto\u002Ffile1 path\u002Fto\u002Ffile2\n\n# Stage by pattern\ngit add *.test.*\ngit add src\u002Fcomponents\u002F*\n\n# Interactive staging\ngit add -p\n```\n\n**Never commit secrets** (.env, credentials.json, private keys).\n\n### 3. Generate Commit Message\n\nAnalyze the diff to determine:\n\n- **Type**: What kind of change is this?\n- **Scope**: What area\u002Fmodule is affected?\n- **Description**: One-line summary of what changed (present tense, imperative mood, \u003C72 chars)\n\n### 4. Execute Commit\n\n```bash\n# Single line\ngit commit -m \"\u003Ctype>[scope]: \u003Cdescription>\"\n\n# Multi-line with body\u002Ffooter\ngit commit -m \"$(cat \u003C\u003C'EOF'\n\u003Ctype>[scope]: \u003Cdescription>\n\n\u003Coptional body>\n\n\u003Coptional footer>\nEOF\n)\"\n```\n\n## Best Practices\n\n- One logical change per commit\n- Present tense: \"add\" not \"added\"\n- Imperative mood: \"fix bug\" not \"fixes bug\"\n- Reference issues: `Closes #123`, `Refs #456`\n- Keep description under 72 characters\n\n## Git Safety Protocol\n\n- NEVER update git config\n- NEVER run destructive commands (--force, hard reset) without explicit request\n- NEVER skip hooks (--no-verify) unless user asks\n- NEVER force push to main\u002Fmaster\n- If commit fails due to hooks, fix and create NEW commit (don't amend)\n",{"name":5,"source":43,"license":14,"category":44,"readonly":45,"sourceUrl":46,"sourceRepo":47,"description":7,"allowed-tools":32},"awesome-copilot","coding",true,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Ftree\u002Fmain\u002Fskills\u002Fgit-commit","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot","b9a52d8e27455bdad953d64928696d028223ea1b","skills\u002Fcoding\u002Fgit-commit","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager","https:\u002F\u002Fgithub.com\u002FImaginerLabs","2026-04-18 16:27:13",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":45},[55,58,61],{"tool":56,"command":57},"npx","npx skills add ImaginerLabs\u002Fskill-manager --skill git-commit",{"tool":59,"command":60},"bunx","bunx skills add ImaginerLabs\u002Fskill-manager --skill git-commit",{"tool":62,"command":63},"pnpm","pnpm dlx skills add ImaginerLabs\u002Fskill-manager --skill git-commit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fcoding\u002Fgit-commit\u002FSKILL.md",[],[67,98,119,147,182,206],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":83,"publishedAt":38},"01M6QJCB2SD5KHC41ZDQC0GA1T","meeting-minutes","Generate concise, actionable meeting minutes for internal meetings. Includes metadata, attendees, agenda, decisions, action items (owner + due date), and follow-up steps.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fmeeting-minutes\u002FSKILL.md",[73,78],{"categoryNo":74,"categoryName":75,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":79,"categoryName":80,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[84,85,86,87,88,37,89,90,91,92,69,28,93,94,95,96,24,23,97,22],"meeting minutes","meeting","minutes","writing","github","generate","decisions","meetings","up","agenda","actionable","concise","follow-up","action",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":38},"01M6QJC71RRGTGNNFEHJG6S20G","documentation-writer","Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fdocumentation-writer\u002FSKILL.md",[],[105,106,107,87,88,37,108,109,110,111,112,113,28,114,115,116,117,24,23,118],"documentation","documentation writer","writer","https","quality","technical","technical writer","expert","documentation expert","structure","authoring","software","principles","high",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":132,"publishedAt":38},"01M6QJC0V3C7C4R9768J1AJYWY","doc-coauthoring","Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fdoc-coauthoring\u002FSKILL.md",[125,128,129],{"categoryNo":126,"categoryName":127,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":74,"categoryName":75,"taxonomyType":76,"taxonomyTypeDesc":77},{"categoryNo":130,"categoryName":131,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000036","内容创作者",[133,134,87,135,136,105,137,138,139,140,141,142,28,143,144,115,145,146,24,22],"doc coauthoring","doc","workflow","official","tasks","decision","write","context","proposals","guide","refine","iteration","trigger","co",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":163,"publishedAt":38},"01M6QJBJ0YPVEWGEXZH3PJRRTT","code-review-workflow","Executes comprehensive 4-phase code review: basic review, quality check, bundle analysis, and test coverage. Should be used when the user mentions comprehensive code review, checking code quality, or reviewing staged changes with multi-phase analysis. This is the comprehensive review workflow, distinct from focused skills like frontend-code-review, staged-code-review, or code-change-test-designer.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Ftesting\u002Fcode-review-workflow\u002FSKILL.md",[153,156,159,160],{"categoryNo":154,"categoryName":155,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":157,"categoryName":158,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":74,"categoryName":75,"taxonomyType":76,"taxonomyTypeDesc":77},{"categoryNo":161,"categoryName":162,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000030","开发工程师",[164,165,135,166,167,168,169,170,171,172,173,33,174,175,176,177,178,179,180,181],"code review","review","code","code review workflow","testing","frontend","test","change","code quality","code-review","check","coverage","quality check","basic","multi","comprehensive code review","with","phase",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":197,"publishedAt":38},"01M6QJB7XNHV3VEEQF4W7FMWF6","code-change-test-designer","Analyzes code changes and designs comprehensive test cases. Reads diffs, summarizes capability changes, and designs test cases covering main flows and edge cases. Should be used when the user mentions test coverage, designing tests for code changes, or analyzing diff\u002Fcommit for testing purposes. Distinguished from code-review-workflow which provides comprehensive review, this skill focuses on test case design for code changes.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Ftesting\u002Fcode-change-test-designer\u002FSKILL.md",[188,189,192,193,194],{"categoryNo":157,"categoryName":158,"taxonomyType":76,"taxonomyTypeDesc":77},{"categoryNo":190,"categoryName":191,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":74,"categoryName":75,"taxonomyType":76,"taxonomyTypeDesc":77},{"categoryNo":161,"categoryName":162,"taxonomyType":81,"taxonomyTypeDesc":82},{"categoryNo":195,"categoryName":196,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000032","设计师",[170,171,166,198,199,168,200,201,135,20,173,202,175,21,28,203,204,205,22,181],"designer","code change test designer","design","diffs","edge","tests","flows","which",{"skillNo":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":210,"categories":211,"keywords":213,"publishedAt":38},"01M6QJB195WD7DCJWDMKWKB29S","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fmeta-skills\u002Fskill-creator\u002FSKILL.md",[212],{"categoryNo":74,"categoryName":75,"taxonomyType":76,"taxonomyTypeDesc":77},[214,215,216,217,136,218,219,220,221,222,33,223,224,225,28,226,227,24,22,208],"skill creator","creator","performance","run evals","variance analysis","create","run","benchmark","Meta","improve","edit","evals","optimize","existing skill"]