[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71SWR42MJZWE53DF26XFNFM":3,"skill-same:01M71SWR42MJZWE53DF26XFNFM":65},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M71SWR42MJZWE53DF26XFNFM","jujutsu-describe",null,"Describe the current jj revision with a proper commit message. Use when the user wants to create a commit message, describe changes, write a commit summary, prepare a commit description, or says \"describe this revision\", \"what should I commit\", \"create commit message\".","Artawower\u002Fkaizen","Artawower","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F16963833?v=4","01M71SV5H0DRR8KXVGD4R51Z99","Art","01M71SV5J1B97T7349GGXQCYXT",2,"GPL-3.0","https:\u002F\u002Fgithub.com\u002FArtawower\u002Fkaizen\u002Fblob\u002Fmaster\u002Fdotfiles\u002Fdot_agents\u002Fskills\u002Fjujutsu-describe\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"jujutsu describe","describe","jujutsu","user","prepare","summary","revision","write","create commit","message","changes","create","with","commit","when","commit message","use","describe changes","jj","2026-11-10 13:02:02",false,"---\nname: jujutsu-describe\ndescription: Describe the current jj revision with a proper commit message. Use when the user wants to create a commit message, describe changes, write a commit summary, prepare a commit description, or says \"describe this revision\", \"what should I commit\", \"create commit message\".\n---\n\n# Jujutsu Describe Skill\n\nGenerate a proper commit message for the current jj revision by analyzing recent commits and current changes.\n\n## Step 1: Check Recent Commit Messages\n\nRun this command to see the last 5 commit messages:\n\n```bash\njj log --limit 5 -r @-\n```\n\nAnalyze the commit message format from these commits to understand the pattern we use:\n- What's the commit type prefix (feat, fix, refactor, chore, etc.)?\n- Is there a scope in parentheses?\n- How are titles formatted (length, capitalization)?\n- Are there any ticket numbers like [VW-XXX]?\n\nExtract this pattern information to reuse it consistently.\n\n## Step 2: Analyze Current Changes\n\nRun this command to see what's changed in the current working copy:\n\n```bash\njj diff\n```\n\nExamine the output to understand what files were modified and what the changes do.\n\n## Step 3: Determine Commit Type and Title\n\nBased on the changes, determine the appropriate commit type:\n\n- **feat** - New feature or functionality\n- **fix** - Bug fix\n- **refactor** - Code refactoring without behavior change\n- **chore** - Maintenance, build changes, dependencies, tooling\n- **docs** - Documentation only\n- **test** - Test additions or changes\n- **style** - Formatting, no code logic change\n\nYou can optionally include a scope in parentheses, e.g., `feat(auth)`, `fix(ui)`, `refactor(api)`.\n\n## Step 4: Check for Previous Issue Reference\n\nLook at the previous commit message (from Step 1). If it contains a ticket number in the format `[VW-XXX]` or similar:\n\n- **Reuse the same ticket number** for consistency\n- If no ticket number found but you're unsure if one should be used, ask the user\n\n## Step 5: Draft the Commit Message\n\n### Title Format\n\n```\n\u003Ctype>(\u003Cscope>): \u003C Title under 50 chars >\n```\n\nExamples:\n- `feat(auth): add JWT authentication`\n- `fix(ui): resolve button alignment`\n- `refactor(api): simplify query builder`\n- `chore(deps): update dependencies`\n- `docs(readme): fix typo`\n\n### Description (Optional)\n\nOnly add a description body (separate line after title) if:\n- The change is non-obvious and needs context\n- There are breaking changes or migrations\n- There are related issues or follow-ups\n\nKeep descriptions concise and informative.\n\n## Final Output\n\nPresent the commit message to the user:\n\n```\nCommit message:\n\u003Ctitle>\n\n\u003Coptional description>\n\nUse this message? [Y\u002Fn]\n```\n\nWait for user confirmation before applying with `jj describe`.","# Jujutsu Describe Skill\n\nGenerate a proper commit message for the current jj revision by analyzing recent commits and current changes.\n\n## Step 1: Check Recent Commit Messages\n\nRun this command to see the last 5 commit messages:\n\n```bash\njj log --limit 5 -r @-\n```\n\nAnalyze the commit message format from these commits to understand the pattern we use:\n- What's the commit type prefix (feat, fix, refactor, chore, etc.)?\n- Is there a scope in parentheses?\n- How are titles formatted (length, capitalization)?\n- Are there any ticket numbers like [VW-XXX]?\n\nExtract this pattern information to reuse it consistently.\n\n## Step 2: Analyze Current Changes\n\nRun this command to see what's changed in the current working copy:\n\n```bash\njj diff\n```\n\nExamine the output to understand what files were modified and what the changes do.\n\n## Step 3: Determine Commit Type and Title\n\nBased on the changes, determine the appropriate commit type:\n\n- **feat** - New feature or functionality\n- **fix** - Bug fix\n- **refactor** - Code refactoring without behavior change\n- **chore** - Maintenance, build changes, dependencies, tooling\n- **docs** - Documentation only\n- **test** - Test additions or changes\n- **style** - Formatting, no code logic change\n\nYou can optionally include a scope in parentheses, e.g., `feat(auth)`, `fix(ui)`, `refactor(api)`.\n\n## Step 4: Check for Previous Issue Reference\n\nLook at the previous commit message (from Step 1). If it contains a ticket number in the format `[VW-XXX]` or similar:\n\n- **Reuse the same ticket number** for consistency\n- If no ticket number found but you're unsure if one should be used, ask the user\n\n## Step 5: Draft the Commit Message\n\n### Title Format\n\n```\n\u003Ctype>(\u003Cscope>): \u003C Title under 50 chars >\n```\n\nExamples:\n- `feat(auth): add JWT authentication`\n- `fix(ui): resolve button alignment`\n- `refactor(api): simplify query builder`\n- `chore(deps): update dependencies`\n- `docs(readme): fix typo`\n\n### Description (Optional)\n\nOnly add a description body (separate line after title) if:\n- The change is non-obvious and needs context\n- There are breaking changes or migrations\n- There are related issues or follow-ups\n\nKeep descriptions concise and informative.\n\n## Final Output\n\nPresent the commit message to the user:\n\n```\nCommit message:\n\u003Ctitle>\n\n\u003Coptional description>\n\nUse this message? [Y\u002Fn]\n```\n\nWait for user confirmation before applying with `jj describe`.",{"name":5,"description":7},"master","cbded6c96796a063405af105d5b3209ab6219407","dotfiles\u002Fdot_agents\u002Fskills\u002Fjujutsu-describe",0,"https:\u002F\u002Fgithub.com\u002FArtawower\u002Fkaizen","https:\u002F\u002Fgithub.com\u002FArtawower","workationmode.com","2026-11-10 19:23:03",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add Artawower\u002Fkaizen --skill jujutsu-describe",{"tool":57,"command":58},"bunx","bunx skills add Artawower\u002Fkaizen --skill jujutsu-describe",{"tool":60,"command":61},"pnpm","pnpm dlx skills add Artawower\u002Fkaizen --skill jujutsu-describe","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FArtawower\u002Fkaizen\u002Fblob\u002Fmaster\u002Fdotfiles\u002Fdot_agents\u002Fskills\u002Fjujutsu-describe\u002FSKILL.md",true,[],[66,98,115,138,158,182],{"skillNo":67,"name":68,"nameZh":6,"description":69,"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":77,"publishedAt":38},"01M71SYJ1B45ZKM8J96AZ3TS0H","yt-analyze","Fetch YouTrack task + comments via MCP, critically analyze relevance and requirements, produce concise summary of what to implement, and build an implementation plan mapped to codebase. Trigger - YouTrack issue ID or request to \"analyze task\", \"plan task\", \"break down YT issue\".","https:\u002F\u002Fgithub.com\u002FArtawower\u002Fkaizen\u002Fblob\u002Fmaster\u002Fdotfiles\u002Fdot_agents\u002Fskills\u002Fyt-analyze\u002FSKILL.md",[72],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97],"analyze","yt analyze","yt","fetch","implementation plan","MCP","plan task","plan","request","break","issue","youtrack","down","trigger","produce","break down","comments","requirements","implement","task",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":38},"01M71SYF7RSTEXKDWPXJ08EVQG","youtrack-task","Analyzes a YouTrack issue, reviews comments and attachments, and proposes or creates actionable subtasks. Use when the user gives a YouTrack issue ID and wants synthesis, decomposition, or follow-up tasks.","https:\u002F\u002Fgithub.com\u002FArtawower\u002Fkaizen\u002Fblob\u002Fmaster\u002Fdotfiles\u002Fdot_agents\u002Fskills\u002Fyoutrack-task\u002FSKILL.md",[],[105,89,97,106,107,108,109,110,111,88,112,35,33,94,113,114,22],"youtrack task","id","reviews","attachments","decomposition","actionable","up","follow-up","tasks","Synthesis",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":38},"01M71SYCE94601T6DA5G2GDKYA","youtrack-search","Searches YouTrack from natural language or native query syntax and returns a concise report with the most relevant issues. Use when the user wants to find issues, triage work, or translate a plain-language query into YouTrack search.","https:\u002F\u002Fgithub.com\u002FArtawower\u002Fkaizen\u002Fblob\u002Fmaster\u002Fdotfiles\u002Fdot_agents\u002Fskills\u002Fyoutrack-search\u002FSKILL.md",[],[122,123,89,124,125,126,127,128,35,33,129,31,130,131,132,133,134,135,136,137],"search","youtrack search","natural language","relevant","translate","issues","plain-language","query","work","concise","native","find","report","syntax","triage","plain",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":152,"publishedAt":38},"01M71SYAXN8EA6DDXEZWVY872S","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002FArtawower\u002Fkaizen\u002Fblob\u002Fmaster\u002Fdotfiles\u002Fdot_agents\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[144,147],{"categoryNo":145,"categoryName":146,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":148,"categoryName":149,"taxonomyType":150,"taxonomyTypeDesc":151},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[153,154,155,156,35,157,33],"writing for agents","for","writing","editing","documents",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":167,"publishedAt":38},"01M71SY8ZKMWPF8ZAENT7MQE28","write-a-prd","Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.","https:\u002F\u002Fgithub.com\u002FArtawower\u002Fkaizen\u002Fblob\u002Fmaster\u002Fdotfiles\u002Fdot_agents\u002Fskills\u002Fwrite-a-prd\u002FSKILL.md",[164],{"categoryNo":165,"categoryName":166,"taxonomyType":150,"taxonomyTypeDesc":151},"01JBSEEDCAT000000000000031","产品经理",[26,168,169,170,171,172,173,174,175,176,177,35,178,33,179,180,95,30,181,85],"write a prd","prd","interview","as","exploration","feature","submit","design","module","new","document","user interview","codebase exploration","new feature",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":38},"01M71SY6J9F119TJSMA2YBEP5P","vitest","Plan and write Vitest tests for changed code. Analyses git diff, checks existing tests, produces a concrete test plan using flat test structure (no describe\u002Fit blocks). Use when adding tests for new\u002Fchanged code, improving Vitest coverage, or asking what to test after a change.","https:\u002F\u002Fgithub.com\u002FArtawower\u002Fkaizen\u002Fblob\u002Fmaster\u002Fdotfiles\u002Fdot_agents\u002Fskills\u002Fvitest\u002FSKILL.md",[],[184,189,190,191,154,192,177,35,193,194,33,195,196,197,85,198,199,26,200,201],"coverage","test plan","diff","tests","Existing","adding tests","code","test","structure","change","flat","blocks","git"]