[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M759FP17VXKX89DQB65GWE3R":3,"skill-same:01M759FP17VXKX89DQB65GWE3R":62},{"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":32,"commitSha":33,"skillDirectory":34,"forksCount":14,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":37,"install":38,"resources":51},"01M759FP17VXKX89DQB65GWE3R","gate-close",null,"Close a landed change into ONE owner-decision packet before any governed-doc status advances. Use whenever CODE HAS LANDED and one or more PRD\u002FRFC\u002FADR\u002FUS docs are candidates to move status, or when the user says \"close this slice\", \"prep the flips\", \"ready to flip\". For a single doc with NO code landed yet (a draft heading to proposed\u002Faccepted), use spec-red-team instead — gate-close already contains a red team per flip.","baodq97\u002Fgovkit","baodq97","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F50482002?v=4","01M759BJ9XC68CW9PQCFK22H1X","Bao Do","01M759BJAY1W696G8A8N841875",0,"MIT","https:\u002F\u002Fgithub.com\u002Fbaodq97\u002Fgovkit\u002Fblob\u002Fmain\u002Fplugins\u002Fswe-flow\u002Fskills\u002Fgate-close\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: gate-close\ndescription: >-\n  Close a landed change into ONE owner-decision packet before any governed-doc status advances.\n  Use whenever CODE HAS LANDED and one or more PRD\u002FRFC\u002FADR\u002FUS docs are candidates to move\n  status, or when the user says \"close this slice\", \"prep the flips\", \"ready to flip\". For a\n  single doc with NO code landed yet (a draft heading to proposed\u002Faccepted), use spec-red-team\n  instead — gate-close already contains a red team per flip.\nhooks:\n  # US-0010 (RFC-0032 F-freeze): DENY any agent Edit|Write that would flip a governed-doc\n  # `status:` front-matter value or an INDEX.md Status-column cell, so a status advance stays an\n  # owner ratification and never an agent's incidental edit. Skill-scoped BY DESIGN: this block\n  # lives ONLY here, never in settings.default.json, so the freeze is active only during a\n  # gate-close run and clears on the next message — an owner-authorized flip applied OUTSIDE an\n  # active run is not intercepted. DOCUMENTED GAP (accepted, stated not hidden): the matcher is\n  # Edit|Write only, so a flip driven through Bash (`sed -i ...`) or any other tool bypasses this\n  # hook entirely; the always-on Stop gate re-checks the whole tree.\n  PreToolUse:\n    - matcher: Edit|Write\n      hooks:\n        - type: command\n          command: node \"${CLAUDE_SKILL_DIR}\u002Ffreeze-status-edit.mjs\"\n---\n\n# Gate Close\n\nA status flip is a ratification, and a ratification needs evidence. This skill collapses the\nrepetitive pre-flip tail into one packet the owner decides from in a single pass.\n\n## When to run it\n\nAfter the change has **landed and been committed**, and before proposing any status advance.\nDo not run it while agents are still editing the tree — the verifier reads the working tree, so\na mid-edit tree yields a false BLOCK. Commit first, then close.\n\n## Current gate verdict (live)\n\nInjected at invocation so the packet is read against ground truth, not a reconstruction — this is\nthe repo's real verify, read-only:\n\n!`npx govkit verify --json`\n\nThe injection is an accelerant, not a dependency: if that command is unavailable (govkit not\ninstalled, or a non-Node repo), ignore this block and discover the real gate from `package.json`\nbelow. `verify` reads the working tree, so a non-empty violation list here usually means the tree\nis still dirty — commit first (see above), then close.\n\n## How to run it\n\n```\nWorkflow({\n  name: 'gate-loop',\n  args: {\n    verifyCmd: 'bun run check',\n    changeSummary: 'One paragraph on what the landed change actually does — the mechanism, the seams, what was verified and how. This is what the red-teamers reason from, so name real symbols and real commands.',\n    flips: [\n      { id: 'US-0015', target: 'done',        doc: 'docs\u002Fissues\u002FUS-0015-....md' },\n      { id: 'RFC-0025', target: 'implemented', doc: 'docs\u002Frfc\u002FRFC-0025-....md' },\n    ],\n  },\n})\n```\n\n`verifyCmd` is required and must be the repo's real gate — never guess it. Discover it from\n`package.json`, `Makefile`, or the CI workflow before invoking. `changeSummary` matters most: a\nvague summary produces a vague red team.\n\n## Reading the packet\n\n```\n{ gate:      { verdict, gates, gateProvenFallible, findings[] },\n  live:      { liveVerdict, ranCommands, claims, notMeasured },  \u002F\u002F 'skipped' unless args.live set (always set at a release gate)\n  reconcile: { edits: [{ doc, reason, proposed }] },   \u002F\u002F exact text, NOT applied\n  redTeam:   [{ id, verdict, criteriaSummary, reconciledText, sourcesExist, killCriterion }],\n  humanGates: [\"US-0015 -> done\", ...] }\n```\n\n- `gate.verdict: BLOCK` or `gate.gateProvenFallible: false` — stop. Nothing advances on an\n  unproven gate.\n- `live.liveVerdict: fail`, or any `live.claims[].verdict: refuted` — stop. The shipped artifact\n  did not run; a green source gate does not override a red real-artifact run.\n- `flip-as-is` — the status is honest; still apply any `reconcile.edits`.\n- `flip-after-reconcile` — apply `reconciledText` first, then flip.\n- `blocked` — do not flip. Fix the code, or scope the claim down to what shipped.\n\n`packet.humanGates` lists every flip candidate flatly — the workflow itself does not tier them.\nThe split below (RFC-0027) is this skill's job, done once the packet is back.\n\n## Acting on the packet\n\n1. **Tier each flip (RFC-0027).** Read the repo's `govkit.yml` for a top-level `ratification:`\n   block. For each flip, its transition key is `doctype:from->to` — read the doc's CURRENT\n   `status:` (`packet.humanGates` only names the id and the target) to build it.\n   - **Block absent** → every flip is **R0** (owner-tier). This is the pre-RFC-0027 behavior,\n     unchanged — nothing here regresses a repo that has not adopted the block yet.\n   - **Block present**, transition matches `R0_owner.transitions`, matches no tier at all, or IS\n     an edit to the `ratification:` block itself → **R0**. An unmatched transition always falls\n     to R0, never to R1 — the default is the ask, not the skip.\n   - Matches `R1_packet.transitions` (`rfc:accepted->implemented`, `us:in-progress->done`,\n     `drift --ack`) AND every condition holds — `gate.verdict == \"SAFE-TO-COMMIT\"` with\n     `gate.gateProvenFallible == true` (the FULL gate, never a narrower command), this packet is\n     itself the required evidence, and this flip's `redTeam[].verdict` is `flip-as-is` or\n     `flip-after-reconcile` with `reconciledText` already applied → **R1, auto-apply**.\n   - Matches `R1_packet.transitions` but a condition fails (`gate.verdict == \"BLOCK\"` or\n     `gateProvenFallible == false`, `redTeam[].verdict == \"blocked\"`, or a `flip-after-reconcile`\n     whose `reconciledText` was never applied) → **R1, escalate** — fold it into the owner-facing\n     set below, naming the exact condition that failed. Never quietly downgrade an unmet R1 to a\n     silent auto-apply.\n   - Matches `R2_lead.transitions` (`us:open->in-progress`, `us->blocked`) → **R2, no ceremony** —\n     these carry no evidence bar to begin with; land directly, citing the policy source only.\n2. Present the R0 set — including every escalated R1, each tagged with the condition that failed\n   — to the owner as ONE decision via the `AskUserQuestion` tool: surface every flip in this set\n   in a single ratification (not N separate prompts), with structured options — authorize \u002F hold \u002F\n   reword-first — alongside the reconcile edits and any limitation the red team surfaced.\n   Recommend with trade-offs; the owner authorizes. Scope this prompt to the R0 + escalated-R1 set\n   ONLY — the R1 auto-apply (step 4) and R2 no-ceremony flips get no fresh ask (RFC-0027).\n3. **Only on that authorization**, apply `reconcile.edits` and every `reconciledText` for the\n   R0\u002Fescalated set. A governed doc must certify exactly what shipped — never round a partial\n   criterion up to done. Land each as a **separate accept commit** that edits the front-matter\n   `status:` and the matching INDEX row, citing the owner's in-session authorization.\n4. **R1 auto-apply (and R2) flips do not wait for step 2.** Apply that flip's `reconciledText`\n   first if its verdict was `flip-after-reconcile`, then land it in its OWN commit whose message\n   cites the packet's run id (the workflow invocation id, e.g. `wf_xxxxxxxx`) and the policy\n   source (`govkit.yml @ \u003Cshort-sha>`) — that citation REPLACES the in-session owner quote, it\n   does not supplement it.\n5. Re-run the gate after the flips, and confirm the remote ref actually moved after pushing.\n\n## Why fewer asks is safe here\n\nR1 removes the ask; it removes nothing that verifies. Three controls stay exactly as strict as\nbefore RFC-0027:\n\n- **The deterministic section gate at `implemented` is untouched.** `govkit verify` still fails\n  an RFC flipped to `implemented` (or a `rel` at `released`) that is missing its\n  `requiredSectionsByStatus` sections — As-built \u002F Deviations from design (RFC-0010). An R1 flip\n  that skips the ask still cannot skip proving what shipped.\n- **The distiller audits every R1 flip commit.** DISTILL (RFC-0017) reads each R1 commit against\n  the packet it cites: a flip that cites a red gate, a `blocked` red-team, or no packet at all is\n  an escape, logged to LEARNING-LOOP. The audit lands after the fact, but it is not optional —\n  R1 is fast, not unwatched.\n- **Code approval stays untouched, always.** This tiering covers doc `status:` bookkeeping only.\n  Never self-approve, never self-merge, never act as code owner (AGENTS.md) — R1 does not touch\n  that rule and never will; it only changes who signs the transcription of a fact the gate and\n  the packet already established.\n\n## Release close\n\nAt a release gate the loop runs its strongest form: `gate: 'release'`, which REQUIRES a `live`\nscenario. The scenario is a real consumer install, not a re-run of this repo's own gate.\n\n```\nWorkflow({\n  name: 'gate-loop',\n  args: {\n    gate: 'release',\n    verifyCmd: 'bun run check',\n    changeSummary: 'One paragraph on what this release ships.',\n    live: {\n      scenario: 'npm pack the tarball; install it into a clean scratch dir (mktemp -d); run `npx govkit init`; confirm the gate is green; then break one governed doc (remove a required front-matter key) and confirm the gate exits non-zero.',\n      expectations: [\n        'the packed tarball installs into a clean dir',\n        'npx govkit init scaffolds and the gate exits 0',\n        'a doc with a required front-matter key removed makes the gate exit non-zero',\n      ],\n    },\n    flips: [{ id: 'REL-0001', target: 'released', doc: 'docs\u002Freleases\u002FREL-0001-....md' }],\n  },\n})\n```\n\nThe verifier returns `live: { liveVerdict, ranCommands, claims, notMeasured }`. On owner\nratification, the ledger entry's `check` string is GENERATED from the verifier's `ranCommands` —\nthe real commands and their real exit codes — not typed by hand. That turns the\n`docs\u002Fledger.json` `check` field from testimony (\"I ran it, it passed\") into evidence (the exact\ncommand a reader can re-run). Never write a `released` flip whose ledger `check` is not backed by\na `ranCommands` entry that exited 0.\n\n## Gotchas\n\nThe failure modes this ritual keeps re-learning, written where you meet them (seeded from\n`LEARNING-LOOP.md`; the distiller extends this list from new escapes):\n\n- **Premature `drift --ack`.** `drift` hashes the **staged\u002Fcommitted** blob, not the working tree.\n  Acking while the governed change is still unstaged pins the *old* blob — the gate goes green, then\n  drift re-fires the moment you commit. Always stage\u002Fcommit the governed change **first**, then\n  `drift --ack`. (Round 23; hit twice in one gate-close session.)\n- **Front-matter ↔ INDEX drift.** A doc's `status:`\u002F`owner:` and its INDEX row cell must match;\n  `verify` catches a mismatch. When you flip a status, edit **both** the front-matter and the INDEX\n  row in the same change, or the close goes red on the next run.\n- **Status flip is an owner act, in its own commit.** A sub-agent never flips a `status:` (the\n  skill-scoped freeze hook now denies it at the tool boundary). The main agent flips only on the\n  owner's in-session authorization, in a **separate** commit that cites it — never folded into the\n  implementation commit. (RFC-0027\u002FRFC-0032 F-freeze.)\n- **Never pipe the gate through `head`\u002F`grep` in a `&&` chain** — the pipe swallows the failing exit\n  code and a red gate reads green. Capture to a file or check `$?` before chaining. (Round 12.)\n- **Act on the *same* green.** `bun run check && \u003Cflip\u002Fmerge\u002Fpush>` in one chain — a green captured a\n  few edits ago certifies the previous tree, not this one. (Round 22.)\n\n## Why one packet\n\nThe owner is the bottleneck when every flip is surfaced separately. Batching the whole tail into\none packet turns N interruptions into one ratification, while keeping the two controls that\nprotect the record: an independent verify and an independent red team, neither authored by\nwhoever wrote the change.\n","# Gate Close\n\nA status flip is a ratification, and a ratification needs evidence. This skill collapses the\nrepetitive pre-flip tail into one packet the owner decides from in a single pass.\n\n## When to run it\n\nAfter the change has **landed and been committed**, and before proposing any status advance.\nDo not run it while agents are still editing the tree — the verifier reads the working tree, so\na mid-edit tree yields a false BLOCK. Commit first, then close.\n\n## Current gate verdict (live)\n\nInjected at invocation so the packet is read against ground truth, not a reconstruction — this is\nthe repo's real verify, read-only:\n\n!`npx govkit verify --json`\n\nThe injection is an accelerant, not a dependency: if that command is unavailable (govkit not\ninstalled, or a non-Node repo), ignore this block and discover the real gate from `package.json`\nbelow. `verify` reads the working tree, so a non-empty violation list here usually means the tree\nis still dirty — commit first (see above), then close.\n\n## How to run it\n\n```\nWorkflow({\n  name: 'gate-loop',\n  args: {\n    verifyCmd: 'bun run check',\n    changeSummary: 'One paragraph on what the landed change actually does — the mechanism, the seams, what was verified and how. This is what the red-teamers reason from, so name real symbols and real commands.',\n    flips: [\n      { id: 'US-0015', target: 'done',        doc: 'docs\u002Fissues\u002FUS-0015-....md' },\n      { id: 'RFC-0025', target: 'implemented', doc: 'docs\u002Frfc\u002FRFC-0025-....md' },\n    ],\n  },\n})\n```\n\n`verifyCmd` is required and must be the repo's real gate — never guess it. Discover it from\n`package.json`, `Makefile`, or the CI workflow before invoking. `changeSummary` matters most: a\nvague summary produces a vague red team.\n\n## Reading the packet\n\n```\n{ gate:      { verdict, gates, gateProvenFallible, findings[] },\n  live:      { liveVerdict, ranCommands, claims, notMeasured },  \u002F\u002F 'skipped' unless args.live set (always set at a release gate)\n  reconcile: { edits: [{ doc, reason, proposed }] },   \u002F\u002F exact text, NOT applied\n  redTeam:   [{ id, verdict, criteriaSummary, reconciledText, sourcesExist, killCriterion }],\n  humanGates: [\"US-0015 -> done\", ...] }\n```\n\n- `gate.verdict: BLOCK` or `gate.gateProvenFallible: false` — stop. Nothing advances on an\n  unproven gate.\n- `live.liveVerdict: fail`, or any `live.claims[].verdict: refuted` — stop. The shipped artifact\n  did not run; a green source gate does not override a red real-artifact run.\n- `flip-as-is` — the status is honest; still apply any `reconcile.edits`.\n- `flip-after-reconcile` — apply `reconciledText` first, then flip.\n- `blocked` — do not flip. Fix the code, or scope the claim down to what shipped.\n\n`packet.humanGates` lists every flip candidate flatly — the workflow itself does not tier them.\nThe split below (RFC-0027) is this skill's job, done once the packet is back.\n\n## Acting on the packet\n\n1. **Tier each flip (RFC-0027).** Read the repo's `govkit.yml` for a top-level `ratification:`\n   block. For each flip, its transition key is `doctype:from->to` — read the doc's CURRENT\n   `status:` (`packet.humanGates` only names the id and the target) to build it.\n   - **Block absent** → every flip is **R0** (owner-tier). This is the pre-RFC-0027 behavior,\n     unchanged — nothing here regresses a repo that has not adopted the block yet.\n   - **Block present**, transition matches `R0_owner.transitions`, matches no tier at all, or IS\n     an edit to the `ratification:` block itself → **R0**. An unmatched transition always falls\n     to R0, never to R1 — the default is the ask, not the skip.\n   - Matches `R1_packet.transitions` (`rfc:accepted->implemented`, `us:in-progress->done`,\n     `drift --ack`) AND every condition holds — `gate.verdict == \"SAFE-TO-COMMIT\"` with\n     `gate.gateProvenFallible == true` (the FULL gate, never a narrower command), this packet is\n     itself the required evidence, and this flip's `redTeam[].verdict` is `flip-as-is` or\n     `flip-after-reconcile` with `reconciledText` already applied → **R1, auto-apply**.\n   - Matches `R1_packet.transitions` but a condition fails (`gate.verdict == \"BLOCK\"` or\n     `gateProvenFallible == false`, `redTeam[].verdict == \"blocked\"`, or a `flip-after-reconcile`\n     whose `reconciledText` was never applied) → **R1, escalate** — fold it into the owner-facing\n     set below, naming the exact condition that failed. Never quietly downgrade an unmet R1 to a\n     silent auto-apply.\n   - Matches `R2_lead.transitions` (`us:open->in-progress`, `us->blocked`) → **R2, no ceremony** —\n     these carry no evidence bar to begin with; land directly, citing the policy source only.\n2. Present the R0 set — including every escalated R1, each tagged with the condition that failed\n   — to the owner as ONE decision via the `AskUserQuestion` tool: surface every flip in this set\n   in a single ratification (not N separate prompts), with structured options — authorize \u002F hold \u002F\n   reword-first — alongside the reconcile edits and any limitation the red team surfaced.\n   Recommend with trade-offs; the owner authorizes. Scope this prompt to the R0 + escalated-R1 set\n   ONLY — the R1 auto-apply (step 4) and R2 no-ceremony flips get no fresh ask (RFC-0027).\n3. **Only on that authorization**, apply `reconcile.edits` and every `reconciledText` for the\n   R0\u002Fescalated set. A governed doc must certify exactly what shipped — never round a partial\n   criterion up to done. Land each as a **separate accept commit** that edits the front-matter\n   `status:` and the matching INDEX row, citing the owner's in-session authorization.\n4. **R1 auto-apply (and R2) flips do not wait for step 2.** Apply that flip's `reconciledText`\n   first if its verdict was `flip-after-reconcile`, then land it in its OWN commit whose message\n   cites the packet's run id (the workflow invocation id, e.g. `wf_xxxxxxxx`) and the policy\n   source (`govkit.yml @ \u003Cshort-sha>`) — that citation REPLACES the in-session owner quote, it\n   does not supplement it.\n5. Re-run the gate after the flips, and confirm the remote ref actually moved after pushing.\n\n## Why fewer asks is safe here\n\nR1 removes the ask; it removes nothing that verifies. Three controls stay exactly as strict as\nbefore RFC-0027:\n\n- **The deterministic section gate at `implemented` is untouched.** `govkit verify` still fails\n  an RFC flipped to `implemented` (or a `rel` at `released`) that is missing its\n  `requiredSectionsByStatus` sections — As-built \u002F Deviations from design (RFC-0010). An R1 flip\n  that skips the ask still cannot skip proving what shipped.\n- **The distiller audits every R1 flip commit.** DISTILL (RFC-0017) reads each R1 commit against\n  the packet it cites: a flip that cites a red gate, a `blocked` red-team, or no packet at all is\n  an escape, logged to LEARNING-LOOP. The audit lands after the fact, but it is not optional —\n  R1 is fast, not unwatched.\n- **Code approval stays untouched, always.** This tiering covers doc `status:` bookkeeping only.\n  Never self-approve, never self-merge, never act as code owner (AGENTS.md) — R1 does not touch\n  that rule and never will; it only changes who signs the transcription of a fact the gate and\n  the packet already established.\n\n## Release close\n\nAt a release gate the loop runs its strongest form: `gate: 'release'`, which REQUIRES a `live`\nscenario. The scenario is a real consumer install, not a re-run of this repo's own gate.\n\n```\nWorkflow({\n  name: 'gate-loop',\n  args: {\n    gate: 'release',\n    verifyCmd: 'bun run check',\n    changeSummary: 'One paragraph on what this release ships.',\n    live: {\n      scenario: 'npm pack the tarball; install it into a clean scratch dir (mktemp -d); run `npx govkit init`; confirm the gate is green; then break one governed doc (remove a required front-matter key) and confirm the gate exits non-zero.',\n      expectations: [\n        'the packed tarball installs into a clean dir',\n        'npx govkit init scaffolds and the gate exits 0',\n        'a doc with a required front-matter key removed makes the gate exit non-zero',\n      ],\n    },\n    flips: [{ id: 'REL-0001', target: 'released', doc: 'docs\u002Freleases\u002FREL-0001-....md' }],\n  },\n})\n```\n\nThe verifier returns `live: { liveVerdict, ranCommands, claims, notMeasured }`. On owner\nratification, the ledger entry's `check` string is GENERATED from the verifier's `ranCommands` —\nthe real commands and their real exit codes — not typed by hand. That turns the\n`docs\u002Fledger.json` `check` field from testimony (\"I ran it, it passed\") into evidence (the exact\ncommand a reader can re-run). Never write a `released` flip whose ledger `check` is not backed by\na `ranCommands` entry that exited 0.\n\n## Gotchas\n\nThe failure modes this ritual keeps re-learning, written where you meet them (seeded from\n`LEARNING-LOOP.md`; the distiller extends this list from new escapes):\n\n- **Premature `drift --ack`.** `drift` hashes the **staged\u002Fcommitted** blob, not the working tree.\n  Acking while the governed change is still unstaged pins the *old* blob — the gate goes green, then\n  drift re-fires the moment you commit. Always stage\u002Fcommit the governed change **first**, then\n  `drift --ack`. (Round 23; hit twice in one gate-close session.)\n- **Front-matter ↔ INDEX drift.** A doc's `status:`\u002F`owner:` and its INDEX row cell must match;\n  `verify` catches a mismatch. When you flip a status, edit **both** the front-matter and the INDEX\n  row in the same change, or the close goes red on the next run.\n- **Status flip is an owner act, in its own commit.** A sub-agent never flips a `status:` (the\n  skill-scoped freeze hook now denies it at the tool boundary). The main agent flips only on the\n  owner's in-session authorization, in a **separate** commit that cites it — never folded into the\n  implementation commit. (RFC-0027\u002FRFC-0032 F-freeze.)\n- **Never pipe the gate through `head`\u002F`grep` in a `&&` chain** — the pipe swallows the failing exit\n  code and a red gate reads green. Capture to a file or check `$?` before chaining. (Round 12.)\n- **Act on the *same* green.** `bun run check && \u003Cflip\u002Fmerge\u002Fpush>` in one chain — a green captured a\n  few edits ago certifies the previous tree, not this one. (Round 22.)\n\n## Why one packet\n\nThe owner is the bottleneck when every flip is surfaced separately. Batching the whole tail into\none packet turns N interruptions into one ratification, while keeping the two controls that\nprotect the record: an independent verify and an independent red team, neither authored by\nwhoever wrote the change.\n",{"name":5,"hooks":24,"description":7},{"PreToolUse":25},[26],{"hooks":27,"matcher":31},[28],{"type":29,"command":30},"command","node \"${CLAUDE_SKILL_DIR}\u002Ffreeze-status-edit.mjs\"","Edit|Write","main","850634e254ea6a5034bf2eddad5fe95091713231","plugins\u002Fswe-flow\u002Fskills\u002Fgate-close","https:\u002F\u002Fgithub.com\u002Fbaodq97\u002Fgovkit","https:\u002F\u002Fgithub.com\u002Fbaodq97","2026-09-07 14:26:00",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add baodq97\u002Fgovkit --skill gate-close",{"tool":44,"command":45},"bunx","bunx skills add baodq97\u002Fgovkit --skill gate-close",{"tool":47,"command":48},"pnpm","pnpm dlx skills add baodq97\u002Fgovkit --skill gate-close","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbaodq97\u002Fgovkit\u002Fblob\u002Fmain\u002Fplugins\u002Fswe-flow\u002Fskills\u002Fgate-close\u002FSKILL.md",true,[52,58],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"freeze-status-edit.mjs","SCRIPT","脚本",13393,"https:\u002F\u002Fgithub.com\u002Fbaodq97\u002Fgovkit\u002Fblob\u002Fmain\u002Fplugins\u002Fswe-flow\u002Fskills\u002Fgate-close\u002Ffreeze-status-edit.mjs",{"path":59,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":60,"sourceHtmlUrl":61},"freeze-status-edit.test.mjs",17895,"https:\u002F\u002Fgithub.com\u002Fbaodq97\u002Fgovkit\u002Fblob\u002Fmain\u002Fplugins\u002Fswe-flow\u002Fskills\u002Fgate-close\u002Ffreeze-status-edit.test.mjs",[63,70,77,84,91,97],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M759HTCHQJVZ4JWDA2JNPJJZ","trigger-shaped","Use when the user says \"plan a sprint retro\"; drafts retro\u002Fnotes.md for the team.","https:\u002F\u002Fgithub.com\u002Fbaodq97\u002Fgovkit\u002Fblob\u002Fmain\u002Fscripts\u002Ffixtures\u002Fskill-lint\u002Ftriggering\u002Fskills\u002Ftrigger-shaped\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M759HS3E2T97ZN1ED2Z96WAJ","terse-unguarded","Step 2 — writes docs\u002Fx\u002Foutput.json quietly.","https:\u002F\u002Fgithub.com\u002Fbaodq97\u002Fgovkit\u002Fblob\u002Fmain\u002Fscripts\u002Ffixtures\u002Fskill-lint\u002Ftriggering\u002Fskills\u002Fterse-unguarded\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M759HPZN28VZHKYFR754CVXT","guarded","Summarizes ledger totals into reports\u002Fmonthly.csv.","https:\u002F\u002Fgithub.com\u002Fbaodq97\u002Fgovkit\u002Fblob\u002Fmain\u002Fscripts\u002Ffixtures\u002Fskill-lint\u002Ftriggering\u002Fskills\u002Fguarded\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M759HMFQAZAWFVSS3KWPCCW0","open","Draft a spec. Use when asked to \"draft a spec\" or \"write the RFC\".","https:\u002F\u002Fgithub.com\u002Fbaodq97\u002Fgovkit\u002Fblob\u002Fmain\u002Fscripts\u002Ffixtures\u002Fskill-lint\u002Fdead-hint\u002Fskills\u002Fopen\u002FSKILL.md",[],[],{"skillNo":92,"name":79,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M759HJ3XX74S70PW9AR8NS66","Deploy the thing.","https:\u002F\u002Fgithub.com\u002Fbaodq97\u002Fgovkit\u002Fblob\u002Fmain\u002Fscripts\u002Ffixtures\u002Fskill-lint\u002Fdead-hint\u002Fskills\u002Fguarded\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M759HCWJN9ACRNC1JW76DR1E","working-discipline","Thinking-checkpoint discipline for substantive implementation, debugging, or autonomous work — 21 trigger-gated items (trigger → mandatory question → evidence to produce) that cut agent error and human escalation. Use before an autonomous or long-running run, when asked to \"work carefully\", \"double-check\", \"làm cẩn thận\", \"reduce errors\", \"be more autonomous\", or after looping twice on the same failing fix. NOT a procedure — checkpoints fire on their triggers and demand evidence, with an N\u002FA escape valve so a strong model pays near-zero overhead.","https:\u002F\u002Fgithub.com\u002Fbaodq97\u002Fgovkit\u002Fblob\u002Fmain\u002Fplugins\u002Fswe-flow\u002Fskills\u002Fworking-discipline\u002FSKILL.md",[],[]]