[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DXSC60SY7QD7SX4VY5RJD8":3,"skill-same:01M6DXSC60SY7QD7SX4VY5RJD8":75},{"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":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":61,"install":62,"resources":74},"01M6DXSC60SY7QD7SX4VY5RJD8","comment-linear-issue",null,"Use this skill only when the user explicitly invokes \u002Fcomment-linear-issue to add a Markdown comment to an existing Linear issue. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. It shows the comment preview, requires explicit confirmation, then posts the comment.","atomicinnovation\u002Faccelerator","atomicinnovation","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F65866524?v=4","01M6DXP513JV585FN2QPNR6079","Atomic","01M6DXP55MPK99YVZ2HGMEN991",34,"MIT","https:\u002F\u002Fgithub.com\u002Fatomicinnovation\u002Faccelerator\u002Fblob\u002Fmain\u002Fskills\u002Fintegrations\u002Flinear\u002Fcomment-linear-issue\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"comment linear issue","issue","linear","auto","when","effects","Existing","true","posts","with","preview","only","never","use","user","context","write","read","confirmation","text","markdown","Bash","write skill","file","2026-11-10 10:12:30",false,"---\nname: comment-linear-issue\ndescription: >\n  Use this skill only when the user explicitly invokes \u002Fcomment-linear-issue to\n  add a Markdown comment to an existing Linear issue. This is a write skill with\n  irreversible side effects — it must never be auto-invoked from conversational\n  context. It shows the comment preview, requires explicit confirmation, then\n  posts the comment.\nargument-hint: \"\u003CIDENTIFIER> --body TEXT | --body-file PATH [--quiet]\"\ndisable-model-invocation: true\nallowed-tools:\n  - Bash\n  - Read\n  - Write\n---\n\n# Comment on a Linear Issue\n\n!`accelerator config context --skill comment-linear-issue --fail-safe`\n\n> **Configuration**: Set `work.integration: linear` in `.accelerator\u002Fconfig.md`.\n\nAdd a Markdown comment to a Linear issue via `commentCreate`. Work through the\nsteps in order. This skill never auto-invokes — it only runs when the user\nexplicitly types `\u002Fcomment-linear-issue`.\n\nThe comment body comes ONLY from text the user typed this turn or a file path\nthe user named this turn — never synthesised from prior context.\n\n## Step 1: Parse arguments\n\nRead the issue identifier (positional) and the body source (`--body TEXT` or\n`--body-file PATH`).\n\n## Step 2: Render the preview\n\nResolve the body: if `--body-file PATH` was given, read the file; otherwise take\n`--body TEXT` verbatim. If neither is present, STOP with `E_COMMENT_NO_BODY`.\n\nShow the resolved intent — the operation (`commentCreate`), the target issue,\nand the Markdown body — under:\n\n> **Proposed Linear write — review before sending**\n\n## Step 3: Confirm before writing\n\nAsk:\n\n> Post this comment to Linear? Reply **y** to confirm, **n** to revise, anything\n> else to abort.\n\nOn a clear yes, proceed. On no\u002Frevise, rebuild the preview. On anything\nambiguous, abort with \"Aborted — no Linear write was made.\"\n\n## Step 4: Send and render\n\n```\naccelerator linear comment add \u003CIDENTIFIER> --body \"...\"\n```\n\nThe subcommand emits a JSON envelope with a top-level `outcome` keyword. On\n`added`, confirm the comment was posted. On any non-zero exit, report the error\nand stop.\n\n!`accelerator config instructions comment-linear-issue --fail-safe`\n","# Comment on a Linear Issue\n\n!`accelerator config context --skill comment-linear-issue --fail-safe`\n\n> **Configuration**: Set `work.integration: linear` in `.accelerator\u002Fconfig.md`.\n\nAdd a Markdown comment to a Linear issue via `commentCreate`. Work through the\nsteps in order. This skill never auto-invokes — it only runs when the user\nexplicitly types `\u002Fcomment-linear-issue`.\n\nThe comment body comes ONLY from text the user typed this turn or a file path\nthe user named this turn — never synthesised from prior context.\n\n## Step 1: Parse arguments\n\nRead the issue identifier (positional) and the body source (`--body TEXT` or\n`--body-file PATH`).\n\n## Step 2: Render the preview\n\nResolve the body: if `--body-file PATH` was given, read the file; otherwise take\n`--body TEXT` verbatim. If neither is present, STOP with `E_COMMENT_NO_BODY`.\n\nShow the resolved intent — the operation (`commentCreate`), the target issue,\nand the Markdown body — under:\n\n> **Proposed Linear write — review before sending**\n\n## Step 3: Confirm before writing\n\nAsk:\n\n> Post this comment to Linear? Reply **y** to confirm, **n** to revise, anything\n> else to abort.\n\nOn a clear yes, proceed. On no\u002Frevise, rebuild the preview. On anything\nambiguous, abort with \"Aborted — no Linear write was made.\"\n\n## Step 4: Send and render\n\n```\naccelerator linear comment add \u003CIDENTIFIER> --body \"...\"\n```\n\nThe subcommand emits a JSON envelope with a top-level `outcome` keyword. On\n`added`, confirm the comment was posted. On any non-zero exit, report the error\nand stop.\n\n!`accelerator config instructions comment-linear-issue --fail-safe`\n",{"name":5,"description":48,"allowed-tools":49,"argument-hint":52,"disable-model-invocation":53},"Use this skill only when the user explicitly invokes \u002Fcomment-linear-issue to add a Markdown comment to an existing Linear issue. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. It shows the comment preview, requires explicit confirmation, then posts the comment.\n",[40,50,51],"Read","Write","\u003CIDENTIFIER> --body TEXT | --body-file PATH [--quiet]",true,"main","007b2dd695b63c2f097cdc40e54229b6e8b4596a","skills\u002Fintegrations\u002Flinear\u002Fcomment-linear-issue",2,"https:\u002F\u002Fgithub.com\u002Fatomicinnovation\u002Faccelerator","https:\u002F\u002Fgo-atomic.io","https:\u002F\u002Fgithub.com\u002Fatomicinnovation","2026-11-13 08:45:04",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":53},[64,67,70],{"tool":65,"command":66},"npx","npx skills add atomicinnovation\u002Faccelerator --skill comment-linear-issue",{"tool":68,"command":69},"bunx","bunx skills add atomicinnovation\u002Faccelerator --skill comment-linear-issue",{"tool":71,"command":72},"pnpm","pnpm dlx skills add atomicinnovation\u002Faccelerator --skill comment-linear-issue","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fatomicinnovation\u002Faccelerator\u002Fblob\u002Fmain\u002Fskills\u002Fintegrations\u002Flinear\u002Fcomment-linear-issue\u002FSKILL.md",[],[76,111,134,154,170,194],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":92,"publishedAt":43},"01M70S7PFGVATJREBFEGPJB718","explore-pr","Build an interactive, design-first and picture-first exploration page for a pull request — its architecture, abstractions and design decisions drawn as diagrams, a guided tour in reading order with code as the evidence, an attention map of where the risk sits, a ledger of its riskiest operations, prior review findings re-checked against the code, and simulations specific to the PR — with the reviewer's verdicts and notes saved. Use when the user wants to explore, understand or review a large pull request or its design, asks for a review page, walkthrough or visual explanation of a PR, or is struggling to review a big change.","https:\u002F\u002Fgithub.com\u002Fatomicinnovation\u002Faccelerator\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fexplore-pr\u002FSKILL.md",[82,87],{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[93,94,95,96,97,98,99,100,101,102,23,103,104,40,105,106,107,108,109,110],"explore pr","explore","pr","diagrams","exploration","re","review findings","walkthrough","design","map","number","URL","code","architecture","reviewer","review","notes","change",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":43},"01M6DY04WBTMFV96JMBP5ZXVFX","update-work-item","Update fields (status, priority, tags, parent, etc.) of an existing work item. Use to transition status, change priority, manage tags, or edit any frontmatter field. No transition enforcement — arbitrary changes are allowed.","https:\u002F\u002Fgithub.com\u002Fatomicinnovation\u002Faccelerator\u002Fblob\u002Fmain\u002Fskills\u002Fwork\u002Fupdate-work-item\u002FSKILL.md",[],[118,119,120,121,122,123,32,40,110,124,125,126,127,128,129,25,130,131,132,133],"work","update","update work item","work item","enforcement","manage","config","edit","validate","status","transition","frontmatter","tags","changes","fields","op",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":43},"01M6DY0106CF15CYEJHZM14GBZ","sync-work-items","Reconcile local work items in meta\u002Fwork\u002F with the active remote tracker named by work.integration. Use when the user wants to sync, push, or pull work items to or from Jira or Linear, preview what a sync would change, or reconcile divergent local and remote state.","https:\u002F\u002Fgithub.com\u002Fatomicinnovation\u002Faccelerator\u002Fblob\u002Fmain\u002Fskills\u002Fwork\u002Fsync-work-items\u002FSKILL.md",[],[118,141,142,143,144,145,30,40,29,110,146,147,148,149,150,151,152,124,153,129,23],"sync","sync work items","promote","Meta","local","active","tracker","max","jira","remote","create","adopt","reconcile",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":43},"01M6HNF86984S4XK21Q26VZA21","sync-work-items-recovery","Recovery procedures for work sync failures that need a person — terminal rows, refused pending pushes and refused orders. Read by sync-work-items — not invoked directly.","https:\u002F\u002Fgithub.com\u002Fatomicinnovation\u002Faccelerator\u002Fblob\u002Fmain\u002Fskills\u002Fwork\u002Fsync-work-items-recovery\u002FSKILL.md",[],[161,118,162,141,142,163,164,165,36,166,26,167,168,169],"sync work items recovery","recovery","work-items","for","terminal","person","false","orders","pending",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":179,"publishedAt":43},"01M6DXZWH7PR72VCEXSSD4XNK4","stress-test-work-item","Interactively stress-test a work item by grilling the user on scope, assumptions, acceptance criteria, edge cases, and dependencies to surface issues, gaps, and flawed assumptions before implementation is planned.","https:\u002F\u002Fgithub.com\u002Fatomicinnovation\u002Faccelerator\u002Fblob\u002Fmain\u002Fskills\u002Fwork\u002Fstress-test-work-item\u002FSKILL.md",[176],{"categoryNo":177,"categoryName":178,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000008","测试与质量",[180,181,118,182,121,183,184,185,186,187,188,40,189,190,124,126,191,192,33,103,193,129],"stress test","test","stress test work item","stress","scope","issues","edge","stress-test","acceptance","acceptance criteria","dependencies","implementation","grilling","gaps",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":200,"publishedAt":43},"01M6DXZRQWHTWV1G9PTTHCGGYA","review-work-item","Review a work item through multiple quality lenses and collaboratively iterate based on findings. Use when the user wants to evaluate a work item before implementation or escalation.","https:\u002F\u002Fgithub.com\u002Fatomicinnovation\u002Faccelerator\u002Fblob\u002Fmain\u002Fskills\u002Fwork\u002Freview-work-item\u002FSKILL.md",[],[108,118,201,121,202,203,32,40,42,204,124,126,191,33,205,23,206,207,129,208],"review work item","review work","escalation","quality","metadata","iterate","evaluate","path"]