[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AQTK6GFWAR89H3XEXPY5FE":3,"skill-same:01M7AQTK6GFWAR89H3XEXPY5FE":44},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7AQTK6GFWAR89H3XEXPY5FE","finishing-a-development-branch",null,"Use when verified work needs integration or cleanup of an existing task-created branch\u002Fworktree, or the user explicitly requests merge, PR, or branch lifecycle handling.","ham-zax\u002Fwebharness","ham-zax","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F81289670?v=4","01M7AQGHAV4TPYCAZY23S7SVSC","Ahmed Hamza","01M7AQGHBCFJYE7KWZ34W9HEGH",0,"MIT","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskill-library\u002Fpacks\u002Factive\u002Ffinishing-a-development-branch\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: finishing-a-development-branch\ndescription: \"Use when verified work needs integration or cleanup of an existing task-created branch\u002Fworktree, or the user explicitly requests merge, PR, or branch lifecycle handling.\"\n---\n\n# Finishing a Development Branch\n\n## Overview\n\nIntegration choice and checkout lifetime are separate. Verify first, mutate only\ntask-owned resources, then prove what was removed or retained.\n\n**Core principle:** fresh evidence -> authorized integration -> ownership-aware\ncleanup -> Git\u002Fpath readback.\n\n**Announce at start:** explain which branch\u002Fworktree lifecycle is being closed.\n\n## Step 1: Environment and Ownership Detection\n\nRead the task's `TaskStartSnapshot` and current repository state. Record:\n\n- root, `HEAD`, branch\u002Fdetached state, upstream divergence, and active Git ops;\n- staged\u002Funstaged\u002Funtracked paths and the task-owned delta;\n- `git worktree list --porcelain`;\n- branch\u002Fworktree creator, task ownership, base branch, and cleanup trigger.\n\nStop on conflicts, unexplained detached state, failed verification, dirty\u002Funtracked state in\na cleanup target, or unknown ownership. Do not infer the base from the names\n`main` or `master`; use task records, repository authority, or explicit user\ndirection. Never auto-stash, reset, clean, pull, rebase, amend, force-push, or\nbypass hooks.\n\nFor a trusted host-managed detached checkout, follow the repository's approved\nmanaged-workspace contract: verify host binding, default cwd, root, and HEAD;\nthen use its scoped local-commit and native handoff path. Report detached HEAD\nin the receipt. This exception does not authorize automatic deletion of the\ndetached checkout or bypass unknown ownership\u002Fbinding.\n\nIf no task-created branch\u002Fworktree exists and integration was not requested,\nskip this workflow: report the local task commit plus `Task clean` and\n`Repository clean`; do not invent merge\u002FPR ceremony.\n\n## Step 2: Fresh Verification\n\nRun the smallest current-authority test set that proves the completed task. If\nit fails, preserve all work and return to diagnosis. Do not present the branch\nas ready.\n\n## Step 3: Choose the Authorized Outcome\n\nWhen a task branch actually needs disposition, present only applicable choices:\n\n1. merge into the recorded base locally;\n2. push and create\u002Fupdate a PR;\n3. keep the branch for later integration;\n4. discard the exact task-owned branch\u002Fworktree.\n\nPush, PR, remote deletion, release, and force operations require explicit user\nauthorization. Discard requires a fresh, exact typed confirmation naming branch,\nworktree path, and commits\u002Fdelta to lose. Generic agreement is insufficient.\n\n## Step 4: Execute Without Hidden Mutation\n\n### Local merge\n\nVerify the target checkout is safe, switch to the recorded base, merge without an implicit pull,\nand rerun verification on the merged result. If integration\nor verification fails, preserve both histories and stop.\n\n### Push or PR\n\nPush only the authorized task branch and create\u002Fupdate the PR with summary and\nfresh test evidence. PR creation does not itself prove merge and does not\nrequire the temporary worktree to remain.\n\n### Keep branch\n\nRetain the branch. Remove a clean task-created temporary worktree by default;\nretain it only for an explicit ongoing-checkout need and report why.\n\n### Discard\n\nAfter exact confirmation, remove only the named clean task-owned worktree, then\nthe named branch. If either differs from the confirmation, stop and ask again.\n\n## Step 5: Prove Integration Before Branch Deletion\n\nUse evidence matching the merge strategy:\n\n- merge\u002Ffast-forward: prove the task tip is an ancestor of the recorded base;\n- squash\u002Frebase: use fresh PR merge metadata plus strategy-appropriate patch\n  equivalence (`git cherry` for rebased commits; stable patch-id or bounded\n  changed-path\u002Ftree comparison for squashes), not an ancestor-only test;\n- unmerged\u002Fopen PR: keep the branch unless discard was exactly confirmed.\n\nNever delete a branch merely because a PR was opened or a similarly named\ncommit exists.\n\n## Step 6: Cleanup in Dependency Order\n\nFor a clean task-owned resource:\n\n1. move to another safe registered checkout; never remove the current working directory;\n2. remove\u002Funregister the worktree first with `git worktree remove \u003Cexact-path>`;\n3. read back `git worktree list --porcelain`;\n4. verify the exact path no longer exists;\n5. only then delete an integrated or exactly confirmed branch;\n6. read back branch refs, `HEAD`, and repository status.\n\nDo not use routine `--force`, global `git worktree prune`, wildcard deletion, or\ncleanup of resources absent from the task ownership record. On Windows, Git may\nunregister a worktree while its directory remains locked: re-check registration\nand the exact resolved path, remove only a proven task-owned clean residual when\nsafe, otherwise retain it and report the lock\u002Fpath. Never widen deletion scope.\n\n## Final Git Receipt\n\nReport:\n\n- current branch and commit SHA\u002Fmessage, or the reason no commit exists;\n- `Task clean: yes|no` and `Repository clean: yes|no` independently;\n- branch\u002Fworktree created, removed, or retained, with evidence\u002Freason;\n- integration evidence and any remaining user action.\n\n`Task clean` means no uncommitted task-owned delta remains. `Repository clean`\nmeans no staged, unstaged, or untracked repository state remains.\n\nThis is a local Git receipt, not authoritative completion or merge truth beyond\nthe evidence read back.\n\n## Integration\n\nCalled only when branch\u002Fworktree integration or explicit lifecycle handling is\nin scope. Pairs with `using-git-worktrees` and\n`verification-before-completion`.\n","# Finishing a Development Branch\n\n## Overview\n\nIntegration choice and checkout lifetime are separate. Verify first, mutate only\ntask-owned resources, then prove what was removed or retained.\n\n**Core principle:** fresh evidence -> authorized integration -> ownership-aware\ncleanup -> Git\u002Fpath readback.\n\n**Announce at start:** explain which branch\u002Fworktree lifecycle is being closed.\n\n## Step 1: Environment and Ownership Detection\n\nRead the task's `TaskStartSnapshot` and current repository state. Record:\n\n- root, `HEAD`, branch\u002Fdetached state, upstream divergence, and active Git ops;\n- staged\u002Funstaged\u002Funtracked paths and the task-owned delta;\n- `git worktree list --porcelain`;\n- branch\u002Fworktree creator, task ownership, base branch, and cleanup trigger.\n\nStop on conflicts, unexplained detached state, failed verification, dirty\u002Funtracked state in\na cleanup target, or unknown ownership. Do not infer the base from the names\n`main` or `master`; use task records, repository authority, or explicit user\ndirection. Never auto-stash, reset, clean, pull, rebase, amend, force-push, or\nbypass hooks.\n\nFor a trusted host-managed detached checkout, follow the repository's approved\nmanaged-workspace contract: verify host binding, default cwd, root, and HEAD;\nthen use its scoped local-commit and native handoff path. Report detached HEAD\nin the receipt. This exception does not authorize automatic deletion of the\ndetached checkout or bypass unknown ownership\u002Fbinding.\n\nIf no task-created branch\u002Fworktree exists and integration was not requested,\nskip this workflow: report the local task commit plus `Task clean` and\n`Repository clean`; do not invent merge\u002FPR ceremony.\n\n## Step 2: Fresh Verification\n\nRun the smallest current-authority test set that proves the completed task. If\nit fails, preserve all work and return to diagnosis. Do not present the branch\nas ready.\n\n## Step 3: Choose the Authorized Outcome\n\nWhen a task branch actually needs disposition, present only applicable choices:\n\n1. merge into the recorded base locally;\n2. push and create\u002Fupdate a PR;\n3. keep the branch for later integration;\n4. discard the exact task-owned branch\u002Fworktree.\n\nPush, PR, remote deletion, release, and force operations require explicit user\nauthorization. Discard requires a fresh, exact typed confirmation naming branch,\nworktree path, and commits\u002Fdelta to lose. Generic agreement is insufficient.\n\n## Step 4: Execute Without Hidden Mutation\n\n### Local merge\n\nVerify the target checkout is safe, switch to the recorded base, merge without an implicit pull,\nand rerun verification on the merged result. If integration\nor verification fails, preserve both histories and stop.\n\n### Push or PR\n\nPush only the authorized task branch and create\u002Fupdate the PR with summary and\nfresh test evidence. PR creation does not itself prove merge and does not\nrequire the temporary worktree to remain.\n\n### Keep branch\n\nRetain the branch. Remove a clean task-created temporary worktree by default;\nretain it only for an explicit ongoing-checkout need and report why.\n\n### Discard\n\nAfter exact confirmation, remove only the named clean task-owned worktree, then\nthe named branch. If either differs from the confirmation, stop and ask again.\n\n## Step 5: Prove Integration Before Branch Deletion\n\nUse evidence matching the merge strategy:\n\n- merge\u002Ffast-forward: prove the task tip is an ancestor of the recorded base;\n- squash\u002Frebase: use fresh PR merge metadata plus strategy-appropriate patch\n  equivalence (`git cherry` for rebased commits; stable patch-id or bounded\n  changed-path\u002Ftree comparison for squashes), not an ancestor-only test;\n- unmerged\u002Fopen PR: keep the branch unless discard was exactly confirmed.\n\nNever delete a branch merely because a PR was opened or a similarly named\ncommit exists.\n\n## Step 6: Cleanup in Dependency Order\n\nFor a clean task-owned resource:\n\n1. move to another safe registered checkout; never remove the current working directory;\n2. remove\u002Funregister the worktree first with `git worktree remove \u003Cexact-path>`;\n3. read back `git worktree list --porcelain`;\n4. verify the exact path no longer exists;\n5. only then delete an integrated or exactly confirmed branch;\n6. read back branch refs, `HEAD`, and repository status.\n\nDo not use routine `--force`, global `git worktree prune`, wildcard deletion, or\ncleanup of resources absent from the task ownership record. On Windows, Git may\nunregister a worktree while its directory remains locked: re-check registration\nand the exact resolved path, remove only a proven task-owned clean residual when\nsafe, otherwise retain it and report the lock\u002Fpath. Never widen deletion scope.\n\n## Final Git Receipt\n\nReport:\n\n- current branch and commit SHA\u002Fmessage, or the reason no commit exists;\n- `Task clean: yes|no` and `Repository clean: yes|no` independently;\n- branch\u002Fworktree created, removed, or retained, with evidence\u002Freason;\n- integration evidence and any remaining user action.\n\n`Task clean` means no uncommitted task-owned delta remains. `Repository clean`\nmeans no staged, unstaged, or untracked repository state remains.\n\nThis is a local Git receipt, not authoritative completion or merge truth beyond\nthe evidence read back.\n\n## Integration\n\nCalled only when branch\u002Fworktree integration or explicit lifecycle handling is\nin scope. Pairs with `using-git-worktrees` and\n`verification-before-completion`.\n",{"name":5,"description":7},"main","59ee67804bc373a9bd079a3a27f47277a6efe564","skill-library\u002Fpacks\u002Factive\u002Ffinishing-a-development-branch","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness","https:\u002F\u002Fgithub.com\u002Fham-zax","2026-11-15 01:18:51",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add ham-zax\u002Fwebharness --skill finishing-a-development-branch",{"tool":36,"command":37},"bunx","bunx skills add ham-zax\u002Fwebharness --skill finishing-a-development-branch",{"tool":39,"command":40},"pnpm","pnpm dlx skills add ham-zax\u002Fwebharness --skill finishing-a-development-branch","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskill-library\u002Fpacks\u002Factive\u002Ffinishing-a-development-branch\u002FSKILL.md",true,[],[45,52,59,66,75,82],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M7AS6BAQQ2WQJYS3WBNJPB2G","x-content","Create, rewrite, critique, select formats for, discover opportunities for, and learn from X\u002FTwitter content and X Articles for a technical AI-native developer\u002Fbuilder account. Use when turning ideas, source posts, releases, benchmarks, results, conversations, authenticated For You or creator-watch opportunities, or project evidence into an Original, Quote, Thread, Reply, or Article; reviewing article titles\u002Foutlines\u002Fvisual briefs\u002Flaunch hooks; improving drafts; choosing additive contributions from live X context; or learning from own-account outcomes. Own content intelligence only; compose with agent-browser for live X state and Growth OS for discovery provenance, approvals, measurement, and publication.","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fx-content\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7AS66FXQR8FEQYW8G8RJB2N","writing-plans","Create detailed implementation plans for multi-step software work before editing code. Use when requirements or a specification must become concrete file-level tasks, interfaces, acceptance criteria, risks, rollout, or explicitly required validation. Default to no test creation, test modification, test execution, TDD, regression-test, or coverage work unless the user, authoritative specification, or mandatory repository policy explicitly requires testing.","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7AS5ZCJX21NF2RESA2QDWPP","systematic-debugging","Root-cause debugging for concrete technical failures including bugs, failing builds or tests, integration issues, performance regressions, and unexpected behavior. Use before proposing or implementing a repair when diagnosis is required. Reproduce the symptom, trace the responsible owner, maintain one leading causal hypothesis, and falsify it with the smallest direct evidence. Compose with Causal Coding for source mutation; testing is opt-in and requires independent authorization.","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[],{"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":19},"01M7AS548FQ63SAB9G0X81VPGJ","skill-creator","Guide for creating and updating high-quality skills by translating workflows, conventions, and reusable processes into well-structured skills. Includes context, use case examples and spec for skills. Use this skill whenever a user asks to create, update, edit, improve, package, or troubleshoot a skill, and also for conversational questions about skills in ChatGPT (e.g., \"What are skills?\", \"What can I use skills for?\", \"What are the best skill use cases for me?\", \"Where can I find my skills?\").","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7AS4XD121Q85Y06EXRGYS4F","reflexion","Self-refinement, multi-perspective critique, verification, and durable lesson curation adapted from NeoLabHQ Reflexion. Use when the user asks to reflect, self-review, critique, double-check, verify and improve prior work, run a rigorous review, memorize lessons, or says \"then reflect\" after a coding, analysis, or writing task. Supports repository-aware evidence gathering and works without subagents or Claude hooks.","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Freflexion\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7AS4RN5TYMA4P6SK6K7NVSR","ponytail","Enforce Ponytail's lazy-senior-developer approach for coding, fixing, refactoring, design, dependency choices, and explicit Ponytail modes such as review, audit, debt, gain, and help. Prefer YAGNI, existing code, standard library, native platform features, existing dependencies, low reader load, and the smallest correct diff. For source mutation, keep Causal Coding authoritative for scope, testing authorization, verification cadence, and stopping. On connected WSL\u002FLinux targets, compose with MCP Harness Router and use `wsl-web-harness` for authoritative repository work.","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002FSKILL.md",[],[]]