[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C1204QJSQ8HS0ZP9CN7TXE":3,"skill-same:01M6C1204QJSQ8HS0ZP9CN7TXE":54},{"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":27,"linkOnly":28,"markdownContent":29,"markdownBody":30,"frontMatter":31,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":14,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":37,"ownerDescription":38,"updatedAt":39,"install":40,"resources":53},"01M6C1204QJSQ8HS0ZP9CN7TXE","git-commit-messages",null,"Guidelines for Michael Vorburger's personal Git commit style.","vorburger\u002Faifiles","vorburger","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F298598?v=4","01M6C11R5X69DM3ZRH19WVATJ5","Michael Vorburger","01M6C11RAG3NAQQZ7S3QNG7ER4",0,"CC-BY-4.0","https:\u002F\u002Fgithub.com\u002Fvorburger\u002Faifiles\u002Fblob\u002Fmain\u002Fskills\u002Fgit-commit-messages\u002FSKILL.md",[],[19,20,21,22,23,24,25,26],"commit","git commit","git","messages","commit messages","git commit messages","personal","guidelines","2026-11-10 10:12:30",false,"---\nname: git-commit-messages\ndescription: Guidelines for Michael Vorburger's personal Git commit style.\n---\n\n# Git Commit Messages\n\nThis skill describes Michael Vorburger's preferred style for Git commit messages across his projects:\n\n## Conventional Commits\n\nUse Conventional Commits format where applicable: `\u003Ctype>(\u003Cscope>): \u003Cdescription>`\n\nCommon types:\n\n- `feat`: If it looks like any sort of new feature is introduced, even minor.\n- `fix`: If it's clearly more of a sort of minor fix.\n- `docs`: If only files in the `docs\u002F` directory changed, and no files outside of it.\n- `deps`: If only dependency related files changed (e.g., `MODULE.bazel`, `docs\u002Fdev\u002Fdependencies.txt`, `maven_install.json`).\n- `style`: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc).\n- `refactor`: A code change that neither fixes a bug nor adds a feature.\n- `perf`: A code change that improves performance.\n- `test`: Adding missing tests or correcting existing tests.\n- `build`: Changes that affect the build system or external dependencies.\n- `ci`: Changes to our CI configuration files and scripts.\n- `chore`: Other changes that don't modify src or test files.\n\n## Skills as Code\n\nFiles under a directory named `skills\u002F` containing `name:` and `description:` YAML front-matter in their MD are considered executable code for the agent, not just documentation. Adding or modifying a skill should therefore always be of commit type `feat` or `fix`, not `docs`.\n\n## General Guidelines\n\n- Keep the subject line (TL;DR) short (maximum 60 characters).\n- Use the imperative mood in the subject line (e.g., \"Add feature\" instead of \"Added feature\").\n- Use the body to explain what and why, vs. how.\n- Do not end the subject line with a dot.\n- Before creating a commit, test the repository. Refer to the `testing` skill for how to test.\n","# Git Commit Messages\n\nThis skill describes Michael Vorburger's preferred style for Git commit messages across his projects:\n\n## Conventional Commits\n\nUse Conventional Commits format where applicable: `\u003Ctype>(\u003Cscope>): \u003Cdescription>`\n\nCommon types:\n\n- `feat`: If it looks like any sort of new feature is introduced, even minor.\n- `fix`: If it's clearly more of a sort of minor fix.\n- `docs`: If only files in the `docs\u002F` directory changed, and no files outside of it.\n- `deps`: If only dependency related files changed (e.g., `MODULE.bazel`, `docs\u002Fdev\u002Fdependencies.txt`, `maven_install.json`).\n- `style`: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc).\n- `refactor`: A code change that neither fixes a bug nor adds a feature.\n- `perf`: A code change that improves performance.\n- `test`: Adding missing tests or correcting existing tests.\n- `build`: Changes that affect the build system or external dependencies.\n- `ci`: Changes to our CI configuration files and scripts.\n- `chore`: Other changes that don't modify src or test files.\n\n## Skills as Code\n\nFiles under a directory named `skills\u002F` containing `name:` and `description:` YAML front-matter in their MD are considered executable code for the agent, not just documentation. Adding or modifying a skill should therefore always be of commit type `feat` or `fix`, not `docs`.\n\n## General Guidelines\n\n- Keep the subject line (TL;DR) short (maximum 60 characters).\n- Use the imperative mood in the subject line (e.g., \"Add feature\" instead of \"Added feature\").\n- Use the body to explain what and why, vs. how.\n- Do not end the subject line with a dot.\n- Before creating a commit, test the repository. Refer to the `testing` skill for how to test.\n",{"name":5,"description":7},"main","6cfcb4ea30a31850a900583021f7ef2b5159538f","skills\u002Fgit-commit-messages","https:\u002F\u002Fgithub.com\u002Fvorburger\u002Faifiles","https:\u002F\u002Fgithub.com\u002Fvorburger","http:\u002F\u002Fwww.vorburger.ch"," 🇺🇦 #KyivNotKiev. Geek Father. EPFL alumni. Speaks Esperanto, Java, no Klingon, but a few other langs. Works at Google. Formerly at Red Hat. Repos personal.","2026-10-18 19:44:02",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add vorburger\u002Faifiles --skill git-commit-messages",{"tool":46,"command":47},"bunx","bunx skills add vorburger\u002Faifiles --skill git-commit-messages",{"tool":49,"command":50},"pnpm","pnpm dlx skills add vorburger\u002Faifiles --skill git-commit-messages","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvorburger\u002Faifiles\u002Fblob\u002Fmain\u002Fskills\u002Fgit-commit-messages\u002FSKILL.md",true,[],[55,64,77,91,99,108],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":27},"01M6C12QVGQB262AXE96P898W5","vorburger-profile","Provides personal and professional information about Michael Vorburger.","https:\u002F\u002Fgithub.com\u002Fvorburger\u002Faifiles\u002Fblob\u002Fmain\u002Fskills\u002Fvorburger-profile\u002FSKILL.md",[],[62,63,25],"vorburger profile","profile",{"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":27},"01M6C12NWCGZ83F0WCSQR8TBC0","typescript-conventions","Enforces TypeScript and project-specific coding standards, including Bun usage and the zero-warning policy. Use this skill when creating or modifying any TypeScript or configuration files.","https:\u002F\u002Fgithub.com\u002Fvorburger\u002Faifiles\u002Fblob\u002Fmain\u002Fskills\u002Ftypescript-conventions\u002FSKILL.md",[],[71,72,73,74,75,76],"typescript conventions","typescript","policy","coding standards","ZeRO","coding",{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":88,"publishedAt":27},"01M6C12KVA8A1HDX56XKJQF93K","testing","Guidelines for determining how to test a project based on its contents.","https:\u002F\u002Fgithub.com\u002Fvorburger\u002Faifiles\u002Fblob\u002Fmain\u002Fskills\u002Ftesting\u002FSKILL.md",[83],{"categoryNo":84,"categoryName":85,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[79,89,26,90],"test","how",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":27},"01M6C12JK1GP5KP4AMKDY5AQJR","skills","Rules for Agent Skills files.","https:\u002F\u002Fgithub.com\u002Fvorburger\u002Faifiles\u002Fblob\u002Fmain\u002Fskills\u002Fskills\u002FSKILL.md",[],[98],"Rules",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":27},"01M6C12GTNMWM6NAB1ZAEJ20NE","scripting","Conventions for writing and executing scripts (TS, Bash, etc.).","https:\u002F\u002Fgithub.com\u002Fvorburger\u002Faifiles\u002Fblob\u002Fmain\u002Fskills\u002Fscripting\u002FSKILL.md",[],[101,106,107],"Bash","writing",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":27},"01M6C12F45S1D29YM5HMEAE10S","preferred-tools","Preferred tools for common tasks like linting and link checking.","https:\u002F\u002Fgithub.com\u002Fvorburger\u002Faifiles\u002Fblob\u002Fmain\u002Fskills\u002Fpreferred-tools\u002FSKILL.md",[],[115,116,117,118],"Tools","preferred tools","common","tasks"]