[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AGHMC4FYMSBTMKCNEXKGPV":3,"skill-same:01M7AGHMC4FYMSBTMKCNEXKGPV":61},{"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":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":39,"ownerHtmlUrl":40,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":41,"install":42,"resources":54},"01M7AGHMC4FYMSBTMKCNEXKGPV","trove-ship",null,"Front-door ship workflow. Prepare a change for landing by composing the review and commit skills, surfacing a final Decision Gate before any destructive action. Thin orchestrator — defers detail to leaf skills.","bravew\u002Ftrove","bravew","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10855844?v=4","01M7ACJ91JZSQYHT81XPVYR7VA","Yong","01M7AFERNR92HDPGNGP5QA16DM",10,"MIT","https:\u002F\u002Fgithub.com\u002Fbravew\u002Ftrove\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Ftrove-ship\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: trove-ship\ndescription: \"Front-door ship workflow. Prepare a change for landing by composing the review and commit skills, surfacing a final Decision Gate before any destructive action. Thin orchestrator — defers detail to leaf skills.\"\nwhen_to_use: \"ship this change; prepare to land; get this PR-ready; ship workflow\"\nuser-invocable: true\nallowed-tools:\n  - \"Bash(git *)\"\n  - \"Bash(gh pr *)\"\n  - Read\n  - Glob\n  - Grep\nmetadata:\n  trove-category: pull-requests\n  trove-category-label: \"Pull requests\"\n---\n\u003C!-- AUTO-GENERATED from SKILL.md.tmpl — do not edit directly -->\n\u003C!-- Regenerate: bun run build:skills -->\n\n## Session Init\n\nThis skill ships Trove conventions. Prefer existing project patterns over generic best practices when they conflict.\n\nIf a sibling skill in this plugin matches the request more directly, defer to it. See `AGENTS.md` (or `docs\u002Frouting.md` in the marketplace) for the per-plugin routing index.\n\nYou are an orchestrator: when a step maps to another skill (e.g., review, security-review, design-review), call out the delegation explicitly rather than re-implementing it inline.\n\n# trove-ship — Pre-Land Preparation\n\n`trove-ship` is an **orchestrator**, not a leaf skill. It walks a diff\nthrough review → commit → ship-readiness check and stops at a final\nDecision Gate before anything destructive (push, PR, tag).\n\n> The repo's `release.yml` workflow handles the actual version bump and\n> tag. `trove-ship` prepares the diff up to \"ready to push\"; the user (or\n> CI on merge) handles publish.\n\n## Inputs\n\n- A working tree with uncommitted or branch-local changes.\n- Optional: target base branch, scope of the change (feature \u002F fix \u002F chore).\n\n## Workflow\n\n### Stage 1 — Review the diff\n\nHand off to **`trove-review`**. Walk the diff through the standard checklist\n(correctness, security, performance, maintainability, testing). If the\ndiff touches sensitive surfaces (auth, payments, secrets), also delegate\nto **`trove-security-review`** for a second pass — this is in `trove-review`'s\n`benefits-from` for exactly this reason.\n\n> Optional: dispatch a read-only sub-agent to verify a specific concern\n> the review surfaced (e.g., \"is this the only callsite of the legacy\n> function?\"). See [docs\u002Forchestration.md](..\u002F..\u002Fdocs\u002Forchestration.md)\n> for delegation phrasing.\n\n### Stage 2 — Author the commit\n\nHand off to **`trove-commit`**. Generate the conventional-commit message\nfrom the diff. Don't substitute your own format — `trove-commit` owns the\nconventions (type, scope, body, footer).\n\n### Stage 3 — Ship-readiness gate\n\nBefore pushing, surface the Decision Gate below. The gate exists because\n\"ready to push\" is a one-way door from the user's perspective: once the\nPR is open, reviewers will look.\n\n## Decision Gate: ready to push\n\nContext: The next step is `git push` and PR creation. Reviewers will see this branch.\nQuestion: Are review and commit message both clean?\nOptions:\n- A. Yes — push and open the PR.\n- B. No — loop back. Name the issue (failing test, unclear commit, scope creep) and fix it.\nDefault: B, because a moment's pause on a one-way door is cheaper than withdrawing a PR.\n\n## Output\n\nAfter the gate clears:\n\n```markdown\n# Ready to ship\n\n## Review summary\n\u003Cfrom trove-review — issues found, severity, status>\n\n## Commit message\n\u003Cfrom trove-commit — final wording, ready to use as `git commit -m`>\n\n## Push command\n\u003Cgit push -u origin \u003Cbranch>>\n```\n\nIf the user chooses option A at the gate, push the current branch with upstream\ntracking and open a PR with `gh pr create`. Detect the likely base branch from\n`staging`, `production`, `main`, `master`, or `develop` using merge-base\ndistance. The PR body should include a terse summary, key changes, tests run,\nand breaking changes or migrations. Analyze all branch commits, not just the\nlatest commit.\n\n## PR shape\n\nPrefer small, stacked PRs over one fat PR. Each commit is a future PR: a reviewer should be able to read one focused change at a time. When a branch has grown to cover several concerns, split it. Run the PR description through `trove-unslop` (its `benefits-from`) and drop Summary\u002FTest-plan boilerplate that adds nothing.\n\n## Anti-patterns\n\n- **Don't skip the review** even on a \"trivial\" change. `trove-ship` exists\n  precisely because trivial changes are where most regressions hide.\n- **Don't write the commit before the review.** A review can change scope;\n  the commit message should reflect the final state.\n- **Don't auto-push.** The Decision Gate is the whole point — a human\n  confirms before the one-way door.\n- **Don't bump VERSION here.** This repo's `release.yml` owns version on\n  merge to main; `trove-ship` is pre-merge.\n","\u003C!-- AUTO-GENERATED from SKILL.md.tmpl — do not edit directly -->\n\u003C!-- Regenerate: bun run build:skills -->\n\n## Session Init\n\nThis skill ships Trove conventions. Prefer existing project patterns over generic best practices when they conflict.\n\nIf a sibling skill in this plugin matches the request more directly, defer to it. See `AGENTS.md` (or `docs\u002Frouting.md` in the marketplace) for the per-plugin routing index.\n\nYou are an orchestrator: when a step maps to another skill (e.g., review, security-review, design-review), call out the delegation explicitly rather than re-implementing it inline.\n\n# trove-ship — Pre-Land Preparation\n\n`trove-ship` is an **orchestrator**, not a leaf skill. It walks a diff\nthrough review → commit → ship-readiness check and stops at a final\nDecision Gate before anything destructive (push, PR, tag).\n\n> The repo's `release.yml` workflow handles the actual version bump and\n> tag. `trove-ship` prepares the diff up to \"ready to push\"; the user (or\n> CI on merge) handles publish.\n\n## Inputs\n\n- A working tree with uncommitted or branch-local changes.\n- Optional: target base branch, scope of the change (feature \u002F fix \u002F chore).\n\n## Workflow\n\n### Stage 1 — Review the diff\n\nHand off to **`trove-review`**. Walk the diff through the standard checklist\n(correctness, security, performance, maintainability, testing). If the\ndiff touches sensitive surfaces (auth, payments, secrets), also delegate\nto **`trove-security-review`** for a second pass — this is in `trove-review`'s\n`benefits-from` for exactly this reason.\n\n> Optional: dispatch a read-only sub-agent to verify a specific concern\n> the review surfaced (e.g., \"is this the only callsite of the legacy\n> function?\"). See [docs\u002Forchestration.md](..\u002F..\u002Fdocs\u002Forchestration.md)\n> for delegation phrasing.\n\n### Stage 2 — Author the commit\n\nHand off to **`trove-commit`**. Generate the conventional-commit message\nfrom the diff. Don't substitute your own format — `trove-commit` owns the\nconventions (type, scope, body, footer).\n\n### Stage 3 — Ship-readiness gate\n\nBefore pushing, surface the Decision Gate below. The gate exists because\n\"ready to push\" is a one-way door from the user's perspective: once the\nPR is open, reviewers will look.\n\n## Decision Gate: ready to push\n\nContext: The next step is `git push` and PR creation. Reviewers will see this branch.\nQuestion: Are review and commit message both clean?\nOptions:\n- A. Yes — push and open the PR.\n- B. No — loop back. Name the issue (failing test, unclear commit, scope creep) and fix it.\nDefault: B, because a moment's pause on a one-way door is cheaper than withdrawing a PR.\n\n## Output\n\nAfter the gate clears:\n\n```markdown\n# Ready to ship\n\n## Review summary\n\u003Cfrom trove-review — issues found, severity, status>\n\n## Commit message\n\u003Cfrom trove-commit — final wording, ready to use as `git commit -m`>\n\n## Push command\n\u003Cgit push -u origin \u003Cbranch>>\n```\n\nIf the user chooses option A at the gate, push the current branch with upstream\ntracking and open a PR with `gh pr create`. Detect the likely base branch from\n`staging`, `production`, `main`, `master`, or `develop` using merge-base\ndistance. The PR body should include a terse summary, key changes, tests run,\nand breaking changes or migrations. Analyze all branch commits, not just the\nlatest commit.\n\n## PR shape\n\nPrefer small, stacked PRs over one fat PR. Each commit is a future PR: a reviewer should be able to read one focused change at a time. When a branch has grown to cover several concerns, split it. Run the PR description through `trove-unslop` (its `benefits-from`) and drop Summary\u002FTest-plan boilerplate that adds nothing.\n\n## Anti-patterns\n\n- **Don't skip the review** even on a \"trivial\" change. `trove-ship` exists\n  precisely because trivial changes are where most regressions hide.\n- **Don't write the commit before the review.** A review can change scope;\n  the commit message should reflect the final state.\n- **Don't auto-push.** The Decision Gate is the whole point — a human\n  confirms before the one-way door.\n- **Don't bump VERSION here.** This repo's `release.yml` owns version on\n  merge to main; `trove-ship` is pre-merge.\n",{"name":5,"metadata":24,"description":7,"when_to_use":27,"allowed-tools":28,"user-invocable":34},{"trove-category":25,"trove-category-label":26},"pull-requests","Pull requests","ship this change; prepare to land; get this PR-ready; ship workflow",[29,30,31,32,33],"Bash(git *)","Bash(gh pr *)","Read","Glob","Grep",true,"main","f88db1f1cf0e0703dd962051ebc142db961d7799","skills\u002Fworkflow\u002Ftrove-ship",1,"https:\u002F\u002Fgithub.com\u002Fbravew\u002Ftrove","https:\u002F\u002Fgithub.com\u002Fbravew","2026-11-12 07:56:32",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":34},[44,47,50],{"tool":45,"command":46},"npx","npx skills add bravew\u002Ftrove --skill trove-ship",{"tool":48,"command":49},"bunx","bunx skills add bravew\u002Ftrove --skill trove-ship",{"tool":51,"command":52},"pnpm","pnpm dlx skills add bravew\u002Ftrove --skill trove-ship","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbravew\u002Ftrove\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Ftrove-ship\u002FSKILL.md",[55],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"SKILL.md.tmpl","OTHER","其他",4147,"https:\u002F\u002Fgithub.com\u002Fbravew\u002Ftrove\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Ftrove-ship\u002FSKILL.md.tmpl",[62,69,76,83,90,97],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7AGJDHTQAS1VK6P7VJAV79G","using-trove","Skill discipline anchor for the Trove marketplace. Loaded once per session; routes the agent to the right trove-* skill before code, planning, review, or git actions.","https:\u002F\u002Fgithub.com\u002Fbravew\u002Ftrove\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Fusing-trove\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7AGJAS4V4TXE6TV6F839BGZ","trove-write-skill","Skill authoring workflow. Use when creating or updating a Codex or Trove skill, including rubrics, tasks, metadata, and validation.","https:\u002F\u002Fgithub.com\u002Fbravew\u002Ftrove\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Ftrove-write-skill\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":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7AGJ87K41ZAC8DDBAV17QFW","trove-worktree","Git worktree workflow for spikes, risky experiments, and broad refactors that should not disturb the user's current branch.","https:\u002F\u002Fgithub.com\u002Fbravew\u002Ftrove\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Ftrove-worktree\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7AGJ32V58VYBFYMS9EMHRY4","trove-why","Reconstruct design rationale and decision history from evidence — source control, issue tracker (Linear), docs (Notion), chat (Slack), error tracking (Sentry) — with calibrated confidence. Use for \"why does X work this way\", \"why did we pick Y\", regressions, and postmortems. Use trove-explain for how it works now.","https:\u002F\u002Fgithub.com\u002Fbravew\u002Ftrove\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Ftrove-why\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7AGJ0FHJSRR8MMXC3V8XNHF","trove-verify","Completion verification workflow. Use before claiming done, fixed, complete, ready, or shipped.","https:\u002F\u002Fgithub.com\u002Fbravew\u002Ftrove\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Ftrove-verify\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M7AGHWV4B9SDS60RH5W0B0K5","trove-unslop","Cut AI tells from writing — PR descriptions, release notes, specs, commit bodies, and replies. Use before finalizing prose, or when the user asks to clean up, de-slop, or make text sound human.","https:\u002F\u002Fgithub.com\u002Fbravew\u002Ftrove\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Ftrove-unslop\u002FSKILL.md",[],[]]