[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MPBBSJV9CY34X3DWQC3NF7":3,"skill-same:01M6MPBBSJV9CY34X3DWQC3NF7":66},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":47,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M6MPBBSJV9CY34X3DWQC3NF7","finishing-a-development-branch-lite",null,"Use when implementation is complete and you need to merge a worktree branch back into the original base branch with build\u002Fcompile verification (no tests)","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\u002Fyyykf\u002Fspellbook-skills\u002Fskills\u002Ffinishing-a-development-branch-lite\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"finishing a development branch","development","finishing a development branch lite","branch","when","merge","you","with","complete","tests","base","back","build","implementation","use","worktree","compile","verification","2026-11-10 10:12:30",false,"---\nname: finishing-a-development-branch-lite\ndescription: Use when implementation is complete and you need to merge a worktree branch back into the original base branch with build\u002Fcompile verification (no tests)\n---\n\n# Finishing a Development Branch Lite\n\n## Overview\nFinish development work by verifying a build\u002Fcompile check, presenting merge options, and cleaning up the worktree.\n\n**Core principle:** Build\u002Fcompile first → confirm base branch → present options → execute → cleanup.\n\n**Announce at start:** \"I'm using the finishing-a-development-branch-lite skill to complete this work.\"\n\n## The Process\n\n### Step 1: Verify Build\u002FCompile (No Tests)\n\n1. Check `AGENTS.md` for build\u002Fcompile commands. If present, follow it.\n2. Otherwise use default build\u002Fcompile commands:\n\n```bash\n# Node.js (requires build script)\nif [ -f package.json ]; then npm run -s build; fi\n\n# Rust\nif [ -f Cargo.toml ]; then cargo build; fi\n\n# Go\nif [ -f go.mod ]; then go build .\u002F...; fi\n\n# Python\nif [ -f pyproject.toml ] || [ -f requirements.txt ]; then python -m compileall .; fi\n\n# Java (Maven)\nif [ -f pom.xml ]; then mvn -q clean compile; fi\n```\n\nIf no build command is available (e.g., no npm build script), ask the user for the correct command.\n\n**If build fails:**\n```\nBuild\u002Fcompile failing (\u003CN> failures). Must fix before completing.\n\n[Show failures]\n```\n\nStop. Do not proceed to Step 2.\n\n### Step 2: Determine Base Branch (Merge Target)\n\nPrefer extracting the base branch from the worktree branch name using the delimiter:\n\n```\n__wt__\n```\n\nExample:\n\n```\nfeature\u002Fauth__wt__login -> base branch: feature\u002Fauth\n```\n\nIf extracted, verify the **local** branch exists:\n\n```bash\ngit show-ref --verify refs\u002Fheads\u002F\u003Cbase-branch>\n```\n\nIf it exists, confirm with the user before merging. If it does not exist, ask the user to provide the base branch.\n\n### Step 3: Present Options\n\nPresent exactly these 4 options:\n\n```\nImplementation complete. What would you like to do?\n\n1. Merge back to \u003Cbase-branch> locally\n2. Push and create a Pull Request\n3. Keep the branch as-is (I'll handle it later)\n4. Discard this work\n\nWhich option?\n```\n\n### Step 4: Execute Choice\n\n#### Option 1: Merge Locally\n\n**Important:** Run the merge from the base-branch worktree (the directory where the base branch is checked out), not from the worktree branch directory.\n\n```bash\n# Switch to base branch\ngit checkout \u003Cbase-branch>\n\n# Pull latest (if appropriate)\ngit pull\n\n# Merge feature branch\ngit merge \u003Cfeature-branch>\n\n# Verify build\u002Fcompile on merged result\n\u003Cbuild command>\n\n# If build passes\ngit branch -d \u003Cfeature-branch>\n```\n\nThen: Cleanup worktree (Step 5)\n\n#### Option 2: Push and Create PR\n\n```bash\n# Push branch\ngit push -u origin \u003Cfeature-branch>\n\n# Create PR\ngh pr create --title \"\u003Ctitle>\" --body \"\u003Csummary and build steps>\"\n```\n\nThen: Cleanup worktree (Step 5)\n\n#### Option 3: Keep As-Is\n\nReport: \"Keeping branch \u003Cname>. Worktree preserved at \u003Cpath>.\"\n\n**Do not cleanup worktree.**\n\n#### Option 4: Discard\n\n**Confirm first:**\n```\nThis will permanently delete:\n- Branch \u003Cname>\n- All commits: \u003Ccommit-list>\n- Worktree at \u003Cpath>\n\nType 'discard' to confirm.\n```\n\nWait for exact confirmation.\n\nIf confirmed:\n```bash\ngit checkout \u003Cbase-branch>\ngit branch -D \u003Cfeature-branch>\n```\n\nThen: Cleanup worktree (Step 5)\n\n### Step 5: Cleanup Worktree\n\n**For Options 1, 2, 4:**\n\nBefore removing a worktree, change into a directory that will remain (e.g., the base-branch worktree). Removing the current directory will break the session.\n\n```bash\ngit worktree list | grep $(git branch --show-current)\n```\n\nIf yes:\n```bash\ngit worktree remove \u003Cworktree-path>\n```\n\n**For Option 3:** Keep worktree.\n\n## Quick Reference\n\n| Option | Merge | Push | Keep Worktree | Cleanup Branch |\n| --- | --- | --- | --- | --- |\n| 1. Merge locally | ✓ | - | - | ✓ |\n| 2. Create PR | - | ✓ | ✓ | - |\n| 3. Keep as-is | - | - | ✓ | - |\n| 4. Discard | - | - | - | ✓ (force) |\n\n## Common Mistakes\n\n**Assuming main\u002Fmaster as base branch**\n- **Problem:** Merges into the wrong branch\n- **Fix:** Confirm the original base branch\n\n**Skipping build verification**\n- **Problem:** Merge broken code\n- **Fix:** Build\u002Fcompile must pass before proceeding\n\n**Discarding without confirmation**\n- **Problem:** Permanent data loss\n- **Fix:** Require typed 'discard'\n\n**Skipping base-branch confirmation because \"it should be obvious\"**\n- **Problem:** Merge target drifts\n- **Fix:** Ask, then proceed\n\n## Rationalization Table\n\n| Excuse | Reality |\n| --- | --- |\n| \"I'll merge this into main, it's fine\" | Merge into the original base branch unless user says otherwise |\n| \"Build is optional\" | Build\u002Fcompile is the gate for completion |\n| \"Discard is reversible\" | Discard is permanent and requires confirmation |\n\n## Red Flags\n\n- \"I'll just merge to main\u002Fmaster\"\n- \"Build can wait until after merge\"\n- \"Discard without asking is faster\"\n\n## Example\n\n```bash\n# Build\u002Fcompile\nmvn -q clean compile\n\n# Merge to base branch\nbase_branch=feature\u002Fauth\nfeature_branch=feature\u002Fauth-impl\n\ngit checkout \"$base_branch\"\ngit pull\ngit merge \"$feature_branch\"\n\n# Verify build\u002Fcompile again\nmvn -q clean compile\n```\n","# Finishing a Development Branch Lite\n\n## Overview\nFinish development work by verifying a build\u002Fcompile check, presenting merge options, and cleaning up the worktree.\n\n**Core principle:** Build\u002Fcompile first → confirm base branch → present options → execute → cleanup.\n\n**Announce at start:** \"I'm using the finishing-a-development-branch-lite skill to complete this work.\"\n\n## The Process\n\n### Step 1: Verify Build\u002FCompile (No Tests)\n\n1. Check `AGENTS.md` for build\u002Fcompile commands. If present, follow it.\n2. Otherwise use default build\u002Fcompile commands:\n\n```bash\n# Node.js (requires build script)\nif [ -f package.json ]; then npm run -s build; fi\n\n# Rust\nif [ -f Cargo.toml ]; then cargo build; fi\n\n# Go\nif [ -f go.mod ]; then go build .\u002F...; fi\n\n# Python\nif [ -f pyproject.toml ] || [ -f requirements.txt ]; then python -m compileall .; fi\n\n# Java (Maven)\nif [ -f pom.xml ]; then mvn -q clean compile; fi\n```\n\nIf no build command is available (e.g., no npm build script), ask the user for the correct command.\n\n**If build fails:**\n```\nBuild\u002Fcompile failing (\u003CN> failures). Must fix before completing.\n\n[Show failures]\n```\n\nStop. Do not proceed to Step 2.\n\n### Step 2: Determine Base Branch (Merge Target)\n\nPrefer extracting the base branch from the worktree branch name using the delimiter:\n\n```\n__wt__\n```\n\nExample:\n\n```\nfeature\u002Fauth__wt__login -> base branch: feature\u002Fauth\n```\n\nIf extracted, verify the **local** branch exists:\n\n```bash\ngit show-ref --verify refs\u002Fheads\u002F\u003Cbase-branch>\n```\n\nIf it exists, confirm with the user before merging. If it does not exist, ask the user to provide the base branch.\n\n### Step 3: Present Options\n\nPresent exactly these 4 options:\n\n```\nImplementation complete. What would you like to do?\n\n1. Merge back to \u003Cbase-branch> locally\n2. Push and create a Pull Request\n3. Keep the branch as-is (I'll handle it later)\n4. Discard this work\n\nWhich option?\n```\n\n### Step 4: Execute Choice\n\n#### Option 1: Merge Locally\n\n**Important:** Run the merge from the base-branch worktree (the directory where the base branch is checked out), not from the worktree branch directory.\n\n```bash\n# Switch to base branch\ngit checkout \u003Cbase-branch>\n\n# Pull latest (if appropriate)\ngit pull\n\n# Merge feature branch\ngit merge \u003Cfeature-branch>\n\n# Verify build\u002Fcompile on merged result\n\u003Cbuild command>\n\n# If build passes\ngit branch -d \u003Cfeature-branch>\n```\n\nThen: Cleanup worktree (Step 5)\n\n#### Option 2: Push and Create PR\n\n```bash\n# Push branch\ngit push -u origin \u003Cfeature-branch>\n\n# Create PR\ngh pr create --title \"\u003Ctitle>\" --body \"\u003Csummary and build steps>\"\n```\n\nThen: Cleanup worktree (Step 5)\n\n#### Option 3: Keep As-Is\n\nReport: \"Keeping branch \u003Cname>. Worktree preserved at \u003Cpath>.\"\n\n**Do not cleanup worktree.**\n\n#### Option 4: Discard\n\n**Confirm first:**\n```\nThis will permanently delete:\n- Branch \u003Cname>\n- All commits: \u003Ccommit-list>\n- Worktree at \u003Cpath>\n\nType 'discard' to confirm.\n```\n\nWait for exact confirmation.\n\nIf confirmed:\n```bash\ngit checkout \u003Cbase-branch>\ngit branch -D \u003Cfeature-branch>\n```\n\nThen: Cleanup worktree (Step 5)\n\n### Step 5: Cleanup Worktree\n\n**For Options 1, 2, 4:**\n\nBefore removing a worktree, change into a directory that will remain (e.g., the base-branch worktree). Removing the current directory will break the session.\n\n```bash\ngit worktree list | grep $(git branch --show-current)\n```\n\nIf yes:\n```bash\ngit worktree remove \u003Cworktree-path>\n```\n\n**For Option 3:** Keep worktree.\n\n## Quick Reference\n\n| Option | Merge | Push | Keep Worktree | Cleanup Branch |\n| --- | --- | --- | --- | --- |\n| 1. Merge locally | ✓ | - | - | ✓ |\n| 2. Create PR | - | ✓ | ✓ | - |\n| 3. Keep as-is | - | - | ✓ | - |\n| 4. Discard | - | - | - | ✓ (force) |\n\n## Common Mistakes\n\n**Assuming main\u002Fmaster as base branch**\n- **Problem:** Merges into the wrong branch\n- **Fix:** Confirm the original base branch\n\n**Skipping build verification**\n- **Problem:** Merge broken code\n- **Fix:** Build\u002Fcompile must pass before proceeding\n\n**Discarding without confirmation**\n- **Problem:** Permanent data loss\n- **Fix:** Require typed 'discard'\n\n**Skipping base-branch confirmation because \"it should be obvious\"**\n- **Problem:** Merge target drifts\n- **Fix:** Ask, then proceed\n\n## Rationalization Table\n\n| Excuse | Reality |\n| --- | --- |\n| \"I'll merge this into main, it's fine\" | Merge into the original base branch unless user says otherwise |\n| \"Build is optional\" | Build\u002Fcompile is the gate for completion |\n| \"Discard is reversible\" | Discard is permanent and requires confirmation |\n\n## Red Flags\n\n- \"I'll just merge to main\u002Fmaster\"\n- \"Build can wait until after merge\"\n- \"Discard without asking is faster\"\n\n## Example\n\n```bash\n# Build\u002Fcompile\nmvn -q clean compile\n\n# Merge to base branch\nbase_branch=feature\u002Fauth\nfeature_branch=feature\u002Fauth-impl\n\ngit checkout \"$base_branch\"\ngit pull\ngit merge \"$feature_branch\"\n\n# Verify build\u002Fcompile again\nmvn -q clean compile\n```\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fyyykf\u002Fspellbook-skills\u002Fskills\u002Ffinishing-a-development-branch-lite",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":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill finishing-a-development-branch-lite",{"tool":58,"command":59},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill finishing-a-development-branch-lite",{"tool":61,"command":62},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill finishing-a-development-branch-lite","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyyykf\u002Fspellbook-skills\u002Fskills\u002Ffinishing-a-development-branch-lite\u002FSKILL.md",true,[],[67,75,82,89,113,137],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":74},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"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":74},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\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":74},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":37},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[96,97,98,99,100,101,102,103,104,105,106,23,25,107,108,109,110,111,24,112],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","done","reviewer","io","change","cli","past",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":37},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[120,121,122,109,26,123,124,125,126,127,128,129,130,131,101,132,133,134,135,136],"deja reflect","reflect","review","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"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":154,"publishedAt":37},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[143,148,151],{"categoryNo":144,"categoryName":145,"taxonomyType":146,"taxonomyTypeDesc":147},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":149,"categoryName":150,"taxonomyType":146,"taxonomyTypeDesc":147},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":152,"categoryName":153,"taxonomyType":146,"taxonomyTypeDesc":147},"01JBSEEDCAT000000000000010","后端与接口",[139,155,156,157,158,159,160,133,161,102,162,163,164,165,23,166,167,168,169,170],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]