[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75BVR6VB05502DRYKENWB0Z":3,"skill-same:01M75BVR6VB05502DRYKENWB0Z":51},{"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":29,"updatedAt":30,"install":31,"resources":44},"01M75BVR6VB05502DRYKENWB0Z","finish-branch",null,"Wrap up the current branch or worktree: clean up debugging leftovers, run final verification, then let the user decide whether to merge, keep, open a PR, or discard.","RollRollRoll\u002Fagent-toolkit","RollRollRoll","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F15213243?v=4","01M75BTX9MEYV2TFZ65FRKG3H7","kgfan","01M75BTXAE7M0DQ4EPDF12BZHN",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FRollRollRoll\u002Fagent-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopment\u002Ffinish-branch\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: finish-branch\ndescription: \"Wrap up the current branch or worktree: clean up debugging leftovers, run final verification, then let the user decide whether to merge, keep, open a PR, or discard.\"\n---\n\n# Finish Branch: Wrapping Up Development\n\n## Goal\n\nAfter a stretch of development is **implemented**, **wrap up** the current branch \u002F worktree: first run a read-only state preflight, then clean up debugging leftovers and run the final tests,\nand finally offer the options \"merge \u002F keep locally \u002F create PR \u002F discard\", leaving destructive and external actions to the user.\n\nUse it after development is done, to clean up leftovers, run final verification, and decide where the branch goes. Setting up a workspace is not its job.\n\n## Invocation contract\n\n**Inputs**\n\n- **Final verification command**: how to run the project's full acceptance check.\n- **Scope of this development** (optional): used to judge which debugging leftovers were introduced by this work; if not given, clean only what can be confirmed.\n- **Caller** (optional): when called by another skill, state the caller. If the cleanup produces code changes, control must go back to the caller to redo the overall acceptance check.\n\n**Returns**\n\n- Preflight conclusion (branch \u002F worktree \u002F staged and untracked state, ahead\u002Fbehind relative to the main branch).\n- What was cleaned up, final test results, the wrap-up option the user chose, and **the actions actually taken**.\n- For an unauthorized action, stop before it and report truthfully; do not decide for the user.\n\n**Responsibility boundaries**\n\n- Do not wrap up if tests fail. Do not automatically commit \u002F merge \u002F push \u002F open a PR \u002F delete a branch \u002F remove a worktree; get confirmation for each one separately.\n- Do not automatically stash, `git clean`, or silently discard to create a \"clean state\".\n- Do not set up a workspace or do code review; this skill only wraps up.\n\n## When to use \u002F when not to use\n\n**Use it when**:\n\n- A stretch of development is done and tests pass, and you need to decide what to do with the branch.\n- Wrapping up after the overall acceptance check passes.\n- You finished work in a worktree and want to merge it back and clean up the worktree.\n\n**Do not use it when**:\n\n- Development is not finished or tests fail: finish development and fix the tests first, then wrap up.\n- You need to set up an isolated workspace: that is not this skill's job.\n\n## Core flow (state preflight → clean up debugging leftovers → final verification → offer options → execute with authorization)\n\n1. **Run a read-only state preflight first**:\n   - Confirm the current branch, whether you are in a worktree, and staged \u002F unstaged \u002F untracked state.\n   - If there are any non-ignored changes on entry, show a summary and stop, and let the user decide. **Do not clean up, commit, stash, or discard first**, so user changes do not get mixed into the wrap-up.\n2. **Clean up debugging leftovers from this development**:\n   - Check this diff for temporary logs, debug prints, breakpoints, temporary flags, and code added only to investigate a problem.\n   - Clean up only leftovers you can confirm this development introduced. When the purpose is unclear, ask the user first; do not touch unrelated code along the way.\n   - Cleanup must happen before the final tests, so a \"green before cleanup\" result is not taken as the final result.\n3. **Run the final tests and confirm all green**: run the full acceptance check the project defines. **Not green, no wrap-up**: go back and fix, then rerun the final tests.\n4. **Recheck repo \u002F worktree state**:\n   - If cleanup produced changes, show the diff and get explicit commit authorization before committing; after committing, confirm the state is clean again.\n   - If cleanup produced code changes, control must go back to the caller to redo the overall acceptance check; the review conclusion from before cleanup cannot be reused.\n   - Relationship to the main branch (how many commits ahead \u002F behind).\n5. **Offer the wrap-up options**:\n   - **Merge to main**: merge back into the main branch.\n   - **Keep locally**: leave it on the branch, do not merge yet.\n   - **Create PR**: push and open a PR; write the PR body by invoking `pr` with the Skill tool.\n   - **Discard**: abandon this work (delete the branch \u002F worktree). **Irreversible**.\n6. **Execute after getting the matching authorization**:\n   - `git commit`, merge, push, creating a PR, and deleting a branch all need the user's explicit confirmation of the specific action before running.\n   - Even if the code is merged or discarding is decided, `git worktree remove` needs separate confirmation; do not read \"chose merge\" as also authorizing removal of the worktree.\n   - For keep locally, only report the branch \u002F worktree path and state; do not make implicit commits or cleanups.\n\n## Safety gates\n\n- **⚠️ State changes need explicit user confirmation, never automatic**: commit, merge, push, create PR, delete branch, discard, remove worktree. Follow the current repo's `CLAUDE.md` \u002F `AGENTS.md` and the platform's approval policy.\n- **No wrap-up if tests fail**: go back and get them green first.\n- **Tests must come after debug cleanup**: any cleanup or fix invalidates earlier test results, so rerun them.\n- **The overall acceptance check also goes stale**: if cleanup produces code changes after the overall acceptance check passed, review again.\n- **Discarding is irreversible**: **confirm twice** before deleting a branch; also get explicit confirmation before removing a worktree.\n- **Detect before acting**: acting before the state is clear (wrong branch, missed uncommitted changes) can cause damage.\n- **No implicit fallbacks**: do not use automatic stash, automatic commits, `git clean`, or silent discards to create a \"clean state\".\n\n> Check: does every commit, merge, push, PR, deletion, or worktree removal you are about to run have explicit authorization for that action? If one is missing, stop before it.\n\n## Common mistakes\n\n- Wrapping up \u002F merging when tests fail.\n- Running tests first, deleting debug prints afterwards, and not rerunning tests.\n- Starting cleanup when there were dirty changes on entry, mixing user changes into the wrap-up.\n- Changing code after the overall acceptance check and then merging on the old review conclusion.\n- Finding uncommitted changes and automatically committing \u002F stashing to keep the flow going.\n- Automatically merging \u002F pushing \u002F opening a PR without letting the user decide (dangerous operation).\n- Removing the worktree after the merge is approved: the user only confirmed the merge, not the removal.\n- Discarding (deleting the branch) without a second confirmation.\n- Acting without checking state: on the wrong branch \u002F missing uncommitted changes.\n- Setting up a workspace here: out of scope, this skill only wraps up.\n","# Finish Branch: Wrapping Up Development\n\n## Goal\n\nAfter a stretch of development is **implemented**, **wrap up** the current branch \u002F worktree: first run a read-only state preflight, then clean up debugging leftovers and run the final tests,\nand finally offer the options \"merge \u002F keep locally \u002F create PR \u002F discard\", leaving destructive and external actions to the user.\n\nUse it after development is done, to clean up leftovers, run final verification, and decide where the branch goes. Setting up a workspace is not its job.\n\n## Invocation contract\n\n**Inputs**\n\n- **Final verification command**: how to run the project's full acceptance check.\n- **Scope of this development** (optional): used to judge which debugging leftovers were introduced by this work; if not given, clean only what can be confirmed.\n- **Caller** (optional): when called by another skill, state the caller. If the cleanup produces code changes, control must go back to the caller to redo the overall acceptance check.\n\n**Returns**\n\n- Preflight conclusion (branch \u002F worktree \u002F staged and untracked state, ahead\u002Fbehind relative to the main branch).\n- What was cleaned up, final test results, the wrap-up option the user chose, and **the actions actually taken**.\n- For an unauthorized action, stop before it and report truthfully; do not decide for the user.\n\n**Responsibility boundaries**\n\n- Do not wrap up if tests fail. Do not automatically commit \u002F merge \u002F push \u002F open a PR \u002F delete a branch \u002F remove a worktree; get confirmation for each one separately.\n- Do not automatically stash, `git clean`, or silently discard to create a \"clean state\".\n- Do not set up a workspace or do code review; this skill only wraps up.\n\n## When to use \u002F when not to use\n\n**Use it when**:\n\n- A stretch of development is done and tests pass, and you need to decide what to do with the branch.\n- Wrapping up after the overall acceptance check passes.\n- You finished work in a worktree and want to merge it back and clean up the worktree.\n\n**Do not use it when**:\n\n- Development is not finished or tests fail: finish development and fix the tests first, then wrap up.\n- You need to set up an isolated workspace: that is not this skill's job.\n\n## Core flow (state preflight → clean up debugging leftovers → final verification → offer options → execute with authorization)\n\n1. **Run a read-only state preflight first**:\n   - Confirm the current branch, whether you are in a worktree, and staged \u002F unstaged \u002F untracked state.\n   - If there are any non-ignored changes on entry, show a summary and stop, and let the user decide. **Do not clean up, commit, stash, or discard first**, so user changes do not get mixed into the wrap-up.\n2. **Clean up debugging leftovers from this development**:\n   - Check this diff for temporary logs, debug prints, breakpoints, temporary flags, and code added only to investigate a problem.\n   - Clean up only leftovers you can confirm this development introduced. When the purpose is unclear, ask the user first; do not touch unrelated code along the way.\n   - Cleanup must happen before the final tests, so a \"green before cleanup\" result is not taken as the final result.\n3. **Run the final tests and confirm all green**: run the full acceptance check the project defines. **Not green, no wrap-up**: go back and fix, then rerun the final tests.\n4. **Recheck repo \u002F worktree state**:\n   - If cleanup produced changes, show the diff and get explicit commit authorization before committing; after committing, confirm the state is clean again.\n   - If cleanup produced code changes, control must go back to the caller to redo the overall acceptance check; the review conclusion from before cleanup cannot be reused.\n   - Relationship to the main branch (how many commits ahead \u002F behind).\n5. **Offer the wrap-up options**:\n   - **Merge to main**: merge back into the main branch.\n   - **Keep locally**: leave it on the branch, do not merge yet.\n   - **Create PR**: push and open a PR; write the PR body by invoking `pr` with the Skill tool.\n   - **Discard**: abandon this work (delete the branch \u002F worktree). **Irreversible**.\n6. **Execute after getting the matching authorization**:\n   - `git commit`, merge, push, creating a PR, and deleting a branch all need the user's explicit confirmation of the specific action before running.\n   - Even if the code is merged or discarding is decided, `git worktree remove` needs separate confirmation; do not read \"chose merge\" as also authorizing removal of the worktree.\n   - For keep locally, only report the branch \u002F worktree path and state; do not make implicit commits or cleanups.\n\n## Safety gates\n\n- **⚠️ State changes need explicit user confirmation, never automatic**: commit, merge, push, create PR, delete branch, discard, remove worktree. Follow the current repo's `CLAUDE.md` \u002F `AGENTS.md` and the platform's approval policy.\n- **No wrap-up if tests fail**: go back and get them green first.\n- **Tests must come after debug cleanup**: any cleanup or fix invalidates earlier test results, so rerun them.\n- **The overall acceptance check also goes stale**: if cleanup produces code changes after the overall acceptance check passed, review again.\n- **Discarding is irreversible**: **confirm twice** before deleting a branch; also get explicit confirmation before removing a worktree.\n- **Detect before acting**: acting before the state is clear (wrong branch, missed uncommitted changes) can cause damage.\n- **No implicit fallbacks**: do not use automatic stash, automatic commits, `git clean`, or silent discards to create a \"clean state\".\n\n> Check: does every commit, merge, push, PR, deletion, or worktree removal you are about to run have explicit authorization for that action? If one is missing, stop before it.\n\n## Common mistakes\n\n- Wrapping up \u002F merging when tests fail.\n- Running tests first, deleting debug prints afterwards, and not rerunning tests.\n- Starting cleanup when there were dirty changes on entry, mixing user changes into the wrap-up.\n- Changing code after the overall acceptance check and then merging on the old review conclusion.\n- Finding uncommitted changes and automatically committing \u002F stashing to keep the flow going.\n- Automatically merging \u002F pushing \u002F opening a PR without letting the user decide (dangerous operation).\n- Removing the worktree after the merge is approved: the user only confirmed the merge, not the removal.\n- Discarding (deleting the branch) without a second confirmation.\n- Acting without checking state: on the wrong branch \u002F missing uncommitted changes.\n- Setting up a workspace here: out of scope, this skill only wraps up.\n",{"name":5,"description":7},"main","7d691099ecfe5a86d66b627266b7ff2998f8a63f","skills\u002Fdevelopment\u002Ffinish-branch","https:\u002F\u002Fgithub.com\u002FRollRollRoll\u002Fagent-toolkit","https:\u002F\u002Fgithub.com\u002FRollRollRoll","Do Do Do !","2026-11-03 16:20:15",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add RollRollRoll\u002Fagent-toolkit --skill finish-branch",{"tool":37,"command":38},"bunx","bunx skills add RollRollRoll\u002Fagent-toolkit --skill finish-branch",{"tool":40,"command":41},"pnpm","pnpm dlx skills add RollRollRoll\u002Fagent-toolkit --skill finish-branch","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FRollRollRoll\u002Fagent-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopment\u002Ffinish-branch\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",327,"https:\u002F\u002Fgithub.com\u002FRollRollRoll\u002Fagent-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopment\u002Ffinish-branch\u002Fagents\u002Fopenai.yaml",[52,61,68,76,84,92],{"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":56,"licenseFileUrl":57,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M75BYT7NM9FZW238XWS3GPXA","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","MIT","https:\u002F\u002Fgithub.com\u002FRollRollRoll\u002Fagent-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Fsupport\u002Fwriting-for-agents\u002FLICENSE.upstream","https:\u002F\u002Fgithub.com\u002FRollRollRoll\u002Fagent-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Fsupport\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M75BYHZGRVHR4GEY5MAHY5XV","test-skill","Blind-test a target skill in an isolated sandbox, collect evidence through headless runs, and produce a step-by-step traceable retrospective report in Chinese.","https:\u002F\u002Fgithub.com\u002FRollRollRoll\u002Fagent-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Fsupport\u002Ftest-skill\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":56,"licenseFileUrl":72,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M75BYETS35KTJZ5W3EBNF7GS","teach","Teach the user a new skill or concept, within this workspace.","https:\u002F\u002Fgithub.com\u002FRollRollRoll\u002Fagent-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Fsupport\u002Fteach\u002FLICENSE.upstream","https:\u002F\u002Fgithub.com\u002FRollRollRoll\u002Fagent-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Fsupport\u002Fteach\u002FSKILL.md",[],[],{"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":56,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M75BYC50PVV26NS2S1CGHGFH","retro","Conduct a retrospective on a coding session.","https:\u002F\u002Fgithub.com\u002FRollRollRoll\u002Fagent-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Fsupport\u002Fretro\u002FLICENSE.upstream","https:\u002F\u002Fgithub.com\u002FRollRollRoll\u002Fagent-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Fsupport\u002Fretro\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":56,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M75BY9Q6BN1DZPTNKTDAV9PN","re-explain","Re-explain earlier content in simple, clear Chinese, filling in the context needed to follow it.","https:\u002F\u002Fgithub.com\u002FRollRollRoll\u002Fagent-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Fsupport\u002Fre-explain\u002FLICENSE.upstream","https:\u002F\u002Fgithub.com\u002FRollRollRoll\u002Fagent-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Fsupport\u002Fre-explain\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":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M75BY6XMK229A7QB20FP7F34","notify-test","Send a test Telegram notification through the agent-notify hooks and report whether the token and chat_id work. Use when the user asks to test or verify agent notifications.","https:\u002F\u002Fgithub.com\u002FRollRollRoll\u002Fagent-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Fsupport\u002Fnotify-test\u002FSKILL.md",[],[]]