[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DHHPB142WDTFHP9JFX3B0P":3,"skill-same:01M7DHHPB142WDTFHP9JFX3B0P":48},{"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":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M7DHHPB142WDTFHP9JFX3B0P","kick-ass-commit",null,"Create world class, high quality commit messages that clarify what changed and why. Use when preparing to commit or when the user requests outstanding commit messages.","andremolnar\u002Fopen-open-design","andremolnar","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F919644?v=4","01M7DHE1X4QH6SJBHR92VG5N84","01M7DHE1XRHK1WQV34AM9M328E",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fkick-ass-commit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: kick-ass-commit\ndescription: Create world class, high quality commit messages that clarify what changed and why. Use when preparing to commit or when the user requests outstanding commit messages.\nmetadata:\n  author: andrebot\n  version: \"1.1\"\n---\n\n# Kick-Ass Commit\n\n## Overview\n\nCreate world class, high quality commit messages that make it easy for people and coding agents to understand what happened.\n\n## Steps\n\n1. Collect the set of modified and untracked files (staged and unstaged).\n2. Inspect diffs for all files that will be committed.\n3. Check for documentation updates, including `README`, `CHANGELOG`, or similar files.\n4. Determine an appropriate scope and a concise summary of the changes.\n5. Draft a commit message using the template and include clear, factual bullet points.\n6. When executing `git commit`, keep shell quoting safe: do not wrap file paths or snippets in backticks inside `-m` values because backticks trigger command substitution.\n7. Immediately validate the final commit message with `git log -1 --format=%B` before any push.\n8. If the message is malformed and the commit is not pushed yet, fix it with a new `git commit --amend -m \"...\" -m \"...\"`, then re-validate.\n9. If the malformed commit was already pushed, do not rewrite history unless the user explicitly requests it; otherwise create a follow-up commit that corrects the record.\n\n## Inputs\n\n- Repository state (status, diff, staged files).\n- Optional scope hint from the user.\n\n## Outputs\n\n- A commit message in the requested template.\n- A short note if documentation changes are detected or missing.\n- A validated final message check before push (`git log -1 --format=%B`).\n\n## Edge cases\n\n- If no changes are present, do not draft a commit; report that there is nothing to commit.\n- If documentation changes are expected but missing, call it out and suggest adding them.\n- If the scope is unclear, infer it from the dominant change area.\n- If message text needs inline code formatting, keep markdown backticks in design notes only; do not include them in shell-executed `git commit -m` arguments.\n\n## Commit template\n\n```\n[scope]: Brief description of changes\n\n- Detailed bullet point about what changed\n- Second detail point\n- Nth detail point (as many as needed)\n- N + 1th detail point\n- etc.\n```\n\n## Example prompts\n\n- \"Craft a world class commit message for these changes\"\n- \"Create a kick-ass commit message for this repo\"\n","# Kick-Ass Commit\n\n## Overview\n\nCreate world class, high quality commit messages that make it easy for people and coding agents to understand what happened.\n\n## Steps\n\n1. Collect the set of modified and untracked files (staged and unstaged).\n2. Inspect diffs for all files that will be committed.\n3. Check for documentation updates, including `README`, `CHANGELOG`, or similar files.\n4. Determine an appropriate scope and a concise summary of the changes.\n5. Draft a commit message using the template and include clear, factual bullet points.\n6. When executing `git commit`, keep shell quoting safe: do not wrap file paths or snippets in backticks inside `-m` values because backticks trigger command substitution.\n7. Immediately validate the final commit message with `git log -1 --format=%B` before any push.\n8. If the message is malformed and the commit is not pushed yet, fix it with a new `git commit --amend -m \"...\" -m \"...\"`, then re-validate.\n9. If the malformed commit was already pushed, do not rewrite history unless the user explicitly requests it; otherwise create a follow-up commit that corrects the record.\n\n## Inputs\n\n- Repository state (status, diff, staged files).\n- Optional scope hint from the user.\n\n## Outputs\n\n- A commit message in the requested template.\n- A short note if documentation changes are detected or missing.\n- A validated final message check before push (`git log -1 --format=%B`).\n\n## Edge cases\n\n- If no changes are present, do not draft a commit; report that there is nothing to commit.\n- If documentation changes are expected but missing, call it out and suggest adding them.\n- If the scope is unclear, infer it from the dominant change area.\n- If message text needs inline code formatting, keep markdown backticks in design notes only; do not include them in shell-executed `git commit -m` arguments.\n\n## Commit template\n\n```\n[scope]: Brief description of changes\n\n- Detailed bullet point about what changed\n- Second detail point\n- Nth detail point (as many as needed)\n- N + 1th detail point\n- etc.\n```\n\n## Example prompts\n\n- \"Craft a world class commit message for these changes\"\n- \"Create a kick-ass commit message for this repo\"\n",{"name":5,"metadata":23,"description":7},{"author":24,"version":25},"andrebot","1.1","main","3a6721b94dec7506e324023f2855495c9c54d0d2",".opencode\u002Fskills\u002Fkick-ass-commit",0,"https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design","https:\u002F\u002Fopen-design.ai","https:\u002F\u002Fgithub.com\u002Fandremolnar","2026-10-30 01:33:11",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add andremolnar\u002Fopen-open-design --skill kick-ass-commit",{"tool":40,"command":41},"bunx","bunx skills add andremolnar\u002Fopen-open-design --skill kick-ass-commit",{"tool":43,"command":44},"pnpm","pnpm dlx skills add andremolnar\u002Fopen-open-design --skill kick-ass-commit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fkick-ass-commit\u002FSKILL.md",true,[],[49,56,63,70,77,86],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":18},"01M7DMPDFNBD52ZP0GNY046Z2A","Beta Skill","Instruction-only fixture skill.","https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Ftools\u002Frelease\u002Ftests\u002Ffixtures\u002Fcatalog\u002Fskills\u002Fbeta\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":18},"01M7DMPC4JJ8ENX7VWTMP38Y9C","Alpha Skill","First fixture skill with a runnable demo.","https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Ftools\u002Frelease\u002Ftests\u002Ffixtures\u002Fcatalog\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M7DMP9J5BX307VWVD67J0BBM","Deck One","A small deck template fixture.","https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Ftools\u002Frelease\u002Ftests\u002Ffixtures\u002Fcatalog\u002Fdesign-templates\u002Fdeck-one\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M7DMP7GNYTFXGK9RDZ2X723P","youtube-clipper","YouTube clip generation and editing with automated workflows — pull source video, slice highlights, add captions, and export.","https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-clipper\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":81,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M7DMP2WHMNKM0P5BXRYAG8D1","writing-guidelines","Review docs\u002Fprose for Writing Guidelines compliance. Use when asked to \"review my docs\", \"check writing style\", \"audit prose\", \"review docs voice and tone\", or \"check this page against the writing handbook\".","MIT","https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-guidelines\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-guidelines\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":18},"01M7DMP0GVJQ37CGXYQDD20VWS","wpds","WordPress Design System. Apply WordPress's official design tokens, typography, and component patterns to themes and sites.","https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Fskills\u002Fwpds\u002FSKILL.md",[],[]]