storyblok-component-push
Skill0 starsChanged 6 months agoMITView on GitHub
Push a NEW bugfix_* component schema to Storyblok via the CLI and regenerate TypeScript types. Use only when a bug fix requires a new isolated component schema — never to modify existing components. Triggered by "push bugfix component", "regen storyblok types", or when the orchestrator needs a new component schema in place before creating a story.
In this repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ado-bug-lifecycleSkill
- ado-bug-querySkill
- ado-pr-createSkill
- bug-captureSkill
- bug-reviewer-runSkill
- bug-triage-sessionSkill
- storyblok-bugfix-storySkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 45
NEVER delete or modify existing components or content types: Only push new bugfix_* components.
- Very specific: line 47
Always regenerate types: after a successful push — pnpm storyblok:types.
- Very specific: line 48
Single-component push only: Do not run storyblok components push with no name argument or with a glob — that pushes everything.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Storyblok — Component Schema Push
Component schemas are the only thing the Storyblok CLI is reliable for. Stories themselves are managed via curl (see storyblok-bugfix-story).
Workflow
cd $TARGET_REPO_PATH/packages/cms # adjust the subpath to wherever your CMS schema lives
# 1. Pull latest (safe, read-only) — always do this first
pnpm storyblok:pull-components
# 2. Push only the NEW bugfix_<name>_<id> component
storyblok components push bugfix_<name>_<id> \
--space $STORYBLOK_SPACE_ID \
--path /tmp/storyblok-push/ \
--separate-files
# 3. Regenerate TypeScript types after any push
pnpm storyblok:types
cd ../..Naming
bugfix_<component_name>_<bug_id> — underscores throughout. Example: bugfix_tabs_99001.
This is the component name. The corresponding story slug uses hyphens (see storyblok-bugfix-story).
Hard rules
- NEVER delete or modify existing components or content types. Only push new
bugfix_*components. - Always pull before push. Confirms you're working from the current schema and avoids overwriting newer changes.
- Always regenerate types after a successful push —
pnpm storyblok:types. The target repo depends on the generated types. - Single-component push only. Do not run
storyblok components pushwith no name argument or with a glob — that pushes everything.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

