[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M787HTE89T0KDRHRQJ06TFKS":3,"skill-same:01M787HTE89T0KDRHRQJ06TFKS":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"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":13,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M787HTE89T0KDRHRQJ06TFKS","tasks",null,"Creates and tracks a vibe workflow's task list and keeps it up to date until the end — through the native task system (TaskCreate \u002F TaskUpdate \u002F TaskList \u002F TaskGet) when it is available, otherwise through a `tasks.tsv` file in the scratchpad, kept by a script that reproduces the same model (ids, statuses, blockedBy dependencies, owner). Invoked internally by other vibe skills, never directly by users.","neolao\u002Fclaude-plugin-vibe","neolao","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F149506?v=4","01M787F66EN3C5HEKZCY53VPY8","01M787F67MZYM53GYFZWR4M59E",0,"MIT","https:\u002F\u002Fgithub.com\u002Fneolao\u002Fclaude-plugin-vibe\u002Fblob\u002Fmain\u002Fskills\u002Ftasks\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: tasks\ndescription: Creates and tracks a vibe workflow's task list and keeps it up to date until the end — through the native task system (TaskCreate \u002F TaskUpdate \u002F TaskList \u002F TaskGet) when it is available, otherwise through a `tasks.tsv` file in the scratchpad, kept by a script that reproduces the same model (ids, statuses, blockedBy dependencies, owner). Invoked internally by other vibe skills, never directly by users.\nargument-hint: \"[file: \u003Cpath>] then \u003Cone task per line: '\u003Csubject> ← blockedBy \\\"\u003Cother subject>\\\"' or '\u003Csubject> ← no dependency'>\"\nuser-invocable: false\nversion: 2.2.0\nmodel: claude-sonnet-5-5\n---\n\n# vibe:tasks — Task List Creation & Tracking\n\n## Golden rule\nA task list kept up to date at every transition, with the same model and the same rules whether the native task system is available or not. The fallback is not a degraded version: it is the same system, stored in a file.\n\n## Input\n- Invoked by another `vibe:*` skill, once per workflow run, right after that skill's plan is approved: `$ARGUMENTS` is the list to create, one task per line, subject ≤ 30 chars, each with its `blockedBy` dependency or `no dependency`.\n- Loaded without a caller's list: split the requested work yourself into tasks of this format before creating them. Subject in the imperative (\"Write tests\"), `activeForm` in the progressive form (\"Writing tests\").\n- Option `file: \u003Cpath>`, on the first line of `$ARGUMENTS`, before the tasks: the list file in fallback mode. An absolute path is taken as is; a relative path is resolved from the scratchpad (`file: tasks-review.tsv` → `\u003Cscratchpad>\u002Ftasks-review.tsv`). Without this line, the file is `\u003Cscratchpad>\u002Ftasks.tsv`. Without a scratchpad indicated, a relative path resolves from the current working directory (see \"Fallback file\"). The script always receives the absolute path resolved this way, never the relative one. In native mode the option is ignored: say so before the first `TaskCreate`, with this sentence: \"Option `file:` ignored: the native task system is available.\"\n- If the list already exists (native: `TaskList` not empty; fallback: the chosen file is present), do not recreate it: append the new tasks to it.\n\n## Detection\nThe native system is available if `TaskCreate` is in your tool list **or** if it loads through `ToolSearch` with the query `select:TaskCreate,TaskUpdate,TaskList,TaskGet`. A deferred tool is not a missing tool: conclude it is missing only after that `ToolSearch`. Detection happens once; the chosen mode holds for the whole session.\n\n## Fallback file\nThe file is the one chosen at input (by default `tasks.tsv` in the scratchpad directory your system prompt indicates); the announcement quotes it as an absolute path. If your system prompt indicates no scratchpad and the path is not absolute (default or relative `file:`): ask for the location with **AskUserQuestion** (recommended option: the current working directory), never `\u002Ftmp` by default; if **AskUserQuestion** is not available, take the current working directory and append to the announcement \"(no scratchpad indicated: path resolved from the current directory)\".\n\n## Create the tasks\n**Native mode**: create every task in order with `TaskCreate` (`subject`, `description`, `activeForm`), then chain the dependencies with `TaskUpdate` (`addBlockedBy`) exactly as given. Finish by showing the list (`TaskList`).\n\n**Fallback mode**: the native system is missing. Pick the mode: by the script if the Bash tool is in your tool list, by hand otherwise. Then run these steps in order, skipping none:\n1. **Creation**, following the chosen mode below, then show the list (`list`).\n2. **Announcement**, in visible text: the user does not read your reasoning, an announcement that only appears there has not been made. It opens the message of your first `●` line, right above it (if you already wrote it before the creation, do not repeat it):\n\n   ```\n   The native task system is not available in this environment — I track the tasks in `\u003Cabsolute path of the file>`, with the same model, through the script.\n   ● \u003CactiveForm of the first task>\n   ```\n\n   The sentence is copied word for word, without rephrasing, with the addition \"(no scratchpad indicated: path resolved from the current directory)\" when \"Fallback file\" requires it. In manual mode, replace \"through the script\" with \"by hand (\u003Creason>)\".\n3. **Reminder**: your final answer opens with the same sentence, addition included, word for word. That is where the user looks for the path of the list.\n\n**Through the script**: every operation goes through `scripts\u002Ftasks.sh`, one Bash call per creation or transition. Its absolute path is the \"Base directory for this skill\" line shown at the top of this skill, followed by `\u002Fscripts\u002Ftasks.sh`. Always run it with `sh`, writing in full in every call the path of the script and the path of the file: never a shell variable (`F=… ; S=…`), which an allow rule `Bash(sh *\u002Fskills\u002Ftasks\u002Fscripts\u002Ftasks.sh:*)` would not recognize:\n\n```\nsh \u003Cbase>\u002Fscripts\u002Ftasks.sh \u003Cfile> create --subject \"…\" --active-form \"…\" --description \"…\" [--blocked-by 1,2]\nsh \u003Cbase>\u002Fscripts\u002Ftasks.sh \u003Cfile> update \u003Cid> --status in_progress|completed|pending|deleted [--owner …] [--add-blocked-by …] [--add-blocks …]\nsh \u003Cbase>\u002Fscripts\u002Ftasks.sh \u003Cfile> drop-pending\nsh \u003Cbase>\u002Fscripts\u002Ftasks.sh \u003Cfile> list\nsh \u003Cbase>\u002Fscripts\u002Ftasks.sh \u003Cfile> get \u003Cid>\n```\n\nCreate the tasks in order: `create` returns `ok #\u003Cid> created`, and that id is the one you pass to `--blocked-by` for the next ones. The script refuses what the rules below forbid (exit 1, message `refused: …`, file unchanged). A refusal signals an error on your side: fix the sequence, for example move the task to `in_progress` before `completed`. Never work around a refusal by editing the file by hand. The details are in [references\u002Fmodel.md](references\u002Fmodel.md).\n\n**By hand**: only if the script cannot run (no Bash, call refused, for example in a non-interactive session, or execution error). You then keep the same file yourself, following the manual operations of [references\u002Fmodel.md](references\u002Fmodel.md). Each transition edits a single line (`Edit`), and you enforce the script's refusals yourself.\n\n## Rules, identical in both modes\n1. Only one task `in_progress` at a time.\n2. Move a task to `in_progress` **before** starting the work it describes, not after. Never `pending` to `completed` directly.\n3. Do not start a task whose `blockedBy` is not `completed`.\n4. Move to `completed` only when the work is entirely done. Failing tests, partial work, unresolved error: the task stays `in_progress` and you create a task for the blocker.\n5. After each `completed`, reread the list (`TaskList` or `list`) and take the unblocked `pending` task with the lowest id.\n6. A task that has become pointless goes `deleted`; it does not stay `pending` indefinitely.\n7. A task discovered along the way is created the moment it appears, not reconstructed at the end.\n\n## Standing instruction for the rest of this session\nOnce this skill has run, every status transition goes through `TaskUpdate` (native), through `tasks.sh update` (fallback, script) or through editing the task's line (fallback, by hand). Every transition comes with one compact status line in your reply:\n- `● \u003CactiveForm>` on the transition to `in_progress`;\n- `✓ \u003Csubject>` on the transition to `completed`, followed by ` — \u003Cconcrete detail>` when one exists (commit hash, test count) — nothing restated.\n\nThe status line reports a transition already recorded, it does not replace it: the call comes first, the line second. This also holds for `in_progress`, even when the task fits in a single action. No transition is silent: a `completed` or an `in_progress` directly followed by another tool call, without its line in your message, is an error, even when several tasks follow each other (one `✓` line per completed task).\n\nThese lines are text of your reply: the user does not read your reasoning, a line that only appears there has not been written. Prose belongs in the final report, not in these lines. Do not re-invoke this skill for an update: this instruction covers them until the end of the session.\n\n## Going back\nA workflow that loops sometimes returns to a step already done (a finding sends it back to planning, for example). The list is then updated in this order:\n1. The current task (the one that triggered the return, often the review) goes `completed`: it did happen.\n2. Every `pending` task is now stale and goes `deleted`: `drop-pending` through the script, or one `deleted` transition per task (`TaskUpdate`, or `Edit` by hand), lowest id first. Never delete a `completed` task: it is the trace of the previous round.\n3. The tasks of the new round are created with the prefix `Round \u003Cn> — ` in their subject (`Round 2 — Plan`), chained by their dependencies. The first round has no prefix.\n\nEach transition keeps its status line (`✓` for the completed task), and each deletion is announced on one line: `✗ \u003Csubject> — stale` (the subject comes from `drop-pending`'s own output, or from the list read before deleting).\n\n## Resume\nAfter a `\u002Fcompact`, an interruption or at the start of a new turn, reread the state before any action: `TaskList`, or `tasks.sh \u003Cfile> list` (the whole file in manual mode). The file path is in the fallback announcement and in your final answers. Do not rely on what remains of the conversation: a `completed` task summarized by the compaction could be redone, an `in_progress` task forgotten.\n\n## Separate lists\nThe skill does not know who calls it: a sub-agent shares the session's scratchpad, has no `TaskCreate` and receives no identifier of its own. Choosing a separate list is therefore up to the caller.\n- The main agent uses the default file.\n- An agent that wants a list of its own — a sub-agent, or an orchestrator that dedicates a list to a mission — passes `file:`.\n- Without the option, two agents of the same session share `tasks.tsv`; avoiding that is up to the caller. The script locks the file during each write, so two agents sharing a list lose no write, but they mix their tasks.\n- Never write in the file of a list you do not keep. You may read it if you are given its path; the `owner` field records the agent in charge of a task.\n","# vibe:tasks — Task List Creation & Tracking\n\n## Golden rule\nA task list kept up to date at every transition, with the same model and the same rules whether the native task system is available or not. The fallback is not a degraded version: it is the same system, stored in a file.\n\n## Input\n- Invoked by another `vibe:*` skill, once per workflow run, right after that skill's plan is approved: `$ARGUMENTS` is the list to create, one task per line, subject ≤ 30 chars, each with its `blockedBy` dependency or `no dependency`.\n- Loaded without a caller's list: split the requested work yourself into tasks of this format before creating them. Subject in the imperative (\"Write tests\"), `activeForm` in the progressive form (\"Writing tests\").\n- Option `file: \u003Cpath>`, on the first line of `$ARGUMENTS`, before the tasks: the list file in fallback mode. An absolute path is taken as is; a relative path is resolved from the scratchpad (`file: tasks-review.tsv` → `\u003Cscratchpad>\u002Ftasks-review.tsv`). Without this line, the file is `\u003Cscratchpad>\u002Ftasks.tsv`. Without a scratchpad indicated, a relative path resolves from the current working directory (see \"Fallback file\"). The script always receives the absolute path resolved this way, never the relative one. In native mode the option is ignored: say so before the first `TaskCreate`, with this sentence: \"Option `file:` ignored: the native task system is available.\"\n- If the list already exists (native: `TaskList` not empty; fallback: the chosen file is present), do not recreate it: append the new tasks to it.\n\n## Detection\nThe native system is available if `TaskCreate` is in your tool list **or** if it loads through `ToolSearch` with the query `select:TaskCreate,TaskUpdate,TaskList,TaskGet`. A deferred tool is not a missing tool: conclude it is missing only after that `ToolSearch`. Detection happens once; the chosen mode holds for the whole session.\n\n## Fallback file\nThe file is the one chosen at input (by default `tasks.tsv` in the scratchpad directory your system prompt indicates); the announcement quotes it as an absolute path. If your system prompt indicates no scratchpad and the path is not absolute (default or relative `file:`): ask for the location with **AskUserQuestion** (recommended option: the current working directory), never `\u002Ftmp` by default; if **AskUserQuestion** is not available, take the current working directory and append to the announcement \"(no scratchpad indicated: path resolved from the current directory)\".\n\n## Create the tasks\n**Native mode**: create every task in order with `TaskCreate` (`subject`, `description`, `activeForm`), then chain the dependencies with `TaskUpdate` (`addBlockedBy`) exactly as given. Finish by showing the list (`TaskList`).\n\n**Fallback mode**: the native system is missing. Pick the mode: by the script if the Bash tool is in your tool list, by hand otherwise. Then run these steps in order, skipping none:\n1. **Creation**, following the chosen mode below, then show the list (`list`).\n2. **Announcement**, in visible text: the user does not read your reasoning, an announcement that only appears there has not been made. It opens the message of your first `●` line, right above it (if you already wrote it before the creation, do not repeat it):\n\n   ```\n   The native task system is not available in this environment — I track the tasks in `\u003Cabsolute path of the file>`, with the same model, through the script.\n   ● \u003CactiveForm of the first task>\n   ```\n\n   The sentence is copied word for word, without rephrasing, with the addition \"(no scratchpad indicated: path resolved from the current directory)\" when \"Fallback file\" requires it. In manual mode, replace \"through the script\" with \"by hand (\u003Creason>)\".\n3. **Reminder**: your final answer opens with the same sentence, addition included, word for word. That is where the user looks for the path of the list.\n\n**Through the script**: every operation goes through `scripts\u002Ftasks.sh`, one Bash call per creation or transition. Its absolute path is the \"Base directory for this skill\" line shown at the top of this skill, followed by `\u002Fscripts\u002Ftasks.sh`. Always run it with `sh`, writing in full in every call the path of the script and the path of the file: never a shell variable (`F=… ; S=…`), which an allow rule `Bash(sh *\u002Fskills\u002Ftasks\u002Fscripts\u002Ftasks.sh:*)` would not recognize:\n\n```\nsh \u003Cbase>\u002Fscripts\u002Ftasks.sh \u003Cfile> create --subject \"…\" --active-form \"…\" --description \"…\" [--blocked-by 1,2]\nsh \u003Cbase>\u002Fscripts\u002Ftasks.sh \u003Cfile> update \u003Cid> --status in_progress|completed|pending|deleted [--owner …] [--add-blocked-by …] [--add-blocks …]\nsh \u003Cbase>\u002Fscripts\u002Ftasks.sh \u003Cfile> drop-pending\nsh \u003Cbase>\u002Fscripts\u002Ftasks.sh \u003Cfile> list\nsh \u003Cbase>\u002Fscripts\u002Ftasks.sh \u003Cfile> get \u003Cid>\n```\n\nCreate the tasks in order: `create` returns `ok #\u003Cid> created`, and that id is the one you pass to `--blocked-by` for the next ones. The script refuses what the rules below forbid (exit 1, message `refused: …`, file unchanged). A refusal signals an error on your side: fix the sequence, for example move the task to `in_progress` before `completed`. Never work around a refusal by editing the file by hand. The details are in [references\u002Fmodel.md](references\u002Fmodel.md).\n\n**By hand**: only if the script cannot run (no Bash, call refused, for example in a non-interactive session, or execution error). You then keep the same file yourself, following the manual operations of [references\u002Fmodel.md](references\u002Fmodel.md). Each transition edits a single line (`Edit`), and you enforce the script's refusals yourself.\n\n## Rules, identical in both modes\n1. Only one task `in_progress` at a time.\n2. Move a task to `in_progress` **before** starting the work it describes, not after. Never `pending` to `completed` directly.\n3. Do not start a task whose `blockedBy` is not `completed`.\n4. Move to `completed` only when the work is entirely done. Failing tests, partial work, unresolved error: the task stays `in_progress` and you create a task for the blocker.\n5. After each `completed`, reread the list (`TaskList` or `list`) and take the unblocked `pending` task with the lowest id.\n6. A task that has become pointless goes `deleted`; it does not stay `pending` indefinitely.\n7. A task discovered along the way is created the moment it appears, not reconstructed at the end.\n\n## Standing instruction for the rest of this session\nOnce this skill has run, every status transition goes through `TaskUpdate` (native), through `tasks.sh update` (fallback, script) or through editing the task's line (fallback, by hand). Every transition comes with one compact status line in your reply:\n- `● \u003CactiveForm>` on the transition to `in_progress`;\n- `✓ \u003Csubject>` on the transition to `completed`, followed by ` — \u003Cconcrete detail>` when one exists (commit hash, test count) — nothing restated.\n\nThe status line reports a transition already recorded, it does not replace it: the call comes first, the line second. This also holds for `in_progress`, even when the task fits in a single action. No transition is silent: a `completed` or an `in_progress` directly followed by another tool call, without its line in your message, is an error, even when several tasks follow each other (one `✓` line per completed task).\n\nThese lines are text of your reply: the user does not read your reasoning, a line that only appears there has not been written. Prose belongs in the final report, not in these lines. Do not re-invoke this skill for an update: this instruction covers them until the end of the session.\n\n## Going back\nA workflow that loops sometimes returns to a step already done (a finding sends it back to planning, for example). The list is then updated in this order:\n1. The current task (the one that triggered the return, often the review) goes `completed`: it did happen.\n2. Every `pending` task is now stale and goes `deleted`: `drop-pending` through the script, or one `deleted` transition per task (`TaskUpdate`, or `Edit` by hand), lowest id first. Never delete a `completed` task: it is the trace of the previous round.\n3. The tasks of the new round are created with the prefix `Round \u003Cn> — ` in their subject (`Round 2 — Plan`), chained by their dependencies. The first round has no prefix.\n\nEach transition keeps its status line (`✓` for the completed task), and each deletion is announced on one line: `✗ \u003Csubject> — stale` (the subject comes from `drop-pending`'s own output, or from the list read before deleting).\n\n## Resume\nAfter a `\u002Fcompact`, an interruption or at the start of a new turn, reread the state before any action: `TaskList`, or `tasks.sh \u003Cfile> list` (the whole file in manual mode). The file path is in the fallback announcement and in your final answers. Do not rely on what remains of the conversation: a `completed` task summarized by the compaction could be redone, an `in_progress` task forgotten.\n\n## Separate lists\nThe skill does not know who calls it: a sub-agent shares the session's scratchpad, has no `TaskCreate` and receives no identifier of its own. Choosing a separate list is therefore up to the caller.\n- The main agent uses the default file.\n- An agent that wants a list of its own — a sub-agent, or an orchestrator that dedicates a list to a mission — passes `file:`.\n- Without the option, two agents of the same session share `tasks.tsv`; avoiding that is up to the caller. The script locks the file during each write, so two agents sharing a list lose no write, but they mix their tasks.\n- Never write in the file of a list you do not keep. You may read it if you are given its path; the `owner` field records the agent in charge of a task.\n",{"name":5,"model":23,"version":24,"description":7,"argument-hint":25,"user-invocable":19},"claude-sonnet-5-5","2.2.0","[file: \u003Cpath>] then \u003Cone task per line: '\u003Csubject> ← blockedBy \"\u003Cother subject>\"' or '\u003Csubject> ← no dependency'>","main","0c226fd01e28e24c34766470e441e4efd4277884","skills\u002Ftasks","https:\u002F\u002Fgithub.com\u002Fneolao\u002Fclaude-plugin-vibe","https:\u002F\u002Fgithub.com\u002Fneolao","https:\u002F\u002Fneolao.com","Fullstack developer","2026-11-13 00:19:16",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add neolao\u002Fclaude-plugin-vibe --skill tasks",{"tool":40,"command":41},"bunx","bunx skills add neolao\u002Fclaude-plugin-vibe --skill tasks",{"tool":43,"command":44},"pnpm","pnpm dlx skills add neolao\u002Fclaude-plugin-vibe --skill tasks","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fneolao\u002Fclaude-plugin-vibe\u002Fblob\u002Fmain\u002Fskills\u002Ftasks\u002FSKILL.md",true,[48,54],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fmodel.md","REFERENCE","参考文档",4423,"https:\u002F\u002Fgithub.com\u002Fneolao\u002Fclaude-plugin-vibe\u002Fblob\u002Fmain\u002Fskills\u002Ftasks\u002Freferences\u002Fmodel.md",{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"scripts\u002Ftasks.sh","SCRIPT","脚本",8588,"https:\u002F\u002Fgithub.com\u002Fneolao\u002Fclaude-plugin-vibe\u002Fblob\u002Fmain\u002Fskills\u002Ftasks\u002Fscripts\u002Ftasks.sh",[61,68,75,82,88,95],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M787J4AMQXRM16BMVK98TYND","workspace-init","Set up or refresh a multi-repo workspace from the parent folder of its sibling repos — the hub repo (repos registry, cross-repo backlog and decisions) that \u002Fvibe:next-task reads, and the local, untracked workspace-root CLAUDE.md that indexes the hub and the siblings","https:\u002F\u002Fgithub.com\u002Fneolao\u002Fclaude-plugin-vibe\u002Fblob\u002Fmain\u002Fskills\u002Fworkspace-init\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M787J00GMM26BJ88M38T1FE4","usage-report","Usage report of a vibe workflow: counts, while the work runs, the bricks called, the loop rounds, the findings, the questions asked to the user and the fixes, then writes these statistics to `.vibe\u002Fusage-reports\u002F` in the project at the end. Invoked by `vibe:feature` and `vibe:fix` through their shared workflow, at the start of the work and at the end. Never triggered by a user request.","https:\u002F\u002Fgithub.com\u002Fneolao\u002Fclaude-plugin-vibe\u002Fblob\u002Fmain\u002Fskills\u002Fusage-report\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M787HQPZHQZT9CGPRT1QM3V7","sync","Sync .vibe\u002F — generate on first run, incrementally update on subsequent runs","https:\u002F\u002Fgithub.com\u002Fneolao\u002Fclaude-plugin-vibe\u002Fblob\u002Fmain\u002Fskills\u002Fsync\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M787HP2484TER1ZEMM7HSVJV","rewrite","https:\u002F\u002Fgithub.com\u002Fneolao\u002Fclaude-plugin-vibe\u002Fblob\u002Fmain\u002Fskills\u002Frewrite\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M787HH252DZHDHJF70DYAQ7A","review","Runs the project's active review agents on a scope and returns their raw findings — one owner per dimension, the shared finding contract injected into every prompt — without judging, fixing or committing anything. Invoked by the build workflow (`vibe:feature`, `vibe:fix`) as its internal review step and by `vibe:audit`, never directly by users.","https:\u002F\u002Fgithub.com\u002Fneolao\u002Fclaude-plugin-vibe\u002Fblob\u002Fmain\u002Fskills\u002Freview\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M787HD4F6Y7ESC3PHJAJHK04","release","Create a versioned release — bump version, finalize CHANGELOG.md, commit and tag","https:\u002F\u002Fgithub.com\u002Fneolao\u002Fclaude-plugin-vibe\u002Fblob\u002Fmain\u002Fskills\u002Frelease\u002FSKILL.md",[],[]]