[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MM2625X6GFK59VEW0Q1G1B":3,"skill-same:01M6MM2625X6GFK59VEW0Q1G1B":76},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":69},"01M6MM2625X6GFK59VEW0Q1G1B","wrap-up-branch",null,"Use when the user asks to finish a feature branch: missing regression tests, review fixes, docs, and the merge into dev or the given target.","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\u002Freidemeister94\u002Fdevelopment-skills\u002Fskills\u002Fwrap-up-branch\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"up","wrap","wrap up","wrap up branch","branch","docs","finish","align docs","merge","review and fix","review","code","confirmation","only","tests","true","missing","fix","align","feature","2026-11-10 10:12:30",false,"---\nname: wrap-up-branch\ndescription: \"Use when the user asks to finish a feature branch: missing regression tests, review fixes, docs, and the merge into dev or the given target.\"\nargument-hint: \"[target-branch]\"\nuser-invocable: true\ndisable-model-invocation: true\neffort: high\n---\n\n# Wrap up branch\n\nFinish the feature branch on the current checkout so it can land safely.\nInvoking the skill authorizes the in-scope edits, their commits on the feature branch, and the merge of the target into the feature branch (step 5).\nThe merge into the target and any push wait for the final question (step 6).\nRun the steps in order. A failed gate stops the run with a report, because a merge with red checks or open findings moves the problem to the whole team.\nEach step that changes files ends with `development-skills:commit` and a Conventional Commit type that matches it: `test`, `fix`, `docs`, `chore`.\n\n## 1. Resolve the branch, the target, and the scope\n\n- The feature branch is the current `HEAD`. Stop on a detached `HEAD` or when `HEAD` already is the target.\n- The target is `$ARGUMENTS`. Without it, look for `dev`, `develop`, and `development` locally and on `origin`: one candidate is the target; several candidates need one question; none means the default branch.\n- Name a `main` or `master` target as protected in the final question; the answer there is the explicit confirmation those branches require.\n- A dirty working tree stops the discovery: ask once whether to commit the listed paths onto the branch or stop. Never stash on the user's behalf.\n- Run `git fetch origin`, then take the scope as `git diff \u003Cmerge-base>...HEAD` with `git merge-base origin\u002F\u003Ctarget> HEAD` (the local target when no remote exists). Save the diff and the commit list in a temp directory outside the repository. Every following step receives this scope, not the whole repository.\n- Run the project's own checks (tests, lint, type checks from its Makefile, `pyproject.toml`, or `package.json`) as the baseline. A red baseline stops the run: the branch must be green before anything is added to it.\n- State the resolved target and merge-base in chat before step 2, so the user can interrupt before step 5 changes the branch.\n\n## 2. Tests\n\nInvoke `development-skills:create-test` in implementation mode with the branch scope.\nAsk it for the regression proof the branch's new behavior still lacks. Include the failure and boundary cases the diff crosses:\n\n- rejection and empty input;\n- limits, timeout, and retry;\n- permission, concurrency, and partial failure.\n\nJudge the result by failures caught, not by counts. When the project runs a coverage tool, report the coverage of the changed files before and after, without chasing a number.\nA new test that fails against the branch reveals a defect. Fix it when the fix stays within the branch scope; otherwise stop and report it, because widening the branch is the user's decision.\nRun the focused tests, then the project checks.\n\n## 3. Review and fix\n\nInvoke `development-skills:staff-review` on the merge-base range. Give it the linked plan, issue, or pull request description as the requirement when one exists; otherwise it skips the specification verdict.\nFix every `MISSING` or `EXTRA` specification finding and every CRITICAL or HIGH quality finding with the [severity scale](..\u002F..\u002Fshared\u002Freview-categories.md). Report MEDIUM and LOW findings unchanged.\nFix a CRITICAL or HIGH design finding when it stays within the branch's requirement; bring one that challenges the requirement or a plan decision to the user with its alternative.\nRun the affected checks, then re-review the fix diff with the prior findings. Stop and ask after three fix rounds, or when a finding conflicts with a decision the branch already made.\n\n## 4. Documentation\n\nInvoke `development-skills:align-docs` in normal mode with the branch scope as task context. It repairs the entry layer, routes, plans, and chronicles the change invalidates, and archives a plan the branch completed.\nWhen the repository keeps a `CHANGELOG.md`, invoke `development-skills:changelog` in `from-commits` mode for the branch commits.\n\n## 5. Bring the target into the branch\n\nMerge `origin\u002F\u003Ctarget>` (or the local target) into the feature branch first. Conflicts then get resolved on the feature branch, and the checks run on the exact tree that will land.\nOn a conflict, invoke `development-skills:resolve-merge`; complete the merge commit it hands off. A skipped conflict stops the run.\nRun the project checks again on the merged tree. A failure stops the run.\n\n## 6. Merge\n\nPresent the summary in chat:\n\n- the target and its protection;\n- the commits this run added;\n- the checks run and their result;\n- the review verdict and the remaining MEDIUM and LOW findings;\n- the documents changed.\n\nThen ask once with the question tool: `Merge`, `Merge and push`, or `Stop`. Printing the options in chat does not count as asking.\n\nOn `Merge` or `Merge and push`:\n\n1. Check out the target; create it from `origin\u002F\u003Ctarget>` when it exists only there. Update it with `git merge --ff-only origin\u002F\u003Ctarget>` (skip without a remote). A diverged local target stops the run.\n2. Run `git merge --no-ff \u003Cfeature-branch>`. The merge commit keeps the feature as one unit that one revert can undo.\n3. On `Merge and push`, run `git push origin \u003Ctarget>`. A rejected push, such as branch protection, is reported with the pull request alternative; never force it.\n\nLeave the feature branch in place: deleting it is the user's choice.\n\n## Report\n\nLead with the result: merged and pushed, merged locally, or stopped at which gate and why.\nThen list the commits added, the checks with their evidence, the findings left open, and what the run did not verify.\n\nOn Codex, translate skill and question tools with [codex-tools.md](..\u002Fusing-development-skills\u002Freferences\u002Fcodex-tools.md).\n","# Wrap up branch\n\nFinish the feature branch on the current checkout so it can land safely.\nInvoking the skill authorizes the in-scope edits, their commits on the feature branch, and the merge of the target into the feature branch (step 5).\nThe merge into the target and any push wait for the final question (step 6).\nRun the steps in order. A failed gate stops the run with a report, because a merge with red checks or open findings moves the problem to the whole team.\nEach step that changes files ends with `development-skills:commit` and a Conventional Commit type that matches it: `test`, `fix`, `docs`, `chore`.\n\n## 1. Resolve the branch, the target, and the scope\n\n- The feature branch is the current `HEAD`. Stop on a detached `HEAD` or when `HEAD` already is the target.\n- The target is `$ARGUMENTS`. Without it, look for `dev`, `develop`, and `development` locally and on `origin`: one candidate is the target; several candidates need one question; none means the default branch.\n- Name a `main` or `master` target as protected in the final question; the answer there is the explicit confirmation those branches require.\n- A dirty working tree stops the discovery: ask once whether to commit the listed paths onto the branch or stop. Never stash on the user's behalf.\n- Run `git fetch origin`, then take the scope as `git diff \u003Cmerge-base>...HEAD` with `git merge-base origin\u002F\u003Ctarget> HEAD` (the local target when no remote exists). Save the diff and the commit list in a temp directory outside the repository. Every following step receives this scope, not the whole repository.\n- Run the project's own checks (tests, lint, type checks from its Makefile, `pyproject.toml`, or `package.json`) as the baseline. A red baseline stops the run: the branch must be green before anything is added to it.\n- State the resolved target and merge-base in chat before step 2, so the user can interrupt before step 5 changes the branch.\n\n## 2. Tests\n\nInvoke `development-skills:create-test` in implementation mode with the branch scope.\nAsk it for the regression proof the branch's new behavior still lacks. Include the failure and boundary cases the diff crosses:\n\n- rejection and empty input;\n- limits, timeout, and retry;\n- permission, concurrency, and partial failure.\n\nJudge the result by failures caught, not by counts. When the project runs a coverage tool, report the coverage of the changed files before and after, without chasing a number.\nA new test that fails against the branch reveals a defect. Fix it when the fix stays within the branch scope; otherwise stop and report it, because widening the branch is the user's decision.\nRun the focused tests, then the project checks.\n\n## 3. Review and fix\n\nInvoke `development-skills:staff-review` on the merge-base range. Give it the linked plan, issue, or pull request description as the requirement when one exists; otherwise it skips the specification verdict.\nFix every `MISSING` or `EXTRA` specification finding and every CRITICAL or HIGH quality finding with the [severity scale](..\u002F..\u002Fshared\u002Freview-categories.md). Report MEDIUM and LOW findings unchanged.\nFix a CRITICAL or HIGH design finding when it stays within the branch's requirement; bring one that challenges the requirement or a plan decision to the user with its alternative.\nRun the affected checks, then re-review the fix diff with the prior findings. Stop and ask after three fix rounds, or when a finding conflicts with a decision the branch already made.\n\n## 4. Documentation\n\nInvoke `development-skills:align-docs` in normal mode with the branch scope as task context. It repairs the entry layer, routes, plans, and chronicles the change invalidates, and archives a plan the branch completed.\nWhen the repository keeps a `CHANGELOG.md`, invoke `development-skills:changelog` in `from-commits` mode for the branch commits.\n\n## 5. Bring the target into the branch\n\nMerge `origin\u002F\u003Ctarget>` (or the local target) into the feature branch first. Conflicts then get resolved on the feature branch, and the checks run on the exact tree that will land.\nOn a conflict, invoke `development-skills:resolve-merge`; complete the merge commit it hands off. A skipped conflict stops the run.\nRun the project checks again on the merged tree. A failure stops the run.\n\n## 6. Merge\n\nPresent the summary in chat:\n\n- the target and its protection;\n- the commits this run added;\n- the checks run and their result;\n- the review verdict and the remaining MEDIUM and LOW findings;\n- the documents changed.\n\nThen ask once with the question tool: `Merge`, `Merge and push`, or `Stop`. Printing the options in chat does not count as asking.\n\nOn `Merge` or `Merge and push`:\n\n1. Check out the target; create it from `origin\u002F\u003Ctarget>` when it exists only there. Update it with `git merge --ff-only origin\u002F\u003Ctarget>` (skip without a remote). A diverged local target stops the run.\n2. Run `git merge --no-ff \u003Cfeature-branch>`. The merge commit keeps the feature as one unit that one revert can undo.\n3. On `Merge and push`, run `git push origin \u003Ctarget>`. A rejected push, such as branch protection, is reported with the pull request alternative; never force it.\n\nLeave the feature branch in place: deleting it is the user's choice.\n\n## Report\n\nLead with the result: merged and pushed, merged locally, or stopped at which gate and why.\nThen list the commits added, the checks with their evidence, the findings left open, and what the run did not verify.\n\nOn Codex, translate skill and question tools with [codex-tools.md](..\u002Fusing-development-skills\u002Freferences\u002Fcodex-tools.md).\n",{"name":5,"effort":44,"description":7,"argument-hint":45,"user-invocable":46,"disable-model-invocation":46},"high","[target-branch]",true,"main","2a6d24be2ed571c5ff2319c506b60741bbcb1cb0","plugins\u002Freidemeister94\u002Fdevelopment-skills\u002Fskills\u002Fwrap-up-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":58,"prompt":68,"zipAvailable":46},[59,62,65],{"tool":60,"command":61},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill wrap-up-branch",{"tool":63,"command":64},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill wrap-up-branch",{"tool":66,"command":67},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill wrap-up-branch","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Freidemeister94\u002Fdevelopment-skills\u002Fskills\u002Fwrap-up-branch\u002FSKILL.md",[70],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"agents\u002Fopenai.yaml","REFERENCE","参考文档",358,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Freidemeister94\u002Fdevelopment-skills\u002Fskills\u002Fwrap-up-branch\u002Fagents\u002Fopenai.yaml",[77,87,95,103,111,119],{"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":81,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":86},"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":86},"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":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":86},"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":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":86},"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":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":86},"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":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":123,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":86},"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",[],[]]