- name
SKILL.md
Файл навыка остаётся в репозитории издателя.
Вставьте скопированную команду в терминал. Она установит этот SKILL.md в выбранного агента.
npx skills add phuryn/product-engineering --skill release-gate -a cursor -yВставьте скопированную команду в терминал. Она установит этот SKILL.md в выбранного агента.
npx skills add phuryn/product-engineering --skill release-gate -a claude-code -yВставьте скопированную команду в терминал. Она установит этот SKILL.md в выбранного агента.
npx skills add phuryn/product-engineering --skill release-gate -a codex -yВставьте скопированную команду в терминал. Она установит этот SKILL.md в выбранного агента.
npx skills add phuryn/product-engineering --skill release-gate -a grok -yОтправьте скопированное сообщение в чат Grok Bot. Бот загрузит этот SKILL.md с GitHub и добавит его к навыкам, общим для всех ваших ботов.
Install this skill: https://github.com/phuryn/product-engineering/tree/HEAD/ai-shipping/skills/release-gateОт издателя
A release is a decision: the owner says go; the agent supplies the evidence. This skill defines the evidence needed at each shipping step, the promotion procedure and how to prove the reviewed build serves.
The product's own instructions come first. Use its named branches, gate, backlog and record files, taking these rules as defaults where its instructions or release doc say nothing.
On another stack, keep the principle and swap the mechanism. Each rule states its principle first and the stack's mechanism second. The web-app rules were learned on Next.js (App Router), Supabase, Clerk and Netlify, with Vitest and Playwright. The client-and-backend rules were learned on a relay service with a web client and an editor extension with desktop installers (references/runbook.md).
Name the product and production branches in the release doc. Write their real names there at the first push, and nowhere else.
<product>.<product>-prod as its default name. Require the local gate, independent review and owner's go first.Treat product-branch pushes as deploys until the production branch exists. Before then, the host deploys the product branch itself; apply the environments skill for branch-to-environment mapping.
A host that deploys by CLI upload deploys the working tree, not a commit. Treat the upload as the push: close the review round first and upload a clean worktree of the reviewed commit. Name the target: railway up --ci -p <project> -e <environment> -s <service>. Bare railway up in an unlinked folder offers to create a project.
Stamp every upload with its commit. Use railway up --message <commit> so the deployment records its commit as meta.cliMessage. Railway uploads otherwise have a snapshot id without a commit, preventing comparison of web and worker trees (observed 2026-11-03). State-reading scripts must account for these behaviours (Railway, observed 2026-11-03):
activeDeployments with status SUCCESS and deploymentStopped: true.environmentStagedChanges creates an empty staged record, { patch: {} }.Keep the release's evidence in the product's existing records. Use the following meanings even when your product gives the records different names:
The suggested script names are gate, smoke -- <url>, visual and agents:live, shared with test-harness. Use your product's names.
Phase ends and deploying pushes require the full applicable gate. Apply test-harness to compare the script with its suite contract. The owner decides any narrower set; record the choice in the plan with its reason and revisit trigger.
test-harness for the map's format.delegation and codex-agents for these boundaries.test-harness).Review before every deploying push and again before production promotion. Apply this however small the change and however green the gate. Before every round, read and apply independent-review for the wrapper, brief, scope, triage, short reports, severity, fix costs, and commit/push effects.
The session must never have seen the build; choose it in this order:
independent-review requires. If it cannot, use its recorded fallback when that can, otherwise the wrapper's reviewer without asking. If no other family can run, use a fresh session of the builder's family. The report names the actual reviewer and why.Keep the review read-only, fresh and unsteered. Start without carried-over memory, using a fresh session rather than resuming or forking the building thread. Supply the unreleased diff plus working tree, without a checklist, earlier findings or an argument for the design.
Compute review subjects from git and repeat until the bar holds. Cover the whole unreleased range in round one, then only changes since the last round, with everything else as context. Fix what the bar names, rerun the tests each fix touches yourself, then review again. Apply independent-review for full gate timing and recording accepted Lows. Stop only when the round has no INTRODUCED finding above Low and no High or Critical of any age remains open. Put pre-existing findings in the backlog with a reason and revisit trigger. Fix High and Critical now, regardless of age.
Propose static audits at each release and wait for the request. Propose security-audit-static and performance-audit-static on the release's changes. Propose a whole-repository pass only for the first release, after a large refactor, or when the owner asks. Run these steered passes beside the independent review rather than using them to replace it. Keep reports under gitignored reports/ so security reports stay out of repository history. Fix findings or backlog them, and record declined passes as declined. Exact ranges are in references/checklist.md.
Use documentation checks without overwriting records maintained during the change. This restriction applies when docs are written with the change and coverage evidence belongs to whoever ran the gate. In that product, use ai-shipping documentation skills only for:
shipping-artifacts.check modes of document-app and derive-tests: they write nothing and list every disagreement among docs, coverage and code.For records maintained with changes, decline audit recommendations to rewrite them. Without check, document-app and derive-tests rewrite docs and coverage from code. ship-check also rewrites agent instructions and runs its own review. Decline an audit's recommendation to run them. If the owner explicitly names one, explain what it would overwrite and offer this release path before running it.
Read migration integration settings and record them with the read date. The release doc must say which case applies:
500 on every affected page.2026-10-25). The build and the migration run then start together with nothing ordering them, and the provider takes every file in the migrations directory.Unread means on. Read the provider dashboard's integration settings and the production branch's provider commit checks. On Supabase, check the project's GitHub integration, its production branch and Deploy to production.
Apply pending migrations by CLI before pushing after the owner's go. Before the go, read production's ledger and dry-run pending migrations. After the go, apply them before the push and reread the ledger, leaving nothing pending to race the build. Keep files you do not intend to run out of the migrations directory.
Reach production through its connection string only. Keep the CLI unlinked for both environments. Reach production through --db-url on the Supabase CLI; use development's own connection string for development. Avoid db push --linked --project-ref <production ref>: precedence is not reliable across versions. A dummy-ref probe used the typed ref for its first request (Supabase CLI 2.122.0, read 2026-10-25). A connection string names one database across versions. Apply supabase-production for the ledger and environments for the window where deployed code meets the new schema.
Send the owner a preview after phase checks and any closing deploy. Ready means the phase checks passed and its review series is clean. Give a link and a short list of what to try, including the look review. Follow independent-review § When for the ordered phase checks and ui-design for the visual method. The coordinator explores the journeys and screens the phase added or changed; the builder never performs that final look. Ten minutes using the product finds what reading code does not.
Show work early only when the owner asks for that preview. Use a development tunnel or the named push; every deploying push still needs review first. Say which phase review has not run and disclose incomplete tests as below; this request is the exception to waiting for a clean series.
e2e:auth did not run: development test mode is not configured." Name the reason and what brings each run back, even when the coverage map already records the gap.next dev. Its address is public: use development only, share the link only with the owner, then stop tunnel and server when done. Apply environments, references/environments-and-branches.md § Showing development to the owner.delegation for the handoff side of this rule.Commands and the record are in references/checklist.md § 4.
grep -o … | wc -l. Avoid grep -c: it counts lines, and a production document is one line. If no served byte changes, record "unprobeable by content" and read the framework's build id, replaced on every build. A generic 200 cannot establish build identity.Run each release as one ordered, logged checklist. This includes packages, extensions, installers, store listings, and clients with backends. Log each step's command, pass and evidence in the release plan (references/runbook.md). Record every skip with its reason; correct a faulty list in the same pass.
agent-instructions. Run the script only after the owner's clear go, authorizing that one release (references/runbook.md). The doc names the steps the owner keeps.--dry-run deploys for real.2026-11-07). Pushing there is a release regardless of tags. Keep next-release work on another branch. Move the served branch to the reviewed commit only at the go, with the tag naming its head.Force-push the production branch · promote with an unapproved suite omission, a stale doc, or an unrun local gate · run any authenticated smoke with a real user's credentials · test against production data · apply a migration through an MCP server or the dashboard · link the database CLI to any project · deploy a runtime from a checkout that is not the release tip · hand-roll a step a release script encodes · infer a go from an ambiguous reply · announce a store listing as live before it serves the version.
references/checklist.md § 1.§ 2), and get the owner's answer in chat.§ 3).§ 4).Each rule's origin, the case that taught it, is in receipts.md beside this file; read it when a rule's edge is unclear.
The reviewed commit serves on the live site, beyond the deploy log, and the post-promotion checks passed. The owner gave the go after the preview.
Related skills:
independent-review (the review loop)test-harness (the gate, the harnesses, the coverage map, the script contract)environments (branches, variables, the migrations window, the tunnel, incidents)supabase-production (the migration ledger)clerk-production (the production instance)agent-instructions (the pass over the agent instructions at each release)app-lifecycle (where publish and go-live sit on the path)ui-design (what a screen may claim; what the exploratory pass looks at)shipping-artifacts (the core docs)Before 'push it', 'ship it', a deploy, release or go-live, or calling a stage done: the gate, the owner's preview, go/no-go, promote, prove it serves, roll back.
---name: release-gatedescription: Before 'push it', 'ship it', a deploy, release or go-live, or calling a stage done: the gate, the owner's…---# ai-shipping/skills/release-gate/SKILL.mdFAQ
Скачайте ai-shipping/skills/release-gate/SKILL.md у издателя или скопируйте путь и откройте репозиторий. PlugMCP только показывает навык в каталоге и не хранит файл.
Издатель хранит его в https://github.com/phuryn/product-engineering.
Claude, Cursor, Codex и Grok Build могут читать SKILL.md, который вы добавляете из репозитория издателя. Grok Bot устанавливает его, когда вы отправляете в чат ссылку на папку навыка на GitHub.
references/runbook.md § E).