菜单
Bondery release operator runbook — prerequisites on main, extension gates, promote main:release and product tags, Dokploy image pins, rollback, and hotfix sequencing. Use when cutting a monthly or patch release, pushing to release, tagging api-X.Y.Z / webapp-X.Y.Z / ext-X.Y.Z, pinning image tags, promoting to production, or rolling back.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Bondery product changelog format, change categories, commit prefixes, calendar versioning, and release-note workflow. Use when editing docs/changelog/unreleased.mdx, documenting a user-visible or operationally notable change, preparing a release, choosing a conventional commit prefix, recording dependency updates, or drafting release communications.
Risk-proportional verification for Bondery monorepo changes. Maps changed files to npm workspaces and shared-package consumers, runs the fastest relevant lint, type, policy, test, contract, build, and runtime checks, then reviews staged and unstaged diffs without requiring commits. Use after implementing or refactoring, before handoff or a PR, when asked to verify/test/check changes, or when deciding which Bondery quality gates apply.
Bondery legal disclosure hygiene — subprocessor registry, policy-claims reconciliation, data-flow triggers, and escalation boundaries. Use when adding third-party vendors/SDKs, new data collection, analytics, AI tools, retention/deletion, or editing Privacy/Terms.
Bondery security patterns — tenant isolation, auth areas, sessions, secrets, input validation, uploads, webhooks, client trust boundaries, and deployment hardening. Use when adding authentication, authorization, API routes, secrets, uploads, webhooks, payments, sensitive data, extension bridges, or reviewing security-sensitive changes.
Bondery Fastify API contracts — transport wrappers, list pagination (offset/search/sort), resource-keyed responses, mutations, Stripe-style errors, route registration order, mobile sync, rate limits, and versioning. Use when adding or changing API routes, client API calls, OpenAPI, sync protocol, or API error codes.
How to create, name, and structure Bondery agent skills per agentskills.io. Use when adding or updating skills in .agents/skills/, writing SKILL.md frontmatter, progressive disclosure, references/, scripts/, or pre-ship checklists for Bondery skills.
| name | bondery-release |
| description | Bondery release operator runbook — prerequisites on main, extension gates, promote main:release and product tags, Dokploy image pins, rollback, and hotfix sequencing. Use when cutting a monthly or patch release, pushing to release, tagging api-X.Y.Z / webapp-X.Y.Z / ext-X.Y.Z, pinning image tags, promoting to production, or rolling back. |
| metadata | {"version":"1.0.0","namespace":"bondery"} |
X.Y.Z)main to release or tagging api-*, webapp-*, ext-*BONDERY_INFRA_*_IMAGE_TAG after a tested deploybondery-changelog.github/workflows/README.mdbondery-verification-loopbabysit skillbondery-api → references/versioning.md:sha-<short> must exist on main before api-X.Y.Z / webapp-X.Y.Z — merge to main first; stage-images.yml builds artifacts on push to main.ghcr.io/usebondery/{api,webapp}:sha-<short> → :X.Y.Z unless force_rebuild: true on manual dispatch (human-approved only).main:release or product tags until the user confirms the Chrome Web Store listing is live.git push origin main:release is not extension-gated — marketing CD only (deploy-website.yml).packages/helpers/src/env/manifest.ts — do not use floating :production as the production/self-host pin for api/webapp..github/workflows/README.md overrides remembered release folklore.| Concern | Owner |
|---|---|
Version scheme, Unreleased → dated section | bondery-changelog |
| CI triggers, Docker channels, promote semantics | .github/workflows/README.md |
| Execute file edits and commits | Cursor implementer agent |
Watch release-* / deploy-website CI | Cursor babysit skill |
| Extension local dev / OAuth | apps/chrome-extension/README.md |
| Release blog post | .agents/workflows/blog/BLOG-POST.md |
| Task | Read |
|---|---|
Pre-release bumps, openapi, build on main | references/prerequisites.md |
| Order of extension → release → tags | references/sequencing-and-gates.md |
| What GitHub runs on push/tag (operator view) | references/ci-triggers.md |
| Manifest pins, Dokploy product stack | references/dokploy-pins.md |
ext-X.Y.Z, Chrome Web Store wait/reject | references/extension.md |
| Hotfix or production rollback | references/rollback-hotfix.md |
| Blog, Discord, Reddit after deploy | references/post-release.md |
Calculate X.Y.Z, cut changelog | bondery-changelog versioning |
Full index: references/README.md.
main complete (prerequisites.md)bondery-changelog)main; stage-images produced :sha-<short> for changed servicesext-X.Y.Z pushed; user confirmed CWS live before product deploymain:release pushed when website (or full stack) readyapi-X.Y.Z / webapp-X.Y.Z tagged only for changed services; CI promote + smoke greendeploy/bondery/.env.example; promoted to release if needed