Contract
- Input: merge-to-main event, deployment metadata, production environment config.
- Output:
GatePostMergeArtifact with canary, health, and feature flag results.
- Scope: post-deployment checks only — canary smoke, health check, feature flag verification.
- Rule: do not block the workflow on failure — alert instead.
- Rule: canary must reach minimum traffic threshold before health check runs.
- Rule: feature flag verification checks that new flags are present and correctly targeted.
Provenance
| Question |
Answer |
| What is the source of truth? |
The merge-to-main event and deployment metadata |
| What is in scope? |
Canary smoke test, production health check, feature flag verification |
| What is explicitly out of scope? |
Full regression suite, load tests, manual QA |
| Who or what consumes this artifact afterward? |
observability or incident-response if failures detected |
| What evidence proves it is done? |
All checks completed, alerts sent if failures, structured result returned |
| What risk remains? |
Canary may not catch all issues; health checks are surface-level; feature flags may have incomplete rollout |
Artifact
Return GatePostMergeArtifact as structured output in the current response. Do not write local artifact files unless the user explicitly asks for an export.
Process
1. Trigger canary smoke test
Deploy to canary environment (5-10% traffic). Run smoke tests against canary endpoints. Wait for success or timeout.
2. Run production health check
Query production health endpoints. Check: response time, error rate, database connectivity, cache hit rate. Compare against SLO thresholds.
3. Verify feature flags
Check that all feature flags introduced in this merge are present in the flag service, have correct targeting rules, and default to off for safety.
4. Alert on failure
If any check fails:
- Send alert to incident channel (Slack, PagerDuty, etc.)
- Tag the merge commit with failure metadata
- Do NOT block the workflow — merge already happened
5. Aggregate results
Compile all check results into GatePostMergeArtifact. Terminal state:
- All
passed → completed
- Any
failed → failed (but workflow not blocked)
Completion
- canary smoke test completed
- production health check completed
- feature flag verification completed
- alerts sent if any check failed
- structured result returned
1---2name: gate-post-merge3category: platform4maturity: stable5version: 16description: Post-deployment quality gate triggered on merge-to-main events. Runs canary smoke test, production health check, and feature flag verification. Alerts on failure without blocking the workflow.7license: MIT8capabilities:9 - run canary and health checks10 - produce quality gate artifact11 - validate quality gate completion criteria12 - trace gate post merge decisions across inputs, constraints, and failure paths13 - validate platform outcomes with evidence, assumptions, and explicit next steps14outputs:15 - type: object16 name: GatePostMergeArtifact17 properties:18 trigger: { type: string, enum: [merge-to-main] }19 checks:20 type: array21 items:22 type: object23 properties:24 name: { type: string }25 status: { type: string, enum: [passed, failed, skipped] }26 durationMs: { type: integer }27 output: { type: string }28 blockOnFailure: { type: boolean }29 alertOnFailure: { type: boolean }30 result: { type: string, enum: [completed, blocked, failed] }31 required: [trigger, checks, blockOnFailure, alertOnFailure, result]32sideEffects: []33dependencies: []34stopCondition: Post-deployment quality gate triggered on merge-to-main events complete; structured result returned; completion criteria checked.35risk: medium36trustTier: 137maxIterations: 338modelTier: fast39promptVersion: "2.0"40artifactType: plan41evaluators:42 - behavioral43 - regression44fixturesPath: .agents/skills/platform/fixtures/behavioral/gate-post-merge.json45diataxis: how-to46tags: [quality, production, canary, gate]47compatibility: [deployment, observability, ship-subissue]48approvalRequired: false49approvalFor: []50metadata:51 source: https://skillmd.com/skills/quantumquirkxyz/gate-post-merge52---5354## Contract5556- Input: merge-to-main event, deployment metadata, production environment config.57- Output: `GatePostMergeArtifact` with canary, health, and feature flag results.58- Scope: post-deployment checks only — canary smoke, health check, feature flag verification.59- Rule: do not block the workflow on failure — alert instead.60- Rule: canary must reach minimum traffic threshold before health check runs.61- Rule: feature flag verification checks that new flags are present and correctly targeted.6263## Provenance6465| Question | Answer |66|---|---|67| What is the source of truth? | The merge-to-main event and deployment metadata |68| What is in scope? | Canary smoke test, production health check, feature flag verification |69| What is explicitly out of scope? | Full regression suite, load tests, manual QA |70| Who or what consumes this artifact afterward? | `observability` or incident-response if failures detected |71| What evidence proves it is done? | All checks completed, alerts sent if failures, structured result returned |72| What risk remains? | Canary may not catch all issues; health checks are surface-level; feature flags may have incomplete rollout |7374## Artifact7576Return `GatePostMergeArtifact` as structured output in the current response. Do not write local artifact files unless the user explicitly asks for an export.7778## Process7980### 1. Trigger canary smoke test81Deploy to canary environment (5-10% traffic). Run smoke tests against canary endpoints. Wait for success or timeout.8283### 2. Run production health check84Query production health endpoints. Check: response time, error rate, database connectivity, cache hit rate. Compare against SLO thresholds.8586### 3. Verify feature flags87Check that all feature flags introduced in this merge are present in the flag service, have correct targeting rules, and default to off for safety.8889### 4. Alert on failure90If any check fails:91- Send alert to incident channel (Slack, PagerDuty, etc.)92- Tag the merge commit with failure metadata93- Do NOT block the workflow — merge already happened9495### 5. Aggregate results96Compile all check results into `GatePostMergeArtifact`. Terminal state:97- All `passed` → `completed`98- Any `failed` → `failed` (but workflow not blocked)99100## Completion101102- canary smoke test completed103- production health check completed104- feature flag verification completed105- alerts sent if any check failed106- structured result returned