Skip to content

Migration skills state explicit template and upgrade conditions #581

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Marius Storhaug (MariusStorhaug) wants to merge 2 commits into
base: main
Choose a base branch
from
+11 −8
Open

Migration skills state explicit template and upgrade conditions #581

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c43c36e
State v8 migration framing as explicit conditions
MariusStorhaug Nov 4, 2026
21cc8b3
State Zensical starter layout as a template revision condition
MariusStorhaug Nov 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 9 additions & 6 deletions .github/plugin/psmodule/skills/psmodule-v8-upgrade/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,8 @@ the template's default files before adding, removing, or relocating anything.
The template is a starting point, not a reason to overwrite module-specific
content.

The current template's default repository anatomy is:
If the selected immutable template revision has this layout, its default
repository anatomy is:

```text
<ModuleName>/
Expand Down Expand Up @@ -125,11 +126,13 @@ Treat files and directories as follows:
Preserve the consumer's local onboarding contract while updating stale links.

If the template revision and the consumer's existing layout disagree, record
the difference and migrate only the requested integration surface. In
particular, the current template uses `.github/zensical.toml`, while this v8
upgrade request uses `docs/zensical.toml`, `docs/content/`, and
`docs/overrides/` (including `docs/overrides/assets/`) as its documentation
contract; a separate `docs/assets/` directory is optional. When that requested
the difference and migrate only the requested integration surface.

If the selected immutable template revision uses `.github/zensical.toml`,
that file contains the template's Zensical settings. If the requested v8
upgrade uses `docs/zensical.toml`, `docs/content/`, and `docs/overrides/`
(including `docs/overrides/assets/`) as its documentation contract, a separate
`docs/assets/` directory is optional. When that requested
documentation migration is in scope, move the template's Zensical settings
and custom assets into the `docs/` contract rather than maintaining both
configurations. When it is not in scope, preserve the consumer's existing
Expand Down
4 changes: 2 additions & 2 deletions .github/plugin/psmodule/skills/psmodule-zensical-migration/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,8 +76,8 @@ Keep existing content under `docs/content/`, custom templates under
`docs/assets/` directory is optional for static content assets. Do not create a
parallel MkDocs theme or leave two active site configurations.

The current `PSModule/Template-PSModule` repository historically stores a
starter `.github/zensical.toml` and may not contain a `docs/` tree. When the
If the selected immutable `PSModule/Template-PSModule` revision contains a
starter `.github/zensical.toml`, it may not contain a `docs/` tree. When the
consumer upgrade explicitly requires the Process-PSModule `docs/` contract,
move the template settings and custom assets into `docs/` and remove the
obsolete active configuration only after the site builds. When that contract
Expand Down
Loading