Keep your PowerShell development environments perfectly synchronized across all your machines
Tired of manually syncing your development environment across multiple machines?
We've all been there - following lengthy OneNote instructions, manually installing tools, copy-pasting configurations, and hoping you didn't miss anything. Every new machine or reinstall meant hours of tedious setup work.
PowerShell DevKit eliminates that pain:
- ✅ One command to set up your complete environment
- ✅ Git-based configuration keeps everything in sync
- ✅ Automatic updates across all your machines
- ✅ Intelligent recovery when things go wrong
- ✅ Consistent experience whether you're on your desktop, laptop, or fresh Windows install
Clone once, run Setup.ps1, and you're done. Your perfect PowerShell environment, reproduced identically everywhere.
# 1. Clone the repository
git clone https://github.com/Tsabo/PowerShell-DevKit.git
cd PowerShell-DevKit
# 2. Run setup
.\Scripts\Setup.ps1
# 3. Validate installation
.\Scripts\Test.ps1
# 4. Keep everything updated
.\Scripts\Update.ps1📖 Read the Full Documentation →
Modern Terminal Experience:
- oh-my-posh with beautiful, informative prompts
- Yazi file manager with git-aware navigation
- Fuzzy finding for files and command history
- Smart directory navigation with zoxide
- Git integration throughout
Smart Automation:
- Component-based architecture with intelligent failure recovery
- Multi-source package management (winget, PSGallery, Scoop, Yazi)
- Comprehensive environment validation
- Update-safe customization patterns
Everything Stays in Sync:
- Git-managed configurations auto-sync across machines
- Single source of truth for all components
- Update once, deploy everywhere
| Section | Description |
|---|---|
| Getting Started | Installation, requirements, quick start guide |
| Components | Detailed docs for oh-my-posh, Yazi, PowerShell modules |
| Scripts | Setup, Test, Update, Deploy-Terminal scripts |
| Configuration | Customize modules, profiles, and themes |
| Architecture | System design and failure recovery |
| Development | Contributing guide and developer reference |
| Help | Troubleshooting and FAQ |
We welcome contributions! See our Contributing Guide for the complete workflow.
Quick start: Fork → Create feature branch → Run .\Scripts\Validate-Code.ps1 → Submit PR
MIT License - See LICENSE for details.
Made with ❤️ for PowerShell developers who value their time