git clone https://github.com/ArchitektApx/PowershellModuleTemplate
cd PowershellModuleTemplate

Edit module.psd1 at the repository root:

./tasks.ps1 prepare
./tasks.ps1 prepare -Platform PowerShell7   # override the platform for this run

This renames Source/ModuleTemplate.ps[dm]1, generates a fresh GUID, stamps the manifest, build.psd1 and LICENSE, generates Tools/PSScriptAnalyzer.psd1 and the CI matrix for your target platform, renders a README.md and CHANGELOG.md for your module, deletes the template-only scaffolding (res/, Tools/templates/, Tools/platforms/), and installs the dev requirements.

Add one .ps1 per function under Source/Public (exported) or Source/Private (internal), then:

./tasks.ps1 build
./tasks.ps1 test
./tasks.ps1 lint

The built module lands in Dist/<ModuleName>/<ModuleVersion>. 🎉

ModuleTargetPlatform selects one of the presets in Tools/platforms/:

The lint step enforces the preset. A ternary or ?? in Source/ passes under PowerShell7 and fails under PowerShell5.1And7.

See ModuleBuilder for how the source tree is assembled into the built module.

.
├── 📄 module.psd1          # Module metadata consumed by the tooling
├── 📄 build.psd1           # ModuleBuilder build config (manifest path, output, SemVer)
├── 🎯 tasks.ps1            # Task runner
├── 📁 Source/
│   ├── ModuleTemplate.psd1   # Becomes <YourModuleName>.psd1 after prepare
│   ├── ModuleTemplate.psm1   # Becomes <YourModuleName>.psm1 after prepare
│   ├── Enum/
│   ├── Classes/
│   ├── Private/
│   └── Public/
├── 🧪 Tests/
│   ├── _TestHelpers.ps1      # Target selection and import helpers; no module name hardcoded
│   ├── Harness.Tests.ps1     # Tests for the test harness itself
│   └── Module.Tests.ps1      # Artifact checks against the BUILT module, green on a fresh clone
├── 🔧 Tools/
│   ├── platforms/          # Target-platform presets (removed by prepare)
│   ├── templates/          # Skeletons rendered by prepare (removed by prepare)
│   └── ...                 # See Tools/README.md
├── 🔐 Docs/HARDENING.md    # GitHub settings to set before publishing (survives prepare)
├── 📚 Docs/CLASSES_AND_ENUMS.md  # Class/enum rules and limits (removed by prepare)
├── 🤖 .github/workflows/   # ci.yml (matrix from the platform) and release.yml (tag -> PSGallery)
└── 📦 Dist/                # Build output (gitignored, created by build)

./tasks.ps1 <TaskName>

📖 Full tool reference: Tools/README.md

ci.yml runs lint, build, and test on every push and pull request. Which hosts it runs on comes from your ModuleTargetPlatform; the template's own default is all four (Windows PowerShell 5.1, and pwsh 7 on Windows, Linux, and macOS).

release.yml fires on a vX.Y.Z tag. It requires the tagged commit to be on the default branch, requires the tag to match the built manifest version, runs the full CI matrix, then publishes to the PowerShell Gallery and creates a GitHub release whose body is that version's CHANGELOG.md section.

The release flow after prepare_release has stamped the version and the PR is merged:

git checkout master
git pull origin master
git tag v1.1.0
git push origin v1.1.0

The generated module README documents this in full. Pull first: the tag has to land on the merged commit, not on whatever you had locally.

Docs/HARDENING.md covers how to close that path:

🔑 the publishing secret  •  🛡️ a default-branch ruleset with an empty bypass list  •  🏷️ immutable release tags  •  🤖 read-only Actions permissions  •  🔎 secret scanning with push protection  •  ✍️ commit signing

Each step says what it does and why it matters, and most come with a gh command.

None of it is on by default, and none of it survives "Use this template". It is GitHub configuration rather than repository content, so you have to redo it per repo. Do it before the first tag.

• 🔢 Version is controlled in build.psd1 via the SemVer key, which prepare_release stamps for you.
• 📤 Copy Dist/<ModuleName>/<ModuleVersion> to a module path, or let the release workflow publish it.

MIT. See the LICENSE file in this repository.