docs: reorganize Hydrogen documentation into focused skills#3555
docs: reorganize Hydrogen documentation into focused skills#3555
Conversation
|
Oxygen deployed a preview of your
Learn more about Hydrogen's GitHub integration. |
|
🤖 Code Review · #projects-dev-ai for questions ✅ Complete - No issues 📋 History✅ No issues |
| - This package calls the `hydrogen init` command from `@shopify/cli-hydrogen` | ||
| 1. **Default behavior**: Uses the skeleton template bundled inside `@shopify/create-hydrogen` | ||
| - No network fetch required—the template is pre-bundled at build time | ||
| - This is why `create-hydrogen` must be bumped when skeleton changes |
There was a problem hiding this comment.
i wonder if we can just use pnpm workspaces for this and omit this section entirely
(by adding skeleton as a dep inside create-hydrogen)
|
|
||
| # Hydrogen Development Workflow | ||
|
|
||
| Development practices and workflow guide for engineers working on Shopify's headless storefront ecosystem. The Hydrogen framework repo is [`Shopify/hydrogen`](https://github.com/Shopify/hydrogen). For domain context, see the `headless-storefronts-context` skill. For repo locations, see the `shopify-repos` skill. |
There was a problem hiding this comment.
are those other skills real? could not find headless-storefronts-context nor shopify-repos
There was a problem hiding this comment.
yep it’s here
so this assumes you have the Vault MCP working with the claude plugin? idk if it’s ok for us to mention them across domains like that
There was a problem hiding this comment.
I think mentioning the other skills is fine, but the internal context needs to stay internal. What do you think of just modifying it to say something like "If you are a Shopify employee, run to get access to the headless-storefronts-context skill (for domain context)"?
There was a problem hiding this comment.
yeah i think that’s fine
ps.: i’d place this skill inside skeleton and publish it for other agents/tools too!
fredericoo
left a comment
fredericoo
left a comment
There was a problem hiding this comment.
lgtm! left a couple of suggestions but we can move files later, and having those on main will be an insta benefit
2 participants
Summary
Part of https://github.com/Shopify/developer-tools-team/issues/1052.
hydrogen-release-processskill — dedicated on-demand runbook for the full release flow (standard, back-fix, snapshot), manual vs automatic steps, changelog.json updates, h2 upgrade enablement, failure recovery, and Dependabot review guidanceCLAUDE.mdfrom ~340 to ~195 lines — keeps only changeset rules (now 3 rules, adding hydrogen-react and CI blind-spot rules), skeleton/CLI quick reference, and circular dependency explanationhydrogen-dev-workflowskill — removes release process and changeset sections that now live elsewhere; fixes dangling cross-referenceshydrogen-versioningskill — cross-references now point to the new release skillStale reference fixes
changesets.yml→release.yml(unified workflow)next-release.yml→next-releasejob inrelease.ymlchangesets-back-fix.yml→backfix-releasejob inrelease.ymllatestBranch→latestVersionin PR title documentation~3.80.4CLI version removed from diagramlatestBranchdescribed as dynamically computed (not hardcoded)Why
CLAUDE.md loads into every Claude Code session. ~145 lines of release process detail were loading even for tasks like fixing a typo or reviewing a bug fix. Moving this content to an on-demand skill means it only loads when triggered by keywords like "release", "back-fix", or "changelog.json".
Out of scope
docs/CALVER.mdhas 6 stale references tochangesets.ymlthat should berelease.yml— noted for a separate cleanup.