[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MP8JA8D2QQAM1EJ1GXAH9Z":3,"skill-same:01M6MP8JA8D2QQAM1EJ1GXAH9Z":65},{"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":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M6MP8JA8D2QQAM1EJ1GXAH9Z","finishing-a-development-branch",null,"Use after execution is complete or intentionally stopped — decide whether to merge back, publish a PR branch, keep the execution checkout, or discard it, and record that disposition in HOTL state.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyimwoo\u002Fhotl-plugin\u002Fskills\u002Ffinishing-a-development-branch\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"finishing a development branch","development","branch","hotl","merge","it","keep","checkout","complete","record","back","use","decide","execution","publish","state","pr","2026-11-10 10:12:30",false,"---\nname: finishing-a-development-branch\ndescription: Use after execution is complete or intentionally stopped — decide whether to merge back, publish a PR branch, keep the execution checkout, or discard it, and record that disposition in HOTL state.\n---\n\n# Finishing A Development Branch\n\nUse this after `loop-execution`, `executing-plans`, or `subagent-execution` when the run already has a `run_id` and you need to decide what happens to the execution branch\u002Fworktree next.\n\n## Core Idea\n\nHOTL distinguishes between:\n\n- **Authoring checkout** — where the workflow was written (`source_branch`, `source_head`)\n- **Execution checkout** — where the workflow ran (`branch`, `execution_root`, `worktree_path`)\n\nFinishing is the stage that closes that loop intentionally. Do not silently merge, delete, or abandon the execution worktree.\n\n## Step 1: Read Execution Provenance\n\nRun:\n\n```bash\nhotl-rt summary \u003Crun-id> --json\n```\n\nSurface these fields before presenting options:\n\n- `status`\n- `source_branch`\n- `branch`\n- `execution_root`\n- `worktree_path`\n- `finish.disposition` (if already recorded)\n- controller owner\u002Fstatus and receipt reasons\n\nIf `finish.disposition` is already set, stop and tell the user the run is already finished.\n\nA successful execution must be `ready_to_finish` before merge or publish. `ready_to_finish` means execution evidence is complete but the run is not yet `completed`. Keep the existing controller lease active and retain `HOTL_OWNER_TOKEN`; if a different controller is finishing, use explicit owner handoff\u002Ftakeover rules from `resuming` first. Run `owner heartbeat` before a long finish operation.\n\n## Step 2: Present The 4 Finish Options\n\nUse these options:\n\n1. **Merge back locally**\n   - Default target: `source_branch` when present and different from the execution branch\n   - Fallback target: `main` or `master`\n2. **Publish branch \u002F create PR**\n   - Push the execution branch to a remote\n   - If `gh` is available and the user wants a PR, create it against the chosen target branch\n3. **Keep as-is**\n   - Preserve the execution branch\u002Fworktree for later review or follow-up changes\n4. **Discard**\n   - Remove the execution branch\u002Fworktree after explicit confirmation\n\nExplain the target branch explicitly when merge or PR target is inferred from `source_branch`.\n\n## Step 3: Authorize External Effects\n\nFor publish\u002FPR, record one bounded `external_write` with the exact target `publish \u003Cbranch> to \u003Cremote>` (append ` and create PR against \u003Ctarget-branch>` when `--create-pr` is used), pass `--idempotency-key \u003Cstable-key>`, obtain human `action decide ... approved --mode human`, and pass the returned action id and key to the helper. If a merge is classified as `production_change`, use the exact target `merge \u003Cbranch> into \u003Ctarget-branch>`. The helper verifies kind, target, key, approval, and not-started status; it then performs `action begin` immediately before the effect and `action complete` with observed evidence before recording finish.\n\nApproval is not effect evidence. If the helper stops after a push, PR attempt, or merge may have started, leave the action unresolved, inspect the target, and use `action reconcile`. Never rerun the helper while the effect is `in_progress` or `uncertain`.\n\n## Step 4: Execute Via The Helper\n\nUse the repo-owned helper:\n\n```bash\nscripts\u002Fhotl-finish-execution.sh --run-id \u003Crun-id> --mode \u003Ckeep|merge|publish|discard> ...\n```\n\nMappings:\n\n- Keep → `--mode keep`\n- Merge locally → `--mode merge [--target-branch \u003Cbranch>]`\n- Publish \u002F PR → `--mode publish [--remote origin] [--target-branch \u003Cbranch>] [--create-pr]`\n- Discard → `--mode discard --confirm discard`\n\nFor an approved merge\u002Fpublish effect, also pass `--effect-action-id \u003Cid> --idempotency-key \u003Ckey>`. The helper records intent with `action begin`, executes the bounded effect, persists `action complete` evidence, then records the finish disposition with `hotl-rt finish ...`. It enforces safety checks around branch switching, merging, cleanup, and destructive discard. `HOTL_OWNER_TOKEN` must remain in the helper environment.\n\n## Step 5: Report The Outcome\n\nAfter the helper succeeds, show:\n\n- Finish disposition\n- Target branch \u002F PR URL if applicable\n- Whether the execution worktree was kept or removed\n- Where the durable report lives\n\nThen run `owner release` and derive a fresh receipt. Claim completion only when the run is `completed` and `sufficiency.sufficient` is true. A failed helper must leave finish unset; use `action reconcile` before another attempt when an external effect may have occurred.\n\nImportant behavior:\n\n- Merge and discard preserve `.hotl\u002Fstate\u002F\u003Crun-id>.json` and `.hotl\u002Freports\u002F\u003Crun-id>.md` back into the repo checkout before removing an isolated execution worktree\n- Publish keeps the execution worktree by default so review follow-ups can continue on the same branch\n- Shared-checkout same-branch runs are intentionally conservative; discard and merge may require manual handling if automation would be ambiguous or destructive\n\n## Guardrails\n\n- Do not auto-merge after execution just because tests passed\n- Do not auto-delete work without explicit user confirmation\n- Do not create a PR unless the user chose the publish\u002FPR path\n- If merge conflicts occur, stop and leave the execution branch\u002Fworktree intact\n- If a chosen PR operation cannot run because `gh` is unavailable or fails after push, do not silently downgrade the approved target. Leave finish unset, reconcile the observed push, and ask whether the user wants a new bounded push-only action.\n","# Finishing A Development Branch\n\nUse this after `loop-execution`, `executing-plans`, or `subagent-execution` when the run already has a `run_id` and you need to decide what happens to the execution branch\u002Fworktree next.\n\n## Core Idea\n\nHOTL distinguishes between:\n\n- **Authoring checkout** — where the workflow was written (`source_branch`, `source_head`)\n- **Execution checkout** — where the workflow ran (`branch`, `execution_root`, `worktree_path`)\n\nFinishing is the stage that closes that loop intentionally. Do not silently merge, delete, or abandon the execution worktree.\n\n## Step 1: Read Execution Provenance\n\nRun:\n\n```bash\nhotl-rt summary \u003Crun-id> --json\n```\n\nSurface these fields before presenting options:\n\n- `status`\n- `source_branch`\n- `branch`\n- `execution_root`\n- `worktree_path`\n- `finish.disposition` (if already recorded)\n- controller owner\u002Fstatus and receipt reasons\n\nIf `finish.disposition` is already set, stop and tell the user the run is already finished.\n\nA successful execution must be `ready_to_finish` before merge or publish. `ready_to_finish` means execution evidence is complete but the run is not yet `completed`. Keep the existing controller lease active and retain `HOTL_OWNER_TOKEN`; if a different controller is finishing, use explicit owner handoff\u002Ftakeover rules from `resuming` first. Run `owner heartbeat` before a long finish operation.\n\n## Step 2: Present The 4 Finish Options\n\nUse these options:\n\n1. **Merge back locally**\n   - Default target: `source_branch` when present and different from the execution branch\n   - Fallback target: `main` or `master`\n2. **Publish branch \u002F create PR**\n   - Push the execution branch to a remote\n   - If `gh` is available and the user wants a PR, create it against the chosen target branch\n3. **Keep as-is**\n   - Preserve the execution branch\u002Fworktree for later review or follow-up changes\n4. **Discard**\n   - Remove the execution branch\u002Fworktree after explicit confirmation\n\nExplain the target branch explicitly when merge or PR target is inferred from `source_branch`.\n\n## Step 3: Authorize External Effects\n\nFor publish\u002FPR, record one bounded `external_write` with the exact target `publish \u003Cbranch> to \u003Cremote>` (append ` and create PR against \u003Ctarget-branch>` when `--create-pr` is used), pass `--idempotency-key \u003Cstable-key>`, obtain human `action decide ... approved --mode human`, and pass the returned action id and key to the helper. If a merge is classified as `production_change`, use the exact target `merge \u003Cbranch> into \u003Ctarget-branch>`. The helper verifies kind, target, key, approval, and not-started status; it then performs `action begin` immediately before the effect and `action complete` with observed evidence before recording finish.\n\nApproval is not effect evidence. If the helper stops after a push, PR attempt, or merge may have started, leave the action unresolved, inspect the target, and use `action reconcile`. Never rerun the helper while the effect is `in_progress` or `uncertain`.\n\n## Step 4: Execute Via The Helper\n\nUse the repo-owned helper:\n\n```bash\nscripts\u002Fhotl-finish-execution.sh --run-id \u003Crun-id> --mode \u003Ckeep|merge|publish|discard> ...\n```\n\nMappings:\n\n- Keep → `--mode keep`\n- Merge locally → `--mode merge [--target-branch \u003Cbranch>]`\n- Publish \u002F PR → `--mode publish [--remote origin] [--target-branch \u003Cbranch>] [--create-pr]`\n- Discard → `--mode discard --confirm discard`\n\nFor an approved merge\u002Fpublish effect, also pass `--effect-action-id \u003Cid> --idempotency-key \u003Ckey>`. The helper records intent with `action begin`, executes the bounded effect, persists `action complete` evidence, then records the finish disposition with `hotl-rt finish ...`. It enforces safety checks around branch switching, merging, cleanup, and destructive discard. `HOTL_OWNER_TOKEN` must remain in the helper environment.\n\n## Step 5: Report The Outcome\n\nAfter the helper succeeds, show:\n\n- Finish disposition\n- Target branch \u002F PR URL if applicable\n- Whether the execution worktree was kept or removed\n- Where the durable report lives\n\nThen run `owner release` and derive a fresh receipt. Claim completion only when the run is `completed` and `sufficiency.sufficient` is true. A failed helper must leave finish unset; use `action reconcile` before another attempt when an external effect may have occurred.\n\nImportant behavior:\n\n- Merge and discard preserve `.hotl\u002Fstate\u002F\u003Crun-id>.json` and `.hotl\u002Freports\u002F\u003Crun-id>.md` back into the repo checkout before removing an isolated execution worktree\n- Publish keeps the execution worktree by default so review follow-ups can continue on the same branch\n- Shared-checkout same-branch runs are intentionally conservative; discard and merge may require manual handling if automation would be ambiguous or destructive\n\n## Guardrails\n\n- Do not auto-merge after execution just because tests passed\n- Do not auto-delete work without explicit user confirmation\n- Do not create a PR unless the user chose the publish\u002FPR path\n- If merge conflicts occur, stop and leave the execution branch\u002Fworktree intact\n- If a chosen PR operation cannot run because `gh` is unavailable or fails after push, do not silently downgrade the approved target. Leave finish unset, reconcile the observed push, and ask whether the user wants a new bounded push-only action.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fyimwoo\u002Fhotl-plugin\u002Fskills\u002Ffinishing-a-development-branch",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill finishing-a-development-branch",{"tool":57,"command":58},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill finishing-a-development-branch",{"tool":60,"command":61},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill finishing-a-development-branch","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyimwoo\u002Fhotl-plugin\u002Fskills\u002Ffinishing-a-development-branch\u002FSKILL.md",true,[],[66,76,84,92,100,108],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":71,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":75},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":75},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\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":70,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":75},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":96,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":75},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":104,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":75},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":112,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":75},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]