[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ERV2X9PJXEBAX4SHJ85CS7":3,"skill-same:01M7ERV2X9PJXEBAX4SHJ85CS7":122},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7ERV2X9PJXEBAX4SHJ85CS7","do",null,"Route a task to one playbook (core or from a repo pack), state the pick, copy its steps into the task list and run them with proof and a learning check. Use for any engineering task in a git repository.","Ventorius\u002Fven-stack","Ventorius","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F5689509?v=4","01M7ERRDPQ5YXCNXJZWEKQNP50","Sebastian Basznianin","01M7ERRDQ9S0ZD9YMH1RN1WVP7",0,"MIT","https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fdo\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: do\ndescription: \"Route a task to one playbook (core or from a repo pack), state the pick, copy its steps into the task list and run them with proof and a learning check. Use for any engineering task in a git repository.\"\nmetadata:\n  layer: L5\n  source: cursor\u002Fplugins@1e5c90a:pstack\u002Fskills\u002Fpoteto-mode\u002FSKILL.md\n  license: MIT\n---\n\n# do\n\nThe task is what the user asked for.\n\nYou own the run. Pick one playbook, show the pick, copy its steps, run them in order, prove the result and close with a learning check. You think, decide and delegate; bulk edits go to agents.\n\n## 1. Read the repo state\n\n- A `ven-*` command is not found, or `ven-doctor` reports an ERROR: run **setup** first.\n- `ven-profile context`: the state directory, a stale profile, the active playbook and past solutions for the files this branch touches. Before editing a file, `ven-profile solutions-for \u003Cfiles>` lists the entries that cover it.\n- `ven-profile fresh` exits 1: name the manifests that changed and re-prove the commands they define (`ven-profile prove \u003Ckey>`) before relying on them, then `ven-profile stamp`.\n- `ven-decisions active` shows a playbook in this worktree: a task that continues it routes to **pickup**, a pause routes to **pause**. A new task while a playbook is active (running or paused) is not silent: ask the user, with a multiple-choice question when your agent has one, whether to finish, abandon or keep the old one paused, and record the answer. Close it with `ven-decisions end --outcome \u003Cdone|abandoned|blocked>` only on finish or abandon. A paused playbook keeps its state; run the new task in a separate worktree or branch, or after the pickup.\n- Commands come only from the profile, which fills in as work needs it. A command the task needs that is missing: find it in the repo (`ven-profile detect` lists manifests, CI and scripts), then `ven-profile learn \u003Ckey> --run '\u003Ccommand>' --evidence '\u003Cfile:line>'`, which runs it once and records whether it passed. A command with effects outside the repo, on tracked files, or that costs money: ask the user before it ever runs, and record it with `--manual \"\u003Creason>\"`. An `unverified` key: say so and don't rely on it.\n- A fact only a person knows (what is risky to touch, what proves a change type, what a domain word means): ask the user once, when a step first needs it, and store the answer (`ven-profile set risk_areas '\u003Clist as JSON>'`, `ven-profile set verify.\u003Cchange type> commands.\u003Ckey>`, a **glossary** entry). Never ask for these up front.\n\n## 2. Build the playbook list\n\n- `ven-profile playbooks` lists every core and pack playbook with its source, path and one-line description. Pick from that list; read a playbook file only once you've picked it.\n- Name the files the task touches (from the task, or a quick search) and run `ven-profile packs-for \u003Cfiles>`. Only those packs apply to this task. Read each returned pack skill file before working on those files, and log it once per task: `ven-decisions add --step pack-skill --decision \u003Cpack>:\u003Cskill>`.\n\n## 3. Pick\n\nMatch the task's shape, not its words. First match wins:\n\n1. The task names a ven skill to run (\"forge-pack \u003Cname>\", \"ratchet this\", \"diagram the deps\"): run that skill as a one-step sequence, then **learning-check**.\n2. A pack playbook whose description fits, from a pack that applies to the task's files. It beats a core playbook of the same shape because it carries the repo's specifics.\n3. A core playbook whose description fits.\n4. Nothing fits: compose an ad-hoc sequence (section 7).\n\nWhen two fit, take the one that asks more of the evidence. Close calls:\n\n- Broken, wrong or regressed → **bug-fix**, even when the fix looks like new behavior.\n- Same behavior, new structure → **refactor**. One mechanical change across many call sites → **migration**.\n- \"X got slower\": a baseline number exists or the user wants a speed target → **perf**; a functional break (timeouts, wrong results) → **bug-fix**. \"Is this slow?\" with nothing to measure → **investigation** first.\n- A question, no change → **investigation** when it asks a specific question and wants findings; **explain** when it teaches or builds understanding for a person (\"explain this PR\", \"teach me X\", \"walk me through\").\n- Production is down or erroring right now, user-facing, needs a fast fix → **hotfix**. A defect with no live fire → **bug-fix**.\n- A test that fails intermittently with no code change → **flaky-test**. A test that fails every time → **bug-fix**.\n- \"Can we do X?\", \"try it and tell me\", a throwaway experiment → **spike**.\n- Bump a dependency, runtime or toolchain version → **dependency-upgrade**. Swap one API or pattern across call sites → **migration**.\n- Only documentation files change → **docs-only**. Docs plus behavior → **feature**.\n- Spans several sessions with an unclear route → **epic**, even when no code changes yet: a chain of decisions to settle before building is epic, one question answered now is **investigation**. Decisions already settled → **feature**.\n- \"Run until done\" over existing tickets → **autonomous-run**. No spec or tickets yet → **feature**.\n- \"Continue\", \"pick up\" → **pickup**. \"Stop here\", \"pause\" → **pause**. \"Open a PR\", \"ship it\" → **ship**.\n\n## 4. Announce and record\n\nThe first line of your reply, exactly:\n\n`**Playbook: \u003Cname>** (core | pack \u003Cpack> | skill) — \u003Cone-line reason>`\n\nKeep that shape: `ven-transcripts` parses it to measure misroutes. Then:\n\n1. `ven-decisions start \u003Cname>`. Skip it for **pickup** and **pause** while a playbook is active: they work inside that playbook, and `start` would reset its recorded steps and the reproduce gate.\n2. Copy the playbook's steps verbatim into your task list (your agent's todo tool, or a checklist you keep in the reply), one task per step: the step line as the subject, its `Done:` line as the description. Task-specific tasks go after them, never instead of them.\n3. A step you won't run stays in the list as `skip: \u003Creason>` and is recorded with `ven-decisions skip --step \u003Cstep> --reason \"\u003Creason>\"`.\n4. After each step: `ven-decisions add --step \u003Cstep> --decision \"\u003Cone line>\" --evidence \"\u003Ccommand + exit code, or file:line>\"`. `\u003Cstep>` is the step's skill name, or its label when it names no skill.\n\n## 5. Run the steps\n\nIn order. A step's `Done:` line is its gate: the next step starts only when it holds, or after you record why it can't.\n\nDelegate by the ambiguity left, not by size, through **delegate**:\n\n| Work | Role |\n|---|---|\n| One ticket end to end, test-first | coder, in its own worktree, in the background |\n| A fully specified edit, or one slice of a fan-out | worker |\n| One review lens, blind to the others | reviewer |\n| Citation and proof checks | verifier |\n\n- Budget tier (`ven-profile config budget_tier`): `lean` lowers effort and skips optional panels; `max` raises effort.\n- A brief drops a tier only when complete, as **delegate** defines it. A brief that says \"decide\" or \"figure out\" stays with you. When you work on files a pack applies to, load that pack's skills yourself.\n- Parallelize independent work. Tickets follow the blocker graph (feature playbook); direct writes to the same files run in order.\n- Read every `VEN-RESULT` trailer. On `BLOCKED: \u003Cquestion>`, answer from the spec or the code, or ask the user if the call is theirs, then continue the same role (it keeps its worktree and context); never start a new one for the answer. Never let an agent guess. A coder's trailer carries `worktree:` and `branch:`; use them to merge.\n- You own what agents return. Read the diff and check the logged verify pass (`ven-decisions list`) before you merge a worktree; a trailer is a claim, not proof.\n- Ask the user only for calls that are theirs: product decisions, and irreversible or outward-facing actions (PRs, pushes, comments, tracker tickets, installs). Find facts yourself. Apply **never-block-on-reversible** to the rest.\n- Apply the principles in [references\u002Fprinciples.md](references\u002Fprinciples.md) when their trigger fits. Name each one that changed a decision in your reply, and the choice it changed.\n\n## 6. Review panels\n\nEach playbook declares `review: panel` or `review: own-read` in its own text. Feature and migration declare panel; refactor and perf declare panel only when a changed file matches a `risk_areas` glob (`ven-profile get risk_areas`); bug-fix, hotfix, docs-only and spike declare own-read. Budget tier `max` forces a panel. A risk-area match upgrades own-read to panel too. The budget tier never removes a panel from risky work.\n\nPanel: run **review**. Own-read: read the diff against the spec or ticket and record it with `ven-decisions add --step review`.\n\n## 6a. Small-task fast path\n\nA task that touches at most two files, has a known check command, and matches no `risk_areas` glob skips the per-step task-list items and the per-step `ven-decisions add` rows. It still runs `ven-decisions start`, **verify** (`ven-profile verify \u003Ckey>`), one **learning-check** row and `ven-decisions end`. Say `fast path` in the announce line's reason. A one-line bug fix with an obvious cause may skip diagram-hypotheses' three-cause minimum, never **reproduce**.\n\n## 7. No playbook fits\n\nCompose a one-off sequence from existing skill names only, ending with **learning-check**. State it as `**Playbook: ad-hoc** (composed) — \u003Creason>`, list the sequence on the next line, and run it like a playbook (`ven-decisions start ad-hoc`). If `ven-decisions list --playbook ad-hoc` shows the same shape before, suggest the \"forge-playbook\" skill to the user.\n\n## 8. Close\n\nThe last step is always **learning-check**. Then `ven-decisions end --outcome \u003Cdone|abandoned|blocked>`. After **pause**, skip `end`: the playbook stays active for the next pickup.\n\nReply: what changed and for whom, the evidence (verify keys and exit codes), skipped steps with reasons, and open decisions. Every claim carries its evidence, or is labeled inferred or guess.\n","# do\n\nThe task is what the user asked for.\n\nYou own the run. Pick one playbook, show the pick, copy its steps, run them in order, prove the result and close with a learning check. You think, decide and delegate; bulk edits go to agents.\n\n## 1. Read the repo state\n\n- A `ven-*` command is not found, or `ven-doctor` reports an ERROR: run **setup** first.\n- `ven-profile context`: the state directory, a stale profile, the active playbook and past solutions for the files this branch touches. Before editing a file, `ven-profile solutions-for \u003Cfiles>` lists the entries that cover it.\n- `ven-profile fresh` exits 1: name the manifests that changed and re-prove the commands they define (`ven-profile prove \u003Ckey>`) before relying on them, then `ven-profile stamp`.\n- `ven-decisions active` shows a playbook in this worktree: a task that continues it routes to **pickup**, a pause routes to **pause**. A new task while a playbook is active (running or paused) is not silent: ask the user, with a multiple-choice question when your agent has one, whether to finish, abandon or keep the old one paused, and record the answer. Close it with `ven-decisions end --outcome \u003Cdone|abandoned|blocked>` only on finish or abandon. A paused playbook keeps its state; run the new task in a separate worktree or branch, or after the pickup.\n- Commands come only from the profile, which fills in as work needs it. A command the task needs that is missing: find it in the repo (`ven-profile detect` lists manifests, CI and scripts), then `ven-profile learn \u003Ckey> --run '\u003Ccommand>' --evidence '\u003Cfile:line>'`, which runs it once and records whether it passed. A command with effects outside the repo, on tracked files, or that costs money: ask the user before it ever runs, and record it with `--manual \"\u003Creason>\"`. An `unverified` key: say so and don't rely on it.\n- A fact only a person knows (what is risky to touch, what proves a change type, what a domain word means): ask the user once, when a step first needs it, and store the answer (`ven-profile set risk_areas '\u003Clist as JSON>'`, `ven-profile set verify.\u003Cchange type> commands.\u003Ckey>`, a **glossary** entry). Never ask for these up front.\n\n## 2. Build the playbook list\n\n- `ven-profile playbooks` lists every core and pack playbook with its source, path and one-line description. Pick from that list; read a playbook file only once you've picked it.\n- Name the files the task touches (from the task, or a quick search) and run `ven-profile packs-for \u003Cfiles>`. Only those packs apply to this task. Read each returned pack skill file before working on those files, and log it once per task: `ven-decisions add --step pack-skill --decision \u003Cpack>:\u003Cskill>`.\n\n## 3. Pick\n\nMatch the task's shape, not its words. First match wins:\n\n1. The task names a ven skill to run (\"forge-pack \u003Cname>\", \"ratchet this\", \"diagram the deps\"): run that skill as a one-step sequence, then **learning-check**.\n2. A pack playbook whose description fits, from a pack that applies to the task's files. It beats a core playbook of the same shape because it carries the repo's specifics.\n3. A core playbook whose description fits.\n4. Nothing fits: compose an ad-hoc sequence (section 7).\n\nWhen two fit, take the one that asks more of the evidence. Close calls:\n\n- Broken, wrong or regressed → **bug-fix**, even when the fix looks like new behavior.\n- Same behavior, new structure → **refactor**. One mechanical change across many call sites → **migration**.\n- \"X got slower\": a baseline number exists or the user wants a speed target → **perf**; a functional break (timeouts, wrong results) → **bug-fix**. \"Is this slow?\" with nothing to measure → **investigation** first.\n- A question, no change → **investigation** when it asks a specific question and wants findings; **explain** when it teaches or builds understanding for a person (\"explain this PR\", \"teach me X\", \"walk me through\").\n- Production is down or erroring right now, user-facing, needs a fast fix → **hotfix**. A defect with no live fire → **bug-fix**.\n- A test that fails intermittently with no code change → **flaky-test**. A test that fails every time → **bug-fix**.\n- \"Can we do X?\", \"try it and tell me\", a throwaway experiment → **spike**.\n- Bump a dependency, runtime or toolchain version → **dependency-upgrade**. Swap one API or pattern across call sites → **migration**.\n- Only documentation files change → **docs-only**. Docs plus behavior → **feature**.\n- Spans several sessions with an unclear route → **epic**, even when no code changes yet: a chain of decisions to settle before building is epic, one question answered now is **investigation**. Decisions already settled → **feature**.\n- \"Run until done\" over existing tickets → **autonomous-run**. No spec or tickets yet → **feature**.\n- \"Continue\", \"pick up\" → **pickup**. \"Stop here\", \"pause\" → **pause**. \"Open a PR\", \"ship it\" → **ship**.\n\n## 4. Announce and record\n\nThe first line of your reply, exactly:\n\n`**Playbook: \u003Cname>** (core | pack \u003Cpack> | skill) — \u003Cone-line reason>`\n\nKeep that shape: `ven-transcripts` parses it to measure misroutes. Then:\n\n1. `ven-decisions start \u003Cname>`. Skip it for **pickup** and **pause** while a playbook is active: they work inside that playbook, and `start` would reset its recorded steps and the reproduce gate.\n2. Copy the playbook's steps verbatim into your task list (your agent's todo tool, or a checklist you keep in the reply), one task per step: the step line as the subject, its `Done:` line as the description. Task-specific tasks go after them, never instead of them.\n3. A step you won't run stays in the list as `skip: \u003Creason>` and is recorded with `ven-decisions skip --step \u003Cstep> --reason \"\u003Creason>\"`.\n4. After each step: `ven-decisions add --step \u003Cstep> --decision \"\u003Cone line>\" --evidence \"\u003Ccommand + exit code, or file:line>\"`. `\u003Cstep>` is the step's skill name, or its label when it names no skill.\n\n## 5. Run the steps\n\nIn order. A step's `Done:` line is its gate: the next step starts only when it holds, or after you record why it can't.\n\nDelegate by the ambiguity left, not by size, through **delegate**:\n\n| Work | Role |\n|---|---|\n| One ticket end to end, test-first | coder, in its own worktree, in the background |\n| A fully specified edit, or one slice of a fan-out | worker |\n| One review lens, blind to the others | reviewer |\n| Citation and proof checks | verifier |\n\n- Budget tier (`ven-profile config budget_tier`): `lean` lowers effort and skips optional panels; `max` raises effort.\n- A brief drops a tier only when complete, as **delegate** defines it. A brief that says \"decide\" or \"figure out\" stays with you. When you work on files a pack applies to, load that pack's skills yourself.\n- Parallelize independent work. Tickets follow the blocker graph (feature playbook); direct writes to the same files run in order.\n- Read every `VEN-RESULT` trailer. On `BLOCKED: \u003Cquestion>`, answer from the spec or the code, or ask the user if the call is theirs, then continue the same role (it keeps its worktree and context); never start a new one for the answer. Never let an agent guess. A coder's trailer carries `worktree:` and `branch:`; use them to merge.\n- You own what agents return. Read the diff and check the logged verify pass (`ven-decisions list`) before you merge a worktree; a trailer is a claim, not proof.\n- Ask the user only for calls that are theirs: product decisions, and irreversible or outward-facing actions (PRs, pushes, comments, tracker tickets, installs). Find facts yourself. Apply **never-block-on-reversible** to the rest.\n- Apply the principles in [references\u002Fprinciples.md](references\u002Fprinciples.md) when their trigger fits. Name each one that changed a decision in your reply, and the choice it changed.\n\n## 6. Review panels\n\nEach playbook declares `review: panel` or `review: own-read` in its own text. Feature and migration declare panel; refactor and perf declare panel only when a changed file matches a `risk_areas` glob (`ven-profile get risk_areas`); bug-fix, hotfix, docs-only and spike declare own-read. Budget tier `max` forces a panel. A risk-area match upgrades own-read to panel too. The budget tier never removes a panel from risky work.\n\nPanel: run **review**. Own-read: read the diff against the spec or ticket and record it with `ven-decisions add --step review`.\n\n## 6a. Small-task fast path\n\nA task that touches at most two files, has a known check command, and matches no `risk_areas` glob skips the per-step task-list items and the per-step `ven-decisions add` rows. It still runs `ven-decisions start`, **verify** (`ven-profile verify \u003Ckey>`), one **learning-check** row and `ven-decisions end`. Say `fast path` in the announce line's reason. A one-line bug fix with an obvious cause may skip diagram-hypotheses' three-cause minimum, never **reproduce**.\n\n## 7. No playbook fits\n\nCompose a one-off sequence from existing skill names only, ending with **learning-check**. State it as `**Playbook: ad-hoc** (composed) — \u003Creason>`, list the sequence on the next line, and run it like a playbook (`ven-decisions start ad-hoc`). If `ven-decisions list --playbook ad-hoc` shows the same shape before, suggest the \"forge-playbook\" skill to the user.\n\n## 8. Close\n\nThe last step is always **learning-check**. Then `ven-decisions end --outcome \u003Cdone|abandoned|blocked>`. After **pause**, skip `end`: the playbook stays active for the next pickup.\n\nReply: what changed and for whom, the evidence (verify keys and exit codes), skipped steps with reasons, and open decisions. Every claim carries its evidence, or is labeled inferred or guess.\n",{"name":5,"metadata":24,"description":7},{"layer":25,"source":26,"license":15},"L5","cursor\u002Fplugins@1e5c90a:pstack\u002Fskills\u002Fpoteto-mode\u002FSKILL.md","main","e57e3dd5c8aec0fe40658397aee9fd9b1d77bb60","plugins\u002Fven\u002Fskills\u002Fdo","https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack","https:\u002F\u002Fgithub.com\u002FVentorius","Heavy testing believer. Workflow automation fan. Fullstack JS developer.","2026-11-04 04:05:46",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Ventorius\u002Fven-stack --skill do",{"tool":40,"command":41},"bunx","bunx skills add Ventorius\u002Fven-stack --skill do",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Ventorius\u002Fven-stack --skill do","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fdo\u002FSKILL.md",true,[48,54,58,62,66,70,74,78,82,86,90,94,98,102,106,110,114,118],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"playbooks\u002Fautonomous-run.md","REFERENCE","参考文档",2305,"https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fdo\u002Fplaybooks\u002Fautonomous-run.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"playbooks\u002Fbug-fix.md",2179,"https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fdo\u002Fplaybooks\u002Fbug-fix.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"playbooks\u002Fdependency-upgrade.md",1830,"https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fdo\u002Fplaybooks\u002Fdependency-upgrade.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"playbooks\u002Fdocs-only.md",1502,"https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fdo\u002Fplaybooks\u002Fdocs-only.md",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"playbooks\u002Fepic.md",2181,"https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fdo\u002Fplaybooks\u002Fepic.md",{"path":71,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":72,"sourceHtmlUrl":73},"playbooks\u002Fexplain.md",761,"https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fdo\u002Fplaybooks\u002Fexplain.md",{"path":75,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":76,"sourceHtmlUrl":77},"playbooks\u002Ffeature.md",2245,"https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fdo\u002Fplaybooks\u002Ffeature.md",{"path":79,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":80,"sourceHtmlUrl":81},"playbooks\u002Fflaky-test.md",1767,"https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fdo\u002Fplaybooks\u002Fflaky-test.md",{"path":83,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":84,"sourceHtmlUrl":85},"playbooks\u002Fhotfix.md",1940,"https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fdo\u002Fplaybooks\u002Fhotfix.md",{"path":87,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":88,"sourceHtmlUrl":89},"playbooks\u002Finvestigation.md",1524,"https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fdo\u002Fplaybooks\u002Finvestigation.md",{"path":91,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":92,"sourceHtmlUrl":93},"playbooks\u002Fmigration.md",1485,"https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fdo\u002Fplaybooks\u002Fmigration.md",{"path":95,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":96,"sourceHtmlUrl":97},"playbooks\u002Fpause.md",1548,"https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fdo\u002Fplaybooks\u002Fpause.md",{"path":99,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":100,"sourceHtmlUrl":101},"playbooks\u002Fperf.md",1844,"https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fdo\u002Fplaybooks\u002Fperf.md",{"path":103,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":104,"sourceHtmlUrl":105},"playbooks\u002Fpickup.md",1570,"https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fdo\u002Fplaybooks\u002Fpickup.md",{"path":107,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":108,"sourceHtmlUrl":109},"playbooks\u002Frefactor.md",1786,"https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fdo\u002Fplaybooks\u002Frefactor.md",{"path":111,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":112,"sourceHtmlUrl":113},"playbooks\u002Fship.md",1801,"https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fdo\u002Fplaybooks\u002Fship.md",{"path":115,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":116,"sourceHtmlUrl":117},"playbooks\u002Fspike.md",1304,"https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fdo\u002Fplaybooks\u002Fspike.md",{"path":119,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":120,"sourceHtmlUrl":121},"references\u002Fprinciples.md",1763,"https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fdo\u002Freferences\u002Fprinciples.md",[123,130,137,144,151,158],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":19},"01M7ES1P06ZPAGTT7YS4V6MS32","yeet","Take every local change green through the repo's own checks, slice it into conventional commits, push, and with --pr open a pull request on the code host. Use only when the user explicitly asks to yeet, or to commit and push everything; never on your own initiative.","https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":19},"01M7ES1JHVQEN3YYMRZEBM2E79","write-docs","Write or update documentation from the code: gather facts, pick the shape for the reader, write it plain, and prove every command and path in it. Use when asked to document a repo, module or feature, or to bring stale docs up to date.","https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fwrite-docs\u002FSKILL.md",[],[],{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":19},"01M7ES1DD3YVMF1MY7D51R6516","why","Find why code is shaped the way it is (design rationale, trade-offs, regressions, odd thresholds) from history, tickets, docs and chat, citing every claim and stating its confidence. Use for 'why does X work this way', 'why did we pick Y', or before changing code whose purpose is unclear.","https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":19},"01M7ES18XVRZGQ0V1BBZH63Q8W","verify","Prove a change works with the check that matches its type, do the read-back, and log the pass against the exact tree. Use when a change is ready to call done, before review, commit or stopping, and whenever ven-decisions end refuses an unverified tree.","https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fverify\u002FSKILL.md",[],[],{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":19},"01M7ES15Z3W8QTJH4CRAJ53D2G","unslop","Cut AI writing tells (filler, model vocabulary, metaphor nouns, hedging, formatting tics) from text while keeping every fact. Use when editing or checking any prose before it ships: docs, PR bodies, reports, skill text.","https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"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":164,"publishedAt":19},"01M7ES12GT9WD9NE2X3M1B29ZZ","type-discipline","Apply when designing types or data shapes, reviewing a signature, or handling outside data, in any language. Make wrong states fail early: in the compiler for typed languages, in validated runtime contracts for untyped ones.","https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Ftype-discipline\u002FSKILL.md",[],[]]