You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit bb81125
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: .agents/skills/ship/SKILL.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -66,6 +66,10 @@ When the user runs `/ship`:
66
66
# Runs every audit CI runs, concurrently, and replays the output of any that fail.
67
67
# The audit list is derived in scripts/run-audits.ts — do not hand-list audits here.
68
68
bun run check:audits || { echo"❌ audit(s) failed — do not ship";exit 1; }
69
+
# CI's "Verify docs manifest is in sync" step is not a `check:*` script, so the runner above
70
+
# does not cover it. (CI's "Security audit" `bun audit` step is `continue-on-error` — advisory
71
+
# only, not a gate — so it is deliberately not run here.)
72
+
bun run docs-manifest:check || { echo"❌ docs manifest out of sync — do not ship";exit 1; }
69
73
```
70
74
If Phase A regenerated a file, its matching `:check` in Phase B now passes trivially — that parity is the point. Do not ship with any generator or audit failing; fix the cause (never silence it) and re-run. `check:migrations` and `type-check` are covered by steps 5 and CI respectively and are not repeated here.
71
75
7.**Stage and commit** the changes with the generated message — including any files Phase A regenerated in step 6
Copy file name to clipboardExpand all lines: apps/docs/content/docs/platform/enterprise/forks.mdx
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -331,6 +331,8 @@ Servers that **publish workflows as MCP tools**.
331
331
|**Fork**|**Values never leave the source.** Workflow text still contains `{{KEY}}` names. Create matching secrets (or the names you will map to) under the child’s **Secrets**. |
332
332
|**Sync**| Map source key names to target key names. Values stay in each workspace. Unmapped required secrets block Sync. |
333
333
334
+
Notes are documentation: a `{{KEY}}` inside a Note block never needs mapping and never blocks Sync.
335
+
334
336
**Example:** Workflows use `{{OPENAI_API_KEY}}`. After fork, add that secret in the child (or map `OPENAI_API_KEY` to whatever name the child uses) before runs and syncs succeed.
0 commit comments