[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72W18N06NXVG3D2VWFZ6Q2R":3,"skill-same:01M72W18N06NXVG3D2VWFZ6Q2R":46},{"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":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M72W18N06NXVG3D2VWFZ6Q2R","comet-hotfix",null,"Comet preset path: Bug fix \u002F hotfix. Skip brainstorming, directly open → build → verify → archive. Applicable for behavior fixes, scenarios not involving new capability design.","rpamis\u002Fcomet","rpamis","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F153429891?v=4","01M72VXBR7EQYMM7KN8C19244V","01M72VXBRYC06QG0ZH0JBGV09V",3298,"MIT","https:\u002F\u002Fgithub.com\u002Frpamis\u002Fcomet\u002Fblob\u002Fmaster\u002Feval\u002Flocal\u002Fskills\u002Fbenchmarks\u002F039-release\u002Fcomet-classic-039-hotfix\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: comet-hotfix\ndescription: \"Comet preset path: Bug fix \u002F hotfix. Skip brainstorming, directly open → build → verify → archive. Applicable for behavior fixes, scenarios not involving new capability design.\"\n---\n\n# Comet Preset Path: Hotfix\n\nQuick bug fix workflow: open → build → verify → archive. Skip brainstorming and full plan, applicable for behavior fixes not involving new capability design.\n\n**Applicable conditions** (all must be met):\n1. Fix bugs in existing functionality, no new capability\n2. No interface changes or architecture adjustments\n3. Change scope is predictable (usually ≤ 2 files)\n\n**Not applicable**: If fix process discovers need for architecture adjustments, should upgrade to full `\u002Fcomet` workflow.\n\n---\n\n## Process (preset workflow, 6 steps)\n\n### 0. Output Language Constraint\n\nStreamlined OpenSpec artifacts must use the language of the user request that triggered this workflow.\n\nExecution chain: open → build → root cause check → verify → archive. Hotfix provides default decisions for each phase: streamlined open, direct build, root cause confirmation, scale-based verification, and final archive confirmation after verification passes.\n\nLocate Comet scripts before starting:\n\n```bash\nCOMET_ENV=\"${COMET_ENV:-$(find . \"$HOME\"\u002F.*\u002Fskills \"$HOME\u002F.config\" \"$HOME\u002F.gemini\" -path '*\u002Fcomet\u002Fscripts\u002Fcomet-env.sh' -type f -print -quit 2>\u002Fdev\u002Fnull)}\"\nif [ -z \"$COMET_ENV\" ]; then\n  echo \"ERROR: comet-env.sh not found. Ensure the comet skill is installed.\" >&2\n  return 1\nfi\n. \"$COMET_ENV\"\n```\n\n### 1. Quick Open (preset open)\n\nReuse Comet open capability to create change, but use hotfix defaults: do not execute `openspec-explore` long exploration, directly enter streamlined change creation.\n\n**Immediately execute:** Use the Skill tool to load the `openspec-new-change` skill. Skipping this step is prohibited.\n\nAfter the skill loads, follow its guidance to create streamlined artifacts:\n  - `proposal.md` — problem description + root cause analysis + fix goal (no solution comparison needed)\n  - `design.md` — fix solution (one is enough, no multi-solution comparison needed)\n  - `tasks.md` — fix task list\n- **No delta spec needed** (unless fix changes existing spec acceptance scenarios)\n\nInitialize Comet state file:\n\n```bash\n\"$COMET_BASH\" \"$COMET_STATE\" init \u003Cname> hotfix\n```\n\nVerify initialized state:\n\n```bash\n\"$COMET_BASH\" \"$COMET_STATE\" check \u003Cname> open\n```\n\nRun phase guard to transition open → build:\n\n```bash\n\"$COMET_BASH\" \"$COMET_GUARD\" \u003Cchange-name> open --apply\n```\n\nCheck `auto_transition` to decide whether to continue:\n\n```bash\n\"$COMET_BASH\" \"$COMET_STATE\" next \u003Cname>\n```\n\n- `NEXT: auto` → continue to Step 2\n- `NEXT: manual` → pause, follow `HINT` to prompt user to run `\u002F\u003CSKILL>` manually\n\n### 2. Direct Build (preset build)\n\nUse hotfix defaults: `build_mode: direct`. Skip Superpowers `brainstorming` and `writing-plans` (unless tasks > 3; if exceeds 3 tasks, transfer to `\u002Fcomet-build`'s plan and execution method selection — note this does NOT trigger full workflow upgrade, only switches execution method).\n\nBefore continuing or starting changes, handle uncommitted changes through `comet\u002Freference\u002Fdirty-worktree.md`. If attribution shows the fix scope exceeds hotfix, handle it through this file's \"Upgrade Conditions\".\n\n**Immediately execute:** Execute tasks one by one according to tasks.md:\n\n1. Read `openspec\u002Fchanges\u002F\u003Cname>\u002Ftasks.md`, get incomplete task list\n2. For each incomplete task:\n   - Modify code according to task description\n   - Run project formatter (e.g., `mvn spotless:apply`, `npm run format`)\n   - Run related tests to confirm pass\n   - Check corresponding `- [ ]` to `- [x]` in tasks.md\n   - Commit code, commit message format: `fix: \u003Cbrief fix description>`\n3. After all tasks complete, explicitly run relevant project tests and build commands\n\n**If fix affects existing spec acceptance scenarios**:\n- Create delta spec in `openspec\u002Fchanges\u002F\u003Cname>\u002Fspecs\u002F\u003Ccapability>\u002Fspec.md`\n- Only include `## MODIFIED Requirements` section\n\nDuring hotfix execution, whenever a crash, unexpected behavior, test failure, or build failure appears while running the program, tests, build, or manual verification, must use the Skill tool to load the Superpowers `systematic-debugging` skill. Before root-cause investigation is complete, must not propose or implement source-code fixes.\n\nFor specific investigation, minimal failing test, fix verification, and keeping the current change verification loop, follow `comet\u002Freference\u002Fdebug-gate.md`.\n\n### 3. Root Cause Elimination Check\n\n**Execute before running build guard**, ensuring the fix actually eliminates the root cause:\n\n1. Read bug description and root cause in proposal.md\n2. Search and verify problem code no longer exists\n3. If root cause not eliminated, return to Step 2 to continue fix (still in build phase, no state transition needed)\n\n**Upgrade conditions**:\n- Root cause check reveals deep architecture issues → Stop hotfix, handle per \"Upgrade Conditions\" section\n- Fix requires additional interface changes → Stop hotfix, handle per \"Upgrade Conditions\" section\n\nAfter root cause is confirmed eliminated, run phase guard to transition build → verify:\n\n```bash\n\"$COMET_BASH\" \"$COMET_GUARD\" \u003Cchange-name> build --apply\n```\n\nState automatically updates to `phase: verify`, `verify_result: pending`, then enter verification.\n\n### 4. Verification (preset verify)\n\nReuse `\u002Fcomet-verify`, with comet-verify's scale assessment deciding lightweight or full verification.\n\n**Immediately execute:** Use the Skill tool to load the `comet-verify` skill. Skipping this step is prohibited.\n\nSmall-scale hotfixes without delta spec usually meet lightweight verification conditions (≤ 3 tasks, ≤ 2 files), comet-verify's scale assessment will select the lightweight verification path (6 quick checks, including lightweight code review). If hotfix created delta spec, enter full verification path according to comet-verify's scale assessment rules.\n\nAfter verification passes, record `.comet.yaml` `verify_result` as `pass` according to `\u002Fcomet-verify` rules, must not skip this status before archiving. After verification passes, still enter `\u002Fcomet-archive`'s final archive confirmation; do not automatically run the archive script.\n\n### 5. Archive (preset archive)\n\nReuse `\u002Fcomet-archive`. Must satisfy `verify_result: pass` in `.comet.yaml` before archiving, and wait for `\u002Fcomet-archive`'s final archive confirmation.\n\n**Immediately execute:** Use the Skill tool to load the `comet-archive` skill to archive. Skipping this step is prohibited.\nIf there is delta spec, sync to main spec according to comet-archive rules, and handle associated Design Doc and Plan archiving annotations.\n\n---\n\n## Continuous Execution Mode\n\n\u003CIMPORTANT>\nHotfix workflow is **one-time continuous execution**. After invoking `\u002Fcomet-hotfix`, agent must automatically advance through hotfix steps, without pausing to wait for user input mid-way.\n\nException: when `.comet.yaml` has `auto_transition: false`, after each phase guard advances `phase`, do not auto-invoke the next skill. In this case, use `\"$COMET_BASH\" \"$COMET_STATE\" next \u003Cname>` output and pause for manual continuation as instructed.\n\nThe following situations must also pause and wait for user confirmation:\n\n1. Encountering upgrade conditions (see \"Upgrade Conditions\" section). **Must use the current platform's available user input\u002Fconfirmation mechanism to pause and wait for the user to explicitly confirm** upgrading to full workflow\n2. workspace isolation and execution-method selection when tasks exceed 3 and transfer to `\u002Fcomet-build`\n3. verify phase (comet-verify) verification-failure and branch-handling decisions\n4. Final archive confirmation (before comet-archive runs the archive script)\n\nExecution order: quick open → direct build → root cause check → verification → archive → complete\n\nAfter each step completes, immediately enter next step. Within each phase, must still call corresponding Comet\u002FOpenSpec\u002FSuperpowers skill according to above requirements; if the called skill has its own user decision points, follow that skill's rules.\n\u003C\u002FIMPORTANT>\n\n---\n\n## Upgrade Conditions\n\nUpgrade to full `\u002Fcomet` when **any** of the following conditions are met:\n\n| Condition | Explanation |\n|-----------|-------------|\n| Change involves **3+ files** | Exceeds single-point fix scope |\n| Architecture changes | New modules, new interfaces, new dependencies |\n| Database schema changes | Structural adjustments |\n| Introduces new public API | Fix creates new external interface |\n| Fix scope exceeds single function\u002Fmodule | Requires coordinated changes |\n\nWhen upgrade conditions are met, **must follow the `comet\u002Freference\u002Fdecision-point.md` protocol to pause and wait for the user to explicitly confirm** upgrading to the full `\u002Fcomet` workflow. Do not directly enter `\u002Fcomet-design`, and do not automatically supplement Design Doc.\n\nAfter user confirms upgrade, **must first update the workflow and phase fields** before entering full flow:\n\n```bash\n\"$COMET_BASH\" \"$COMET_STATE\" set \u003Cname> workflow full\n\"$COMET_BASH\" \"$COMET_STATE\" set \u003Cname> phase design\n```\n\nThen on current change basis, supplement Design Doc: **Immediately use the Skill tool to load the `comet-design` skill**, proceed normally with full workflow. If user does not confirm upgrade, stop hotfix and report that current change has exceeded hotfix scope.\n\n---\n\n## Exit Conditions\n\n- Bug fixed, tests pass\n- Change archived\n- If spec changes, synced to main spec\n- **Phase guard**: Before build → verify run `\"$COMET_BASH\" \"$COMET_GUARD\" \u003Cchange-name> build --apply`; before verify → archive follow `\u002Fcomet-verify` and run `\"$COMET_BASH\" \"$COMET_GUARD\" \u003Cchange-name> verify --apply`\n\n## Automatic Handoff to Next Phase\n\nFollow `comet\u002Freference\u002Fauto-transition.md`. Key command:\n\n```bash\n\"$COMET_BASH\" \"$COMET_STATE\" next \u003Cname>\n```\n\n- `NEXT: auto` → invoke the skill pointed to by `SKILL` to continue hotfix workflow (`phase: build` returns `comet-hotfix`, `verify` returns `comet-verify`, `archive` returns `comet-archive`)\n- `NEXT: manual` → do not invoke the next skill; prompt user to manually run `\u002F\u003CSKILL>` per `HINT`\n- `NEXT: done` → workflow is complete, no further action needed\n","# Comet Preset Path: Hotfix\n\nQuick bug fix workflow: open → build → verify → archive. Skip brainstorming and full plan, applicable for behavior fixes not involving new capability design.\n\n**Applicable conditions** (all must be met):\n1. Fix bugs in existing functionality, no new capability\n2. No interface changes or architecture adjustments\n3. Change scope is predictable (usually ≤ 2 files)\n\n**Not applicable**: If fix process discovers need for architecture adjustments, should upgrade to full `\u002Fcomet` workflow.\n\n---\n\n## Process (preset workflow, 6 steps)\n\n### 0. Output Language Constraint\n\nStreamlined OpenSpec artifacts must use the language of the user request that triggered this workflow.\n\nExecution chain: open → build → root cause check → verify → archive. Hotfix provides default decisions for each phase: streamlined open, direct build, root cause confirmation, scale-based verification, and final archive confirmation after verification passes.\n\nLocate Comet scripts before starting:\n\n```bash\nCOMET_ENV=\"${COMET_ENV:-$(find . \"$HOME\"\u002F.*\u002Fskills \"$HOME\u002F.config\" \"$HOME\u002F.gemini\" -path '*\u002Fcomet\u002Fscripts\u002Fcomet-env.sh' -type f -print -quit 2>\u002Fdev\u002Fnull)}\"\nif [ -z \"$COMET_ENV\" ]; then\n  echo \"ERROR: comet-env.sh not found. Ensure the comet skill is installed.\" >&2\n  return 1\nfi\n. \"$COMET_ENV\"\n```\n\n### 1. Quick Open (preset open)\n\nReuse Comet open capability to create change, but use hotfix defaults: do not execute `openspec-explore` long exploration, directly enter streamlined change creation.\n\n**Immediately execute:** Use the Skill tool to load the `openspec-new-change` skill. Skipping this step is prohibited.\n\nAfter the skill loads, follow its guidance to create streamlined artifacts:\n  - `proposal.md` — problem description + root cause analysis + fix goal (no solution comparison needed)\n  - `design.md` — fix solution (one is enough, no multi-solution comparison needed)\n  - `tasks.md` — fix task list\n- **No delta spec needed** (unless fix changes existing spec acceptance scenarios)\n\nInitialize Comet state file:\n\n```bash\n\"$COMET_BASH\" \"$COMET_STATE\" init \u003Cname> hotfix\n```\n\nVerify initialized state:\n\n```bash\n\"$COMET_BASH\" \"$COMET_STATE\" check \u003Cname> open\n```\n\nRun phase guard to transition open → build:\n\n```bash\n\"$COMET_BASH\" \"$COMET_GUARD\" \u003Cchange-name> open --apply\n```\n\nCheck `auto_transition` to decide whether to continue:\n\n```bash\n\"$COMET_BASH\" \"$COMET_STATE\" next \u003Cname>\n```\n\n- `NEXT: auto` → continue to Step 2\n- `NEXT: manual` → pause, follow `HINT` to prompt user to run `\u002F\u003CSKILL>` manually\n\n### 2. Direct Build (preset build)\n\nUse hotfix defaults: `build_mode: direct`. Skip Superpowers `brainstorming` and `writing-plans` (unless tasks > 3; if exceeds 3 tasks, transfer to `\u002Fcomet-build`'s plan and execution method selection — note this does NOT trigger full workflow upgrade, only switches execution method).\n\nBefore continuing or starting changes, handle uncommitted changes through `comet\u002Freference\u002Fdirty-worktree.md`. If attribution shows the fix scope exceeds hotfix, handle it through this file's \"Upgrade Conditions\".\n\n**Immediately execute:** Execute tasks one by one according to tasks.md:\n\n1. Read `openspec\u002Fchanges\u002F\u003Cname>\u002Ftasks.md`, get incomplete task list\n2. For each incomplete task:\n   - Modify code according to task description\n   - Run project formatter (e.g., `mvn spotless:apply`, `npm run format`)\n   - Run related tests to confirm pass\n   - Check corresponding `- [ ]` to `- [x]` in tasks.md\n   - Commit code, commit message format: `fix: \u003Cbrief fix description>`\n3. After all tasks complete, explicitly run relevant project tests and build commands\n\n**If fix affects existing spec acceptance scenarios**:\n- Create delta spec in `openspec\u002Fchanges\u002F\u003Cname>\u002Fspecs\u002F\u003Ccapability>\u002Fspec.md`\n- Only include `## MODIFIED Requirements` section\n\nDuring hotfix execution, whenever a crash, unexpected behavior, test failure, or build failure appears while running the program, tests, build, or manual verification, must use the Skill tool to load the Superpowers `systematic-debugging` skill. Before root-cause investigation is complete, must not propose or implement source-code fixes.\n\nFor specific investigation, minimal failing test, fix verification, and keeping the current change verification loop, follow `comet\u002Freference\u002Fdebug-gate.md`.\n\n### 3. Root Cause Elimination Check\n\n**Execute before running build guard**, ensuring the fix actually eliminates the root cause:\n\n1. Read bug description and root cause in proposal.md\n2. Search and verify problem code no longer exists\n3. If root cause not eliminated, return to Step 2 to continue fix (still in build phase, no state transition needed)\n\n**Upgrade conditions**:\n- Root cause check reveals deep architecture issues → Stop hotfix, handle per \"Upgrade Conditions\" section\n- Fix requires additional interface changes → Stop hotfix, handle per \"Upgrade Conditions\" section\n\nAfter root cause is confirmed eliminated, run phase guard to transition build → verify:\n\n```bash\n\"$COMET_BASH\" \"$COMET_GUARD\" \u003Cchange-name> build --apply\n```\n\nState automatically updates to `phase: verify`, `verify_result: pending`, then enter verification.\n\n### 4. Verification (preset verify)\n\nReuse `\u002Fcomet-verify`, with comet-verify's scale assessment deciding lightweight or full verification.\n\n**Immediately execute:** Use the Skill tool to load the `comet-verify` skill. Skipping this step is prohibited.\n\nSmall-scale hotfixes without delta spec usually meet lightweight verification conditions (≤ 3 tasks, ≤ 2 files), comet-verify's scale assessment will select the lightweight verification path (6 quick checks, including lightweight code review). If hotfix created delta spec, enter full verification path according to comet-verify's scale assessment rules.\n\nAfter verification passes, record `.comet.yaml` `verify_result` as `pass` according to `\u002Fcomet-verify` rules, must not skip this status before archiving. After verification passes, still enter `\u002Fcomet-archive`'s final archive confirmation; do not automatically run the archive script.\n\n### 5. Archive (preset archive)\n\nReuse `\u002Fcomet-archive`. Must satisfy `verify_result: pass` in `.comet.yaml` before archiving, and wait for `\u002Fcomet-archive`'s final archive confirmation.\n\n**Immediately execute:** Use the Skill tool to load the `comet-archive` skill to archive. Skipping this step is prohibited.\nIf there is delta spec, sync to main spec according to comet-archive rules, and handle associated Design Doc and Plan archiving annotations.\n\n---\n\n## Continuous Execution Mode\n\n\u003CIMPORTANT>\nHotfix workflow is **one-time continuous execution**. After invoking `\u002Fcomet-hotfix`, agent must automatically advance through hotfix steps, without pausing to wait for user input mid-way.\n\nException: when `.comet.yaml` has `auto_transition: false`, after each phase guard advances `phase`, do not auto-invoke the next skill. In this case, use `\"$COMET_BASH\" \"$COMET_STATE\" next \u003Cname>` output and pause for manual continuation as instructed.\n\nThe following situations must also pause and wait for user confirmation:\n\n1. Encountering upgrade conditions (see \"Upgrade Conditions\" section). **Must use the current platform's available user input\u002Fconfirmation mechanism to pause and wait for the user to explicitly confirm** upgrading to full workflow\n2. workspace isolation and execution-method selection when tasks exceed 3 and transfer to `\u002Fcomet-build`\n3. verify phase (comet-verify) verification-failure and branch-handling decisions\n4. Final archive confirmation (before comet-archive runs the archive script)\n\nExecution order: quick open → direct build → root cause check → verification → archive → complete\n\nAfter each step completes, immediately enter next step. Within each phase, must still call corresponding Comet\u002FOpenSpec\u002FSuperpowers skill according to above requirements; if the called skill has its own user decision points, follow that skill's rules.\n\u003C\u002FIMPORTANT>\n\n---\n\n## Upgrade Conditions\n\nUpgrade to full `\u002Fcomet` when **any** of the following conditions are met:\n\n| Condition | Explanation |\n|-----------|-------------|\n| Change involves **3+ files** | Exceeds single-point fix scope |\n| Architecture changes | New modules, new interfaces, new dependencies |\n| Database schema changes | Structural adjustments |\n| Introduces new public API | Fix creates new external interface |\n| Fix scope exceeds single function\u002Fmodule | Requires coordinated changes |\n\nWhen upgrade conditions are met, **must follow the `comet\u002Freference\u002Fdecision-point.md` protocol to pause and wait for the user to explicitly confirm** upgrading to the full `\u002Fcomet` workflow. Do not directly enter `\u002Fcomet-design`, and do not automatically supplement Design Doc.\n\nAfter user confirms upgrade, **must first update the workflow and phase fields** before entering full flow:\n\n```bash\n\"$COMET_BASH\" \"$COMET_STATE\" set \u003Cname> workflow full\n\"$COMET_BASH\" \"$COMET_STATE\" set \u003Cname> phase design\n```\n\nThen on current change basis, supplement Design Doc: **Immediately use the Skill tool to load the `comet-design` skill**, proceed normally with full workflow. If user does not confirm upgrade, stop hotfix and report that current change has exceeded hotfix scope.\n\n---\n\n## Exit Conditions\n\n- Bug fixed, tests pass\n- Change archived\n- If spec changes, synced to main spec\n- **Phase guard**: Before build → verify run `\"$COMET_BASH\" \"$COMET_GUARD\" \u003Cchange-name> build --apply`; before verify → archive follow `\u002Fcomet-verify` and run `\"$COMET_BASH\" \"$COMET_GUARD\" \u003Cchange-name> verify --apply`\n\n## Automatic Handoff to Next Phase\n\nFollow `comet\u002Freference\u002Fauto-transition.md`. Key command:\n\n```bash\n\"$COMET_BASH\" \"$COMET_STATE\" next \u003Cname>\n```\n\n- `NEXT: auto` → invoke the skill pointed to by `SKILL` to continue hotfix workflow (`phase: build` returns `comet-hotfix`, `verify` returns `comet-verify`, `archive` returns `comet-archive`)\n- `NEXT: manual` → do not invoke the next skill; prompt user to manually run `\u002F\u003CSKILL>` per `HINT`\n- `NEXT: done` → workflow is complete, no further action needed\n",{"name":5,"description":7},"master","a61a2e5b4766e1ad62377dec598e402560a259b6","eval\u002Flocal\u002Fskills\u002Fbenchmarks\u002F039-release\u002Fcomet-classic-039-hotfix",314,"https:\u002F\u002Fgithub.com\u002Frpamis\u002Fcomet","https:\u002F\u002Fdocs.comet.rpamis.com","https:\u002F\u002Fgithub.com\u002Frpamis","More Efficient, Easier to Use, and Less Annoying","2026-11-15 00:26:58",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add rpamis\u002Fcomet --skill comet-hotfix",{"tool":38,"command":39},"bunx","bunx skills add rpamis\u002Fcomet --skill comet-hotfix",{"tool":41,"command":42},"pnpm","pnpm dlx skills add rpamis\u002Fcomet --skill comet-hotfix","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frpamis\u002Fcomet\u002Fblob\u002Fmaster\u002Feval\u002Flocal\u002Fskills\u002Fbenchmarks\u002F039-release\u002Fcomet-classic-039-hotfix\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M72W3K6F0C2FKZ8DHABM49R7","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Frpamis\u002Fcomet\u002Fblob\u002Fmaster\u002Feval\u002Flocal\u002Fskills\u002Fbenchmarks\u002Fdependency\u002Fsuperpowers\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M72W3HCPQ3GVMACX61QJTD4B","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Frpamis\u002Fcomet\u002Fblob\u002Fmaster\u002Feval\u002Flocal\u002Fskills\u002Fbenchmarks\u002Fdependency\u002Fsuperpowers\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M72W3F8EVD3EK4NXJG40P84K","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Frpamis\u002Fcomet\u002Fblob\u002Fmaster\u002Feval\u002Flocal\u002Fskills\u002Fbenchmarks\u002Fdependency\u002Fsuperpowers\u002Fverification-before-completion\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M72W3CA9YM0Y6CSXXTNCV1CA","using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","https:\u002F\u002Fgithub.com\u002Frpamis\u002Fcomet\u002Fblob\u002Fmaster\u002Feval\u002Flocal\u002Fskills\u002Fbenchmarks\u002Fdependency\u002Fsuperpowers\u002Fusing-git-worktrees\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M72W3AEH0F548GTPRNYRR3H3","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002Frpamis\u002Fcomet\u002Fblob\u002Fmaster\u002Feval\u002Flocal\u002Fskills\u002Fbenchmarks\u002Fdependency\u002Fsuperpowers\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M72W38EN8NEKX1YN4W9G19Y2","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002Frpamis\u002Fcomet\u002Fblob\u002Fmaster\u002Feval\u002Flocal\u002Fskills\u002Fbenchmarks\u002Fdependency\u002Fsuperpowers\u002Fsystematic-debugging\u002FSKILL.md",[],[]]