[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PMCNSAK1GC3P7C5J49R3RE":3,"skill-same:01M6PMCNSAK1GC3P7C5J49R3RE":71},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":14,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M6PMCNSAK1GC3P7C5J49R3RE","start-ticket",null,"Kick off work on a Linear ticket end to end — file or look up the ticket, create an isolated jj workspace for it, move into that workspace, pull the ticket, and brief its scope. Use when the user wants to start working on a subject or an existing ticket, \"start a ticket\", \"kick off LIN-123\", or spin up a workspace from a ticket and begin.","vjrasane\u002Fdotfiles","vjrasane","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F3148501?v=4","01M6BXVXZN07KKKXF9Q8JNN90K","Ville Räsänen","01M6BXVY3R8G19AN5BRA73H85R",0,"GPL-2.0","https:\u002F\u002Fgithub.com\u002Fvjrasane\u002Fdotfiles\u002Fblob\u002Fmain\u002Fllms\u002Fclaude\u002Fskills\u002Fstart-ticket\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"start ticket","start","ticket","up","Existing","for","URL","quick","move","scope","end","MCP","use","linear ticket","jj","work on","Bash","brief","file","pull","2026-11-10 10:12:30",false,"---\nname: start-ticket\ndescription: Kick off work on a Linear ticket end to end — file or look up the ticket, create an isolated jj workspace for it, move into that workspace, pull the ticket, and brief its scope. Use when the user wants to start working on a subject or an existing ticket, \"start a ticket\", \"kick off LIN-123\", or spin up a workspace from a ticket and begin.\nallowed-tools: Skill, AskUserQuestion, Bash, Read, Grep, Glob, mcp__plugin_hm_linear, mcp__claude_ai_Linear\nargument-hint: \u003Csubject for a new ticket, or an existing ticket ID\u002FURL; add \"quick\" to skip ticket questions>\n---\n\n# Start Ticket\n\nDrive the opening of a ticket in one shot: ticket → workspace → move in → pull → brief.\nChain the existing `linear-ticket` and `workspace` skills rather than reimplementing them;\nthey stay the source of truth for how tickets and workspaces are made. Run unattended through\nthe brief, then hand back so the user directs the actual work.\n\nRun from inside the repo the work belongs to — the workspace is a jj workspace of the current\nrepo.\n\n## Input\n\nThe argument is either:\n\n- **A subject** — free text describing new work (e.g. \"rotate the ingestion S3 keys\"). No\n  ticket exists yet; create one.\n- **An existing ticket** — a Linear identifier (`LIN-123`, `PROJ-45`) or a Linear URL\n  (`https:\u002F\u002Flinear.app\u002F...\u002Fissue\u002FLIN-123\u002F...`). Skip creation; use it as-is.\n\nDetect an existing ticket when the argument matches `^[A-Z][A-Z0-9]+-[0-9]+$` or is a\n`linear.app` URL (extract the identifier from the URL path). Anything else is a subject.\n\n## Workflow\n\n1. **Resolve the ticket.**\n   - *Existing:* fetch it with the Linear MCP (`get_issue`). Confirm it resolved; if not,\n     stop and report.\n   - *New:* invoke the `linear-ticket` skill with the subject. It runs interactive (confirms\n     team\u002Fproject) unless the argument contains \"quick\"\u002F\"small\"\u002F\"fast\" — pass those words\n     through so its fast-path fires. When it returns, capture the created identifier.\n\n2. **Create the workspace.** Invoke the `workspace` skill, telling it this is for the ticket\n   and passing the ticket identifier and title so it builds the slugged directory\n   (`ws-\u003Cticket-id>-\u003Cname>`, lowercased). Let it pick the base (trunk) and do the jj setup,\n   symlinks, and bookmark. Capture the workspace path it reports.\n\n3. **Move in.** `cd` into the workspace path. The Bash working directory persists for the rest\n   of the session, so all later work happens there — no new session is started. Verify with\n   `jj workspace root` that the cwd is the new workspace before continuing.\n\n4. **Pull the ticket.** Fetch the full issue (`get_issue`) — description, state, assignee,\n   priority, labels, relations, and recent comments if present.\n\n5. **Brief and hand back.** Summarize in a few lines: the identifier + title + URL, the scope\n   (from the description), and anything load-bearing (relations, acceptance criteria the user\n   put on the ticket). Do **not** start planning or writing code. End by handing control back\n   to the user to direct the work.\n\n## Reporting\n\nOne compact block at the end:\n\n```\nLIN-123 — Rotate ingestion S3 keys   \u003Curl>\nWorkspace: ..\u002Fws-lin-123-rotate-ingestion-s3-keys  (cwd now here)\nScope: \u003Cone or two lines from the ticket>\nReady — how do you want to start?\n```\n\n## Notes\n\n- If the argument is empty, ask for the subject or ticket (`AskUserQuestion`), then proceed.\n- If `linear-ticket` or `workspace` needs a decision (team, base), let that skill handle the\n  asking — don't pre-empt it.\n- Stop and report rather than guessing if the ticket won't resolve or the workspace creation\n  fails; don't move in or brief on a half-built state.\n","# Start Ticket\n\nDrive the opening of a ticket in one shot: ticket → workspace → move in → pull → brief.\nChain the existing `linear-ticket` and `workspace` skills rather than reimplementing them;\nthey stay the source of truth for how tickets and workspaces are made. Run unattended through\nthe brief, then hand back so the user directs the actual work.\n\nRun from inside the repo the work belongs to — the workspace is a jj workspace of the current\nrepo.\n\n## Input\n\nThe argument is either:\n\n- **A subject** — free text describing new work (e.g. \"rotate the ingestion S3 keys\"). No\n  ticket exists yet; create one.\n- **An existing ticket** — a Linear identifier (`LIN-123`, `PROJ-45`) or a Linear URL\n  (`https:\u002F\u002Flinear.app\u002F...\u002Fissue\u002FLIN-123\u002F...`). Skip creation; use it as-is.\n\nDetect an existing ticket when the argument matches `^[A-Z][A-Z0-9]+-[0-9]+$` or is a\n`linear.app` URL (extract the identifier from the URL path). Anything else is a subject.\n\n## Workflow\n\n1. **Resolve the ticket.**\n   - *Existing:* fetch it with the Linear MCP (`get_issue`). Confirm it resolved; if not,\n     stop and report.\n   - *New:* invoke the `linear-ticket` skill with the subject. It runs interactive (confirms\n     team\u002Fproject) unless the argument contains \"quick\"\u002F\"small\"\u002F\"fast\" — pass those words\n     through so its fast-path fires. When it returns, capture the created identifier.\n\n2. **Create the workspace.** Invoke the `workspace` skill, telling it this is for the ticket\n   and passing the ticket identifier and title so it builds the slugged directory\n   (`ws-\u003Cticket-id>-\u003Cname>`, lowercased). Let it pick the base (trunk) and do the jj setup,\n   symlinks, and bookmark. Capture the workspace path it reports.\n\n3. **Move in.** `cd` into the workspace path. The Bash working directory persists for the rest\n   of the session, so all later work happens there — no new session is started. Verify with\n   `jj workspace root` that the cwd is the new workspace before continuing.\n\n4. **Pull the ticket.** Fetch the full issue (`get_issue`) — description, state, assignee,\n   priority, labels, relations, and recent comments if present.\n\n5. **Brief and hand back.** Summarize in a few lines: the identifier + title + URL, the scope\n   (from the description), and anything load-bearing (relations, acceptance criteria the user\n   put on the ticket). Do **not** start planning or writing code. End by handing control back\n   to the user to direct the work.\n\n## Reporting\n\nOne compact block at the end:\n\n```\nLIN-123 — Rotate ingestion S3 keys   \u003Curl>\nWorkspace: ..\u002Fws-lin-123-rotate-ingestion-s3-keys  (cwd now here)\nScope: \u003Cone or two lines from the ticket>\nReady — how do you want to start?\n```\n\n## Notes\n\n- If the argument is empty, ask for the subject or ticket (`AskUserQuestion`), then proceed.\n- If `linear-ticket` or `workspace` needs a decision (team, base), let that skill handle the\n  asking — don't pre-empt it.\n- Stop and report rather than guessing if the ticket won't resolve or the workspace creation\n  fails; don't move in or brief on a half-built state.\n",{"name":5,"description":7,"allowed-tools":49,"argument-hint":50},"Skill, AskUserQuestion, Bash, Read, Grep, Glob, mcp__plugin_hm_linear, mcp__claude_ai_Linear","\u003Csubject for a new ticket, or an existing ticket ID\u002FURL; add \"quick\" to skip ticket questions>","main","279f653efb69e08a0404316e32356fb2e4d78acd","llms\u002Fclaude\u002Fskills\u002Fstart-ticket","https:\u002F\u002Fgithub.com\u002Fvjrasane\u002Fdotfiles","https:\u002F\u002Fgithub.com\u002Fvjrasane","2026-11-05 23:04:06",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add vjrasane\u002Fdotfiles --skill start-ticket",{"tool":63,"command":64},"bunx","bunx skills add vjrasane\u002Fdotfiles --skill start-ticket",{"tool":66,"command":67},"pnpm","pnpm dlx skills add vjrasane\u002Fdotfiles --skill start-ticket","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvjrasane\u002Fdotfiles\u002Fblob\u002Fmain\u002Fllms\u002Fclaude\u002Fskills\u002Fstart-ticket\u002FSKILL.md",true,[],[72,98,104,116,127,146],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":89,"publishedAt":44},"01M6BXWMYDB847PE9T0JR5J26K","writing-assistant","Help improve and flesh out written text in markdown or plain text files. Use when the user wants writing feedback, style fixes, grammar corrections, or help expanding bullet points into prose. Does not write text from scratch.","https:\u002F\u002Fgithub.com\u002Fvjrasane\u002Fdotfiles\u002Fblob\u002Fmain\u002Fllms\u002Fclaude\u002Fskills\u002Fwriting-assistant\u002FSKILL.md",[78,81,84],{"categoryNo":79,"categoryName":80,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":82,"categoryName":83,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[90,91,92,42,93,94,95,96,97],"writing assistant","writing","assistant","help","markdown","improve","text","feedback",{"skillNo":99,"name":100,"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":101,"categories":102,"keywords":103,"publishedAt":44},"01M6BXWKJ4182T739T99VZFMHT","workspace","https:\u002F\u002Fgithub.com\u002Fvjrasane\u002Fdotfiles\u002Fblob\u002Fmain\u002Fllms\u002Fclaude\u002Fskills\u002Fworkspace\u002FSKILL.md",[],[100],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":111,"publishedAt":44},"01M6BXWGV66SSKYFMCHTRKEDKK","skill-writer","Guide users through creating Agent Skills for Claude Code. Use when the user wants to create, write, author, or design a new Skill, or needs help with SKILL.md files, frontmatter, or skill structure.","https:\u002F\u002Fgithub.com\u002Fvjrasane\u002Fdotfiles\u002Fblob\u002Fmain\u002Fllms\u002Fclaude\u002Fskills\u002Fskill-writer\u002FSKILL.md",[110],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[112,93,113,114,115],"skill writer","code","create","design",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":44},"01M6BXWF4JR4RRHJRSMRVS7BKQ","review","Review code changes for quality, security, and best practices","https:\u002F\u002Fgithub.com\u002Fvjrasane\u002Fdotfiles\u002Fblob\u002Fmain\u002Fllms\u002Fclaude\u002Fskills\u002Freview\u002FSKILL.md",[],[118,123,124,125,126,113],"security","quality","review code","best practices",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":137,"publishedAt":44},"01M6BXWCGMN7YPSZ71AG207YSW","review-mr","Find the GitLab merge request for the current jj branch and run a code review on it. Use when the user wants to review the MR, review the merge request, review \"my MR\", or review the current branch's changes on GitLab.","https:\u002F\u002Fgithub.com\u002Fvjrasane\u002Fdotfiles\u002Fblob\u002Fmain\u002Fllms\u002Fclaude\u002Fskills\u002Freview-mr\u002FSKILL.md",[133,136],{"categoryNo":134,"categoryName":135,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[138,118,139,140,35,141,142,143,114,144,113,145,40,38],"review mr","gitlab","code review","diffs","merge","plugin","run","linear",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":153,"publishedAt":44},"01M6BXWA9RFTMJQ7R5XP4ETSC8","researcher","Research a topic by gathering information from web sources and local files. Use when the user asks to research, investigate, or deep-dive into a subject. Supports incremental research via a research.md file.","https:\u002F\u002Fgithub.com\u002Fvjrasane\u002Fdotfiles\u002Fblob\u002Fmain\u002Fllms\u002Fclaude\u002Fskills\u002Fresearcher\u002FSKILL.md",[152],{"categoryNo":82,"categoryName":83,"taxonomyType":21,"taxonomyTypeDesc":22},[148,154,42,155,156],"web","investigate","research"]