[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6K498R827T73HC9PH8Z0FD2":3,"skill-same:01M6K498R827T73HC9PH8Z0FD2":64},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":14,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M6K498R827T73HC9PH8Z0FD2","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","jan-guenter\u002Fsquid4win","jan-guenter","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10003091?v=4","01M6K46F086GAGX6T722TGJKB8","Jan Günter","01M6K46F43A3RXTQCJ0W8QGFE7",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjan-guenter\u002Fsquid4win\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgit-commit\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"git commit","commit","git","for","detecting","with","scope","type","grouping","commit changes","auto","diff","use","interactive","Bash","analysis","messages","file","commit message","create","2026-11-10 10:12:30",false,"---\nname: git-commit\ndescription: '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'\nlicense: MIT\nallowed-tools: Bash\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,"license":15,"description":7,"allowed-tools":33},"main","888717890170acc3250618f7e7ac4a85f7e0994e",".agents\u002Fskills\u002Fgit-commit","https:\u002F\u002Fgithub.com\u002Fjan-guenter\u002Fsquid4win","https:\u002F\u002Fgithub.com\u002Fjan-guenter","2026-06-29 12:16:03",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add jan-guenter\u002Fsquid4win --skill git-commit",{"tool":56,"command":57},"bunx","bunx skills add jan-guenter\u002Fsquid4win --skill git-commit",{"tool":59,"command":60},"pnpm","pnpm dlx skills add jan-guenter\u002Fsquid4win --skill git-commit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjan-guenter\u002Fsquid4win\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgit-commit\u002FSKILL.md",true,[],[65,96,125,150,181,205],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":79,"publishedAt":39},"01M6K4B4JB6DEMDW6NMRNSG1T6","refactor","Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.","https:\u002F\u002Fgithub.com\u002Fjan-guenter\u002Fsquid4win\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frefactor\u002FSKILL.md",[71,76],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":77,"categoryName":78,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000015","视觉设计",[67,80,81,82,83,84,85,86,87,31,88,89,90,91,92,26,93,94,22,95],"design","code","Type Safety","Safety","improve","refactoring","repo","behavior","design patterns","code refactoring","functions","patterns","maintainability","extracting","Variables","down",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":107,"publishedAt":39},"01M6K4ANBZFRXQA3WFYG3WSRHS","prd","Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.","https:\u002F\u002Fgithub.com\u002Fjan-guenter\u002Fsquid4win\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fprd\u002FSKILL.md",[102],{"categoryNo":103,"categoryName":104,"taxonomyType":105,"taxonomyTypeDesc":106},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[98,108,109,110,111,112,34,113,114,115,116,117,118,119,120,121,22,122,123,124],"documents","risk analysis","generate","product","risk","quality","technical","requirements","systems","software","Product Requirements","specifications","user stories","high","summaries","features","stories",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":135,"publishedAt":39},"01M6K482WB93YH1TDJ2KJJPHWK","design-documentation","Transform approved requirements into comprehensive technical designs. Define system architecture, component interactions, data models, and interfaces to create a blueprint for implementation.","https:\u002F\u002Fgithub.com\u002Fjan-guenter\u002Fsquid4win\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdesign-documentation\u002FSKILL.md",[131,132],{"categoryNo":77,"categoryName":78,"taxonomyType":74,"taxonomyTypeDesc":75},{"categoryNo":133,"categoryName":134,"taxonomyType":105,"taxonomyTypeDesc":106},"01JBSEEDCAT000000000000032","设计师",[80,136,137,138,139,38,81,140,141,142,114,143,144,145,146,147,115,148,149,22],"documentation","design documentation","component","architecture","data","team","system","cursor","Blueprint","models","windsurf","kiro","define","transform",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":162,"publishedAt":39},"01M6K47SB3HCWXWV5FQW6K1H58","csharp-developer","Use when building C# applications with .NET 8+, ASP.NET Core APIs, or Blazor web apps. Builds REST APIs using minimal or controller-based routing, configures database access with Entity Framework Core, implements async patterns and cancellation, structures applications with CQRS via MediatR, and scaffolds Blazor components with state management. Invoke for C#, .NET, ASP.NET Core, Blazor, Entity Framework, EF Core, Minimal API, MAUI, SignalR.","https:\u002F\u002Fgithub.com\u002Fjan-guenter\u002Fsquid4win\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcsharp-developer\u002FSKILL.md",[156,159],{"categoryNo":157,"categoryName":158,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":160,"categoryName":161,"taxonomyType":105,"taxonomyTypeDesc":106},"01JBSEEDCAT000000000000030","开发工程师",[163,164,165,166,167,81,168,169,170,171,172,173,174,175,176,177,91,178,179,180],"csharp","developer","csharp developer","components","core","blazor","framework","database","ef core","controller","api","access","designer","framework core","engineer","optimizer","apps","signalr",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":188,"publishedAt":39},"01M6K47EBZVG4DH2NN0TTCW44R","cpp-pro","Writes, optimizes, and debugs C++ applications using modern C++20\u002F23 features, template metaprogramming, and high-performance systems techniques. Use when building or refactoring C++ code requiring concepts, ranges, coroutines, SIMD optimization, or careful memory management — or when addressing performance bottlenecks, concurrency issues, and build system configuration with CMake.","https:\u002F\u002Fgithub.com\u002Fjan-guenter\u002Fsquid4win\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcpp-pro\u002FSKILL.md",[187],{"categoryNo":160,"categoryName":161,"taxonomyType":105,"taxonomyTypeDesc":106},[189,190,191,192,193,194,195,81,196,197,198,199,200,85,201,177,202,203,204,123],"cpp","cpp pro","pro","memory","performance","rust","cmake","issues","metaprogramming","concurrency","embedded-systems","careful","template","c++","high-performance","concepts",{"skillNo":206,"name":207,"nameZh":6,"description":208,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":209,"categories":210,"keywords":213,"publishedAt":39},"01M6K46XD4YD1NR28VNB79DQJB","code-review","Guide for making code reviews. Use this when asked to make code reviews, or ask to use it before committing changes.","https:\u002F\u002Fgithub.com\u002Fjan-guenter\u002Fsquid4win\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcode-review\u002FSKILL.md",[211,212],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},{"categoryNo":160,"categoryName":161,"taxonomyType":105,"taxonomyTypeDesc":106},[214,215,81,216,217,31,218,219,220,22,221],"code review","review","ask","guide","it","make","reviews","changes"]