dev-env-kit

Public Windows development environment kit for quickly rebuilding a new PC from CLI-managed manifests. The repository stores scripts and package manifests only. It does not store installers, tokens, SSH keys, IDE sign-in state, or private machine credentials.

What It Installs

• Git
• Python 3.13
• uv
• Oracle JDK 20
• Visual Studio Code and extensions
• MSYS2 UCRT64 GCC toolchain

Export From This PC

Run this from the repository root on a configured machine:

Set-ExecutionPolicy -Scope CurrentUser RemoteSigned
.\export-current.ps1
git status
git add .
git commit -m "Export Windows dev environment kit"
git push

Before pushing to a public repository, inspect the diff:

git diff --cached

Do not commit tokens, SSH keys, private package feeds, internal URLs, or local credential files.

Install On A New Windows 11 PC

Install Git first if it is not already present, then clone this repository:

git clone https://github.com/<your-user>/dev-env-kit.git
cd dev-env-kit
Set-ExecutionPolicy -Scope CurrentUser RemoteSigned
.\install.ps1
.\scripts\verify.ps1

The installer uses online package sources:

• winget for core applications
• MSYS2 pacman for UCRT64 GCC packages
• pip for Python CLI tools
• VS Code Marketplace for extensions

Manifests

• manifests/winget.packages.json: winget package IDs to install.
• manifests/vscode.extensions.txt: VS Code extension IDs to install.
• manifests/vscode.extensions.lock.txt: exported extension versions for audit.
• manifests/msys2.packages.txt: MSYS2 packages to install.
• manifests/python.tools.txt: Python CLI tools installed with pip.
• manifests/gitconfig.template: safe global Git config template.

Public Repository Safety

This kit intentionally excludes:

• VS Code Settings Sync state
• GitHub or other API tokens
• SSH private keys
• IDE login sessions
• company or private registry credentials
• machine-specific local config files

Put local-only settings in config.local.ps1. That file is ignored by Git.