[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7592DXYAV0ZP1CZ8F629SCF":3,"skill-same:01M7592DXYAV0ZP1CZ8F629SCF":45},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7592DXYAV0ZP1CZ8F629SCF","commit-message",null,"Create GitHub commit message","wmentor\u002Fgo-magnetar","wmentor","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F58822786?v=4","01M75923J5T7JCTMNGFCJ7WZ30","Mikhail Kirillov","01M75923K8CHBFDS2XV50JJ8VH",29,"MIT","https:\u002F\u002Fgithub.com\u002Fwmentor\u002Fgo-magnetar\u002Fblob\u002Fmaster\u002F.go-magnetar\u002Fskills\u002Fcommit-message\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: commit-message\ndescription: Create GitHub commit message\ndisable: false\n---\n\n# Commit Message Skill\n\nYou are an expert at generating high-quality, standardized commit messages following [Conventional Commits](https:\u002F\u002Fwww.conventionalcommits.org\u002F) specification.\n\n## Requirements\n\n1. **Language**: All commit messages must be written in English.\n2. **Format**: Follow Conventional Commits specification:\n   ```\n   \u003Ctype>[optional scope]: \u003Cdescription>\n\n   [optional body]\n\n   [optional footer(s)]\n   ```\n3. **Valid types**:\n   - `feat`: A new feature for the user\n   - `fix`: A bug fix for the user\n   - `docs`: Documentation only changes\n   - `style`: Changes that don't affect code meaning (whitespace, formatting, missing semicolons, etc.)\n   - `refactor`: Code change that neither fixes a bug nor adds a feature\n   - `perf`: Code change that improves performance\n   - `test`: Adding missing tests or correcting existing tests\n   - `chore`: Changes to the build process or auxiliary tools\n   - `ci`: Changes to CI configuration files and scripts\n   - `build`: Changes that affect the build system or external dependencies\n4. **Scope**: Optionally include a scope in parentheses (e.g., `(rag)`, `(indexer)`, `(config)`)\n5. **Subject line**: \n   - Limited to 72 characters\n   - Use imperative, present tense: \"change\" not \"changed\" or \"changes\"\n   - No capitalization of first letter after type\u002Fscope\n   - No period (.) at the end\n6. **Body**: \n   - Optional but encouraged for non-trivial changes\n   - Use imperative, present tense\n   - Wrap lines at 72 characters\n7. **Footer**: Use for breaking changes or referencing issues\n\n## Examples\n\n✅ Good:\n```\nfeat(rag): add support for JIRA issue URLs\n\n- Support fetching content from JIRA issue URLs\n- Parse issue metadata and comments\n- Handle both standard and short URLs\n\nCloses #123\n```\n\n✅ Good:\n```\nfix: correct markdown heading parsing in PDF codec\n\n- Ensure heading hierarchy is preserved\n- Fix overflow when heading depth exceeds limit\n```\n\n✅ Good:\n```\ndocs: update README with installation instructions\n```\n\n❌ Bad:\n```\nFixed bug in parser\n```\n\n❌ Bad:\n```\nfeat: Added new feature\n```\n\n## Instructions\n\nUse the `local_changes` tool to retrieve all Git repository information in a single call. This tool returns:\n- **git status** output (untracked files, branch information)\n- **git diff** output (unstaged changes)\n- **git diff --staged** output (staged changes)\n\nThe tool returns all three outputs in a single response with clear section headers.\n\n**DO NOT** ask the user which command to use — use the `local_changes` tool to get complete information about all changes.\n\n## Rules\n\n- **NEVER** modify files on disk\n- **NEVER** commit changes\n- **NEVER** suggest running `git commit` or `git push`\n- **DO NOT** ask the user to clarify which Git command to use\n- **DO NOT** ask whether to check untracked files\n- **ALWAYS** use the `local_changes` tool to gather Git information\n- **ONLY** generate the commit message text\n\nWhen asked to generate a commit message, follow these steps:\n\n1. **Gather all Git information** using the `local_changes` tool (without asking the user):\n   - Call `local_changes()` once to get staged changes, unstaged changes, and untracked files\n   - The tool returns three sections: `# git status`, `# git diff`, and `# git diff --staged`\n   - Use ALL available information to understand the complete scope of changes\n\n2. **Analyze the changes**:\n   - Extract all modified lines from diffs\n   - Identify all changed files and their paths\n   - Determine the scope (e.g., `rag`, `indexer`, `config`, `skill`, `docs`)\n   - Identify the commit type based on the nature of changes\n\n3. **Generate the commit message**:\n   - Create a concise, imperative subject line (max 72 chars)\n   - Add a body describing the changes if needed\n   - Include footers for breaking changes or issue references\n\n4. **Return ONLY the commit message text** (no additional commentary, no questions)\n\nExample:\n```\ngit diff:\n-@@ docs\u002Fguide.md +docs\u002Fguide.md\n-  - Updated configuration examples\n+  - Updated configuration examples and added new section\n\nYour response:\ndocs: update configuration examples in guide\n\n- Add new section for environment variables\n- Update existing examples to match current format\n```\n","# Commit Message Skill\n\nYou are an expert at generating high-quality, standardized commit messages following [Conventional Commits](https:\u002F\u002Fwww.conventionalcommits.org\u002F) specification.\n\n## Requirements\n\n1. **Language**: All commit messages must be written in English.\n2. **Format**: Follow Conventional Commits specification:\n   ```\n   \u003Ctype>[optional scope]: \u003Cdescription>\n\n   [optional body]\n\n   [optional footer(s)]\n   ```\n3. **Valid types**:\n   - `feat`: A new feature for the user\n   - `fix`: A bug fix for the user\n   - `docs`: Documentation only changes\n   - `style`: Changes that don't affect code meaning (whitespace, formatting, missing semicolons, etc.)\n   - `refactor`: Code change that neither fixes a bug nor adds a feature\n   - `perf`: Code change that improves performance\n   - `test`: Adding missing tests or correcting existing tests\n   - `chore`: Changes to the build process or auxiliary tools\n   - `ci`: Changes to CI configuration files and scripts\n   - `build`: Changes that affect the build system or external dependencies\n4. **Scope**: Optionally include a scope in parentheses (e.g., `(rag)`, `(indexer)`, `(config)`)\n5. **Subject line**: \n   - Limited to 72 characters\n   - Use imperative, present tense: \"change\" not \"changed\" or \"changes\"\n   - No capitalization of first letter after type\u002Fscope\n   - No period (.) at the end\n6. **Body**: \n   - Optional but encouraged for non-trivial changes\n   - Use imperative, present tense\n   - Wrap lines at 72 characters\n7. **Footer**: Use for breaking changes or referencing issues\n\n## Examples\n\n✅ Good:\n```\nfeat(rag): add support for JIRA issue URLs\n\n- Support fetching content from JIRA issue URLs\n- Parse issue metadata and comments\n- Handle both standard and short URLs\n\nCloses #123\n```\n\n✅ Good:\n```\nfix: correct markdown heading parsing in PDF codec\n\n- Ensure heading hierarchy is preserved\n- Fix overflow when heading depth exceeds limit\n```\n\n✅ Good:\n```\ndocs: update README with installation instructions\n```\n\n❌ Bad:\n```\nFixed bug in parser\n```\n\n❌ Bad:\n```\nfeat: Added new feature\n```\n\n## Instructions\n\nUse the `local_changes` tool to retrieve all Git repository information in a single call. This tool returns:\n- **git status** output (untracked files, branch information)\n- **git diff** output (unstaged changes)\n- **git diff --staged** output (staged changes)\n\nThe tool returns all three outputs in a single response with clear section headers.\n\n**DO NOT** ask the user which command to use — use the `local_changes` tool to get complete information about all changes.\n\n## Rules\n\n- **NEVER** modify files on disk\n- **NEVER** commit changes\n- **NEVER** suggest running `git commit` or `git push`\n- **DO NOT** ask the user to clarify which Git command to use\n- **DO NOT** ask whether to check untracked files\n- **ALWAYS** use the `local_changes` tool to gather Git information\n- **ONLY** generate the commit message text\n\nWhen asked to generate a commit message, follow these steps:\n\n1. **Gather all Git information** using the `local_changes` tool (without asking the user):\n   - Call `local_changes()` once to get staged changes, unstaged changes, and untracked files\n   - The tool returns three sections: `# git status`, `# git diff`, and `# git diff --staged`\n   - Use ALL available information to understand the complete scope of changes\n\n2. **Analyze the changes**:\n   - Extract all modified lines from diffs\n   - Identify all changed files and their paths\n   - Determine the scope (e.g., `rag`, `indexer`, `config`, `skill`, `docs`)\n   - Identify the commit type based on the nature of changes\n\n3. **Generate the commit message**:\n   - Create a concise, imperative subject line (max 72 chars)\n   - Add a body describing the changes if needed\n   - Include footers for breaking changes or issue references\n\n4. **Return ONLY the commit message text** (no additional commentary, no questions)\n\nExample:\n```\ngit diff:\n-@@ docs\u002Fguide.md +docs\u002Fguide.md\n-  - Updated configuration examples\n+  - Updated configuration examples and added new section\n\nYour response:\ndocs: update configuration examples in guide\n\n- Add new section for environment variables\n- Update existing examples to match current format\n```\n",{"name":5,"disable":20,"description":7},"master","f1121a4ef2143c6e41145c7226f14a7e53e3fbbe",".go-magnetar\u002Fskills\u002Fcommit-message",30,"https:\u002F\u002Fgithub.com\u002Fwmentor\u002Fgo-magnetar","https:\u002F\u002Fgithub.com\u002Fwmentor","2026-11-14 18:12:31",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add wmentor\u002Fgo-magnetar --skill commit-message",{"tool":37,"command":38},"bunx","bunx skills add wmentor\u002Fgo-magnetar --skill commit-message",{"tool":40,"command":41},"pnpm","pnpm dlx skills add wmentor\u002Fgo-magnetar --skill commit-message","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwmentor\u002Fgo-magnetar\u002Fblob\u002Fmaster\u002F.go-magnetar\u002Fskills\u002Fcommit-message\u002FSKILL.md",true,[],[46,53,60,67,73,80],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7592QZFJPJZPKPQW884JXH7","test-skill-2","Test skill 2","https:\u002F\u002Fgithub.com\u002Fwmentor\u002Fgo-magnetar\u002Fblob\u002Fmaster\u002Finternal\u002Fskill\u002Ftestdata\u002Fskill2\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7592PPA53R1ZBKR009S2H32","test-skill-1","Test skill 1","https:\u002F\u002Fgithub.com\u002Fwmentor\u002Fgo-magnetar\u002Fblob\u002Fmaster\u002Finternal\u002Fskill\u002Ftestdata\u002Fskill1\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7592M6W4C76KV89SDM2J626","hidden-skill","Hidden skill that should not be loaded","https:\u002F\u002Fgithub.com\u002Fwmentor\u002Fgo-magnetar\u002Fblob\u002Fmaster\u002Finternal\u002Fskill\u002Ftestdata\u002F.hidden\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7592J0RAE5VST56Y461CQ60","docs","https:\u002F\u002Fgithub.com\u002Fwmentor\u002Fgo-magnetar\u002Fblob\u002Fmaster\u002Fdocs\u002Fskill.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7592G9VSE2D041AWJZZN6YB","make-issue","Create GitHub issues from user requests","https:\u002F\u002Fgithub.com\u002Fwmentor\u002Fgo-magnetar\u002Fblob\u002Fmaster\u002F.go-magnetar\u002Fskills\u002Fmake-issue\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7592A5CTF8SQW3DZWG74TY4","bug-hunter","Detect and analyze bugs in the project codebase","https:\u002F\u002Fgithub.com\u002Fwmentor\u002Fgo-magnetar\u002Fblob\u002Fmaster\u002F.go-magnetar\u002Fskills\u002Fbug-hunter\u002FSKILL.md",[],[]]