🚀 DevWizard - Enterprise DevOps Automation CLI + GUI

Generate • Validate • Simulate • Export DevOps pipelines like a pro.

DevWizard is an intelligent DevOps automation engine ⚙️ designed to automatically generate production-ready CI/CD pipelines 🚀, containerization configurations 📦, and deployment workflows 🌐 for any software project with zero manual setup.

By simply providing a repository URL 🔗 or local project path 📁, DevWizard analyzes the project structure 🧠, detects the programming language 💻, framework 🏗️, build tools 🔧, and deployment requirements 🚢, and generates fully validated configurations such as GitHub Actions workflows ⚡, Docker files 🐳, Docker Compose files 📜, and Kubernetes manifests ☸️.

It also performs validation ✅ and simulation 🧪 to ensure the generated pipelines are executable, reliable, and production-safe 🛡️.

DevWizard provides both a modern CLI interface ⌨️ and a powerful GUI interface 🖥️, making it accessible to developers of all experience levels from beginners to enterprise teams- while maintaining enterprise-grade reliability 🏢, automation 🤖, and usability ✨.

❗ Problem Statement

Modern teams still spend too much time manually building CI/CD pipelines, debugging inconsistent workflow behavior, and rewriting boilerplate infrastructure files across projects.

Core problems DevWizard solves

🕒 Time loss from repetitive setup: teams repeatedly create similar pipeline files from scratch.
🧩 Inconsistent standards: each repository ends up with different quality and structure.
🐞 Deployment risk: unvalidated workflows break during CI execution and slow releases.
👥 Skill gap barrier: non-DevOps-heavy teams struggle to bootstrap production-ready automation.

🌍 Why This Matters in Industry

Modern engineering teams lose significant time on repetitive pipeline setup, inconsistent CI rules, and manual deployment glue. DevWizard addresses that gap with deterministic generation and validation.

📈 Business + Engineering Impact

🚀 Faster onboarding: New projects get CI/CD foundations quickly.
🧱 Standardization: Teams share a consistent pipeline baseline across repositories.
🛡️ Risk reduction: Validation/simulation reduce pipeline regressions before merge.
📊 Automation readiness: JSON output integrates with higher-level platform tooling.
💰 Cost efficiency: Less manual DevOps setup means more developer time on product features.

📝 Why command explanations are important

Each command in this README now includes purpose and impact notes so teams can:

understand exactly what the command does,
decide when to use it in delivery workflows,
and reduce trial-and-error during setup.

🌟 Why DevWizard?

⚡ Fast setup for DevOps workflows (GitHub Actions, Docker, Compose, K8s-ready flow)
🧠 Capability-driven generation using project fingerprinting and rule pipelines
✅ Validation + simulation before final export
🧾 Machine-friendly JSON mode for scripts and automation
🧪 Developer diagnostics with raw payload visibility
🖥️ GUI + CLI parity for both technical and non-technical users

🔥 Key Differentiators

🧭 Deterministic stage engine: predictable state transitions for trustworthy CI behavior.
🧠 Capability-aware generation: templates adapt to language/framework/build-tool detection.
✅ Validation + simulation built-in: catch issues before generated assets reach production.
🧾 Automation-native JSON contract: easy integration with bots, portals, and internal platforms.
🖥️ Dual interface strategy: same power for CLI users and GUI-first teams.
🛡️ Enterprise readiness: security-aware, auditable, and standardization-friendly workflow output.

🎬 Demo

Quick Demo Paths

🎥 Video Demo: https://youtu.be/MQqZp1N-VeA
🖼️ UI Walkthrough: see Screenshots & UI Gallery
🎨 Flow Visuals: see Visual Graphics

60-Second CLI Demo

./devwizard.exe generate --repo https://github.com/DhruvP2205/blast-radius --type github-actions --deploy-target vercel --verbose

What this demo proves:

⚡ Fast project analysis,
🧠 Capability-driven output,
✅ Observable deterministic stages,
📦 Export-ready CI artifact generation.

📚 Table of Contents

❗ Problem Statement
🌍 Why This Matters in Industry
🌟 Why DevWizard?
🔥 Key Differentiators
🎬 Demo
✨ Feature Overview
🏗️ Project Structure
🧰 Prerequisites
📥 Installation (Windows, Linux, macOS)
⚡ Quick Start
▶️ How to Run
🛠️ Command Reference
🏢 Industry Use Cases
🧪 Real Examples
🧾 JSON Output Contract
📤 Generated Output Artifacts
🧠 Pipeline Stages
🖼️ Screenshots & UI Gallery
🎨 Visual Graphics
🏛️ Architecture
🔐 Security Model
📦 Build Targets
🛠️ Troubleshooting
👨‍💻 Developer Section
🤝 Contribution Section
🗺️ Roadmap
🌐 Open Source Docs
❓ FAQ
🎥 YouTube & 🔗 LinkedIn

✨ Feature Overview

Core Engine

🔍 Repository/local source analysis
⚙️ Workflow generation from capability planning
✅ Validation and dry-run simulation
📦 Export and artifact write-out

Interfaces

⌨️ CLI for scripted and terminal-driven usage
🖥️ GUI for guided configuration, run monitoring, and settings

UX Improvements Already Included

Ordered stage logging (queued → analyzing → generating → validating → executing → exporting → completed)
Deterministic YAML job ordering (test before deploy)
Styled notifications in GUI (SweetAlert2 toasts for actions like copy/download)

Enterprise-Oriented Design Choices

🧭 Deterministic stage transitions to improve observability and reliability
🧾 Structured serializer output for safer automation integration
📁 Executable-relative frontend path support for portable desktop usage
🛡️ Scoped generation controls to avoid accidental writes in protected contexts

🏗️ Project Structure

DevWizard/
├─ backend/
│  ├─ cmd/cli/                 # CLI entrypoint
│  ├─ internal/                # Core logic, API, engine, CLI modules
│  └─ web/dist/                # Frontend production build served by backend runtime
├─ frontend/                   # React + Vite app
├─ scripts/
│  └─ build-cli.mjs            # Node script to build CLI
├─ docs/
│  └─ images/                  # README screenshots and diagrams
├─ devwizard.exe               # Local built binary (example)
└─ README.md

🧰 Prerequisites

Go (as declared in backend/go.mod, currently go 1.25.7)
Node.js + npm
Git

Recommended:

Windows PowerShell / macOS Terminal / Linux shell
VS Code for full project workflow

📥 Installation (Windows, Linux, macOS)

This project is source-first. Installation means preparing dependencies and building the CLI binary for your platform.

📦 Clone repository (all platforms)

git clone https://github.com/DhruvP2205/DevWizard.git
cd DevWizard

Why this is important:

Ensures you are building and running from the official project repository.

🪟 Windows setup

1) Install tools

winget install Git.Git
winget install OpenJS.NodeJS.LTS
winget install GoLang.Go

Why this is important:

Installs Git for repository operations, Node.js for frontend build, and Go for backend/CLI compilation.

2) Verify installed versions

git --version
node --version
npm --version
go version

Why this is important:

Confirms your environment is valid before running build commands.

3) Build frontend and CLI

npm install
Set-Location frontend
npm install
npm run build
Set-Location ..\backend
go build -o ..\devwizard.exe .\cmd\cli
Set-Location ..

Why this is important:

Produces a working frontend bundle and the Windows executable devwizard.exe.

🐧 Linux setup (Ubuntu/Debian example)

1) Install tools

sudo apt update
sudo apt install -y git curl build-essential
curl -fsSL https://deb.nodesource.com/setup_lts.x | sudo -E bash -
sudo apt install -y nodejs golang-go

Why this is important:

Installs required compilers/runtimes and CLI tools needed by DevWizard.

2) Verify installed versions

git --version
node --version
npm --version
go version

Why this is important:

Prevents hidden environment mismatches before compilation.

3) Build frontend and CLI

npm install
cd frontend
npm install
npm run build
cd ../backend
go build -o ../devwizard-linux-amd64 ./cmd/cli
cd ..
chmod +x ./devwizard-linux-amd64

Why this is important:

Produces a Linux-ready binary and ensures execute permission is set.

🍎 macOS setup (Homebrew)

1) Install tools

brew update
brew install git node go

Why this is important:

Installs all required dependencies using a stable package manager flow.

2) Verify installed versions

git --version
node --version
npm --version
go version

Why this is important:

Ensures your local toolchain is healthy before builds.

3) Build frontend and CLI

npm install
cd frontend
npm install
npm run build
cd ../backend
go build -o ../devwizard-macos-arm64 ./cmd/cli
cd ..
chmod +x ./devwizard-macos-arm64

Why this is important:

Generates a native macOS binary for local execution.

⚡ Quick Start

1) Install dependencies

# Root-level script dependencies
npm install

# Frontend dependencies
cd frontend
npm install
cd ..

Command explanation:

npm install (root): installs workspace-level Node dependencies and helper scripts.
cd frontend: enters the GUI project.
npm install (frontend): installs React/Vite app dependencies.
cd ..: returns to repository root.

Why this is important:

Without dependency installation, builds and GUI runtime will fail.

2) Build frontend

cd frontend
npm run build
cd ..

Command explanation:

cd frontend: navigates to frontend package.
npm run build: generates production frontend bundle used by backend GUI mode.
cd ..: returns to root for next steps.

Why this is important:

GUI startup depends on compiled frontend assets.

3) Build CLI

Option A — script

npm run build:cli

Command explanation:

npm run build:cli: runs the repository’s build script to compile CLI artifacts.

Why this is important:

Gives teams a consistent one-command build path in CI and local dev.

Option B — manual

cd backend
go build -o devwizard.exe ./cmd/cli
cd ..

Command explanation:

cd backend: enters Go module.
go build -o devwizard.exe ./cmd/cli: compiles CLI executable.
cd ..: returns to root.

Why this is important:

Manual build mode is useful for debugging Go-specific issues quickly.

Build root binary directly

cd backend
go build -o ..\devwizard.exe ./cmd/cli
cd ..

Command explanation:

Builds binary directly in root for easier invocation (./devwizard.exe).

Why this is important:

Reduces path friction for teammates and automation scripts.

▶️ How to Run

CLI Mode

./devwizard.exe generate --repo https://github.com/DhruvP2205/blast-radius --type github-actions --deploy-target vercel --verbose

Command explanation:

Runs generate against a remote Git repository and emits GitHub Actions output.

Why this is important:

Demonstrates real-world bootstrap of CI for existing repositories.

GUI Mode

./devwizard.exe --gui

Command explanation:

Starts the local web-based GUI interface.

Why this is important:

Enables less CLI-heavy users to configure and run workflows visually.

GUI Mode with explicit frontend path

./devwizard.exe --gui --frontend ./frontend

Command explanation:

Forces GUI to use a specific frontend path.

Why this is important:

Helps when running from custom directories or debug environments.

🛠️ Command Reference

`generate`

Generate DevOps assets from a source.

devwizard generate --repo <git-url> --type github-actions
devwizard generate --path <local-project-path> --type dockerfile

Command explanation:

First command: generate CI workflow from a Git repository URL.
Second command: generate Dockerfile from a local project path.

Why this is important:

Covers both common enterprise entry points: monorepo/local apps and hosted repositories.

Common flags:

--repo, --branch, --path
--type (github-actions, gitlab-ci, dockerfile, docker-compose, kubernetes, terraform)
--deploy-target (none, vercel, netlify, kubernetes, container, vm)
--runtime, --language, --build-tool, --framework
--no-validate, --simulate, --output, --verbose, --json

`history`

devwizard history --last 10
devwizard history --failed

Command explanation:

--last 10: shows most recent runs for quick monitoring.
--failed: filters failed jobs for faster incident triage.

Why this is important:

Improves operational visibility and debugging speed.

`validate`

devwizard validate --path ./frontend

Command explanation:

Checks generated artifacts and project assumptions without full execution.

Why this is important:

Prevents broken pipeline definitions from reaching CI systems.

`simulate`

devwizard simulate --path ./frontend

Command explanation:

Performs a dry-run simulation to preview behavior and stage progression.

Why this is important:

Reduces deployment risk by catching logic issues earlier.

🏢 Industry Use Cases

🚀 1) Startup teams shipping quickly

Bootstrap CI/CD in minutes instead of hand-writing workflows.
Reduce early-stage DevOps bottlenecks when engineering bandwidth is limited.

🏢 2) Enterprises standardizing delivery

Enforce predictable pipeline patterns across many repositories.
Use structured output and stage logs for governance and internal tooling.

🛠️ 3) Platform engineering teams

Integrate DevWizard JSON mode into internal portals and self-service CI tooling.
Provide a guided GUI path for teams less comfortable with deep CLI usage.

🧪 Real Examples

Generate GitHub Actions with Vercel deploy flow

devwizard generate \
  --repo https://github.com/DhruvP2205/blast-radius \
  --type github-actions \
  --deploy-target vercel \
  --runtime 20.x

Command explanation:

Generates GitHub Actions workflow with Vercel deploy-ready setup and runtime pinning.

Why this is important:

Standardizes app delivery with deployment targets and consistent runtime definitions.

Generate from local project with custom output

devwizard generate \
  --path ./frontend \
  --type github-actions \
  --output ./generated

Command explanation:

Generates files from local source and writes artifacts to ./generated.

Why this is important:

Keeps generated output isolated for review and versioning.

Run with verbose stage diagnostics

devwizard generate --path ./frontend --type github-actions --verbose

Command explanation:

Enables detailed logs for stage-level debugging.

Why this is important:

Speeds up root-cause analysis in CI template issues.

🧾 JSON Output Contract

Use --json for machine-readable responses:

devwizard generate --path ./frontend --type github-actions --json

Command explanation:

Returns structured JSON output for machine consumption.

Why this is important:

Enables integration with internal developer portals, bots, and automation pipelines.

Envelope:

{
  "success": true,
  "data": {
    "jobId": "job_...",
    "actionFile": { "name": "...", "content": "..." }
  }
}

Integration impact:

This output pattern is easy to parse in CI wrappers, bots, orchestration services, and dashboards.

📤 Generated Output Artifacts

Depending on command flags and project detection, DevWizard can generate:

GitHub Actions workflow definitions
GitLab CI definitions
Dockerfile and Docker Compose templates
Kubernetes manifest starters
Terraform starter templates

Why this is important:

Teams can standardize delivery assets while still customizing for project needs.

🧠 Pipeline Stages

DevWizard uses deterministic execution stages:

queued
analyzing
generating
validating
executing
exporting
completed

🖼️ Screenshots & UI Gallery

🖥️ GUI Experience

1) Dashboard Overview
Quick project snapshot with key navigation points for first-time users.

2) Pipeline Generator
Guided workflow setup for generating CI/CD templates in a few steps.

3) Execution Monitor
Live execution visibility with stage progress from queued to completed.

4) Settings Panel
Centralized configuration for environment preferences and defaults.

5) Developer Mode
Advanced diagnostics and deeper runtime insights for technical users.

⌨️ CLI Experience

6) CLI Help Command
Command discovery view for available options, flags, and usage format.

7) CLI History Command
Execution history output for tracking recent and failed runs.

8) CLI Generate Command
Primary command output showing analysis and artifact generation flow.

🎨 Visual Graphics

🧭 Workflow Lifecycle Graphic

🧠 Capability Detection Graphic

Why this is useful:

👀 Makes the README more engaging for first-time visitors.
📊 Communicates architecture and flow faster than text-only sections.
🤝 Helps contributors understand generation logic before reading code.

🏛️ Architecture

flowchart LR
  U[User] --> CLI[DevWizard CLI]
  U --> GUI[DevWizard GUI]
  GUI --> API[Backend API]
  CLI --> CORE[Core Engine]
  API --> CORE
  CORE --> DETECT[Project Detection]
  CORE --> GEN[Template Generation]
  CORE --> VAL[Validation]
  CORE --> SIM[Simulation]
  CORE --> EXP[Export]

🔐 Security Model

DevWizard is designed for safe-by-default generation and enterprise trust.

Security principles

🔒 Local-first analysis: project inspection happens locally where possible.
🧾 Deterministic outputs: same inputs produce predictable pipeline artifacts.
🛡️ Controlled write behavior: generation respects scoped output boundaries.
👁️ Auditability: stage progression and outputs are observable and reviewable.
🚫 No hidden execution model: simulation and validation clarify behavior before adoption.

Operational trust signals

Security reporting process: see SECURITY.md
Community standards: see CODE_OF_CONDUCT.md
Contribution governance: see CONTRIBUTING.md

📦 Build Targets

Typical output names:

🪟 devwizard-windows-amd64.exe
🐧 devwizard-linux-amd64
🍎 devwizard-macos-amd64
🍏 devwizard-macos-arm64

Example cross-build command style:

go build -o devwizard-windows-amd64.exe ./backend/cmd/cli

Command explanation:

Compiles a Windows-target binary from the CLI entrypoint.

Why this is important:

Helps release engineering produce distributable binaries for multiple teams.

🛠️ Troubleshooting

GUI not starting

🧩 Ensure Node/npm are installed and available in PATH.
📁 Ensure frontend path is resolvable:

devwizard --gui --frontend ./frontend

Command explanation:

Starts GUI with explicit path override to frontend assets.

Why this is important:

Resolves path discovery issues in non-standard run locations.

Local path not found

📌 Use correct absolute/relative path.
📂 Ensure target is a directory.

Build or dependency issues

cd frontend && npm install
cd ../backend && go mod tidy

Command explanation:

Reinstalls frontend packages and syncs Go module dependencies.

Why this is important:

Fixes common dependency drift problems across development environments.

👨‍💻 Developer Section

Developer: Dhruv Prajapati
GitHub: https://github.com/DhruvP2205
Project: DevWizard

Maintainer Focus

🧭 Enterprise-grade deterministic behavior
🖥️ Reliable CLI + GUI experience
✅ Production-ready output format and validation pipeline

🤝 Contribution Section

Contributions are welcome and appreciated! 🎉

How to contribute

Fork the repository
Create a feature branch
Make focused changes
Run checks/build locally
Submit a pull request with screenshots/logs where relevant

Recommended checklist before PR

Frontend builds (npm run build)
Backend builds (go build)
Updated docs (if behavior changes)
No unrelated formatting churn

Suggested PR title format

feat(ui): improve sidebar collapse behavior

🗺️ Roadmap

Near-term

✅ Stabilize end-to-end generate/validate/simulate/export journey
🔄 Expand demo assets (GIF/video + richer screenshots)
🧪 Add focused test cases for edge detection and template correctness

Mid-term

🧩 Plugin-style template packs for additional deployment targets
📊 Enhanced run analytics and execution observability in GUI
🔐 Expanded security hardening and policy checks for generated pipelines

Long-term

🏢 Team workspaces and policy profiles for enterprise organizations
🤖 AI-assisted remediation suggestions for invalid CI/CD configurations
🌍 Broader cloud/deployment ecosystem integrations

🌐 Open Source Docs

For full open-source governance and collaboration standards, see:

🧩 These files define legal usage, contribution quality, community behavior, and security disclosure workflows.

❓ FAQ

Is DevWizard only for GitHub Actions?

No. It also supports multiple output types like Dockerfile, Docker Compose, Kubernetes, Terraform, and GitLab CI.

Can I use DevWizard in CI scripts?

Yes. Use JSON mode for machine-readable responses and deterministic stage progression for easier parsing.

Can non-CLI users use this tool?

Yes. GUI mode provides a guided experience for configuration and execution.

🎥 YouTube & 🔗 LinkedIn

🎥 YouTube: https://www.youtube.com/@beTheNOOB
🔗 LinkedIn: https://www.linkedin.com/in/dhruv-prajapati-cybersecurity/

❤️ Support the Project

If this project helps you:

⭐ Star it
🍴 Fork it and build with it
🧪 Test it with your repositories
📝 Improve docs/screenshots
📣 Share with your developer network

Name		Name	Last commit message	Last commit date
Latest commit History 2 Commits
backend		backend
docs/images		docs/images
frontend		frontend
scripts		scripts
.gitignore		.gitignore
CODE_OF_CONDUCT.md		CODE_OF_CONDUCT.md
CONTRIBUTING.md		CONTRIBUTING.md
LICENSE		LICENSE
OPEN_SOURCE.md		OPEN_SOURCE.md
README.md		README.md
SECURITY.md		SECURITY.md
devwizard-linux-amd64		devwizard-linux-amd64
devwizard-macos-amd64		devwizard-macos-amd64
devwizard-macos-arm64		devwizard-macos-arm64
devwizard-windows-amd64.exe		devwizard-windows-amd64.exe
devwizard.exe		devwizard.exe
package-lock.json		package-lock.json
package.json		package.json

Folders and files

Latest commit

History

Repository files navigation

🚀 DevWizard - Enterprise DevOps Automation CLI + GUI

❗ Problem Statement

Core problems DevWizard solves

🌍 Why This Matters in Industry

📈 Business + Engineering Impact

📝 Why command explanations are important

🌟 Why DevWizard?

🔥 Key Differentiators

🎬 Demo

Quick Demo Paths

60-Second CLI Demo

📚 Table of Contents

✨ Feature Overview

Core Engine

Interfaces

UX Improvements Already Included

Enterprise-Oriented Design Choices

🏗️ Project Structure

🧰 Prerequisites

📥 Installation (Windows, Linux, macOS)

📦 Clone repository (all platforms)

🪟 Windows setup

🐧 Linux setup (Ubuntu/Debian example)

🍎 macOS setup (Homebrew)

⚡ Quick Start

1) Install dependencies

2) Build frontend

3) Build CLI

Option A — script

Option B — manual

Build root binary directly

▶️ How to Run

CLI Mode

GUI Mode

GUI Mode with explicit frontend path

🛠️ Command Reference

generate

history

validate

simulate

🏢 Industry Use Cases

🚀 1) Startup teams shipping quickly

🏢 2) Enterprises standardizing delivery

🛠️ 3) Platform engineering teams

🧪 Real Examples

Generate GitHub Actions with Vercel deploy flow

Generate from local project with custom output

Run with verbose stage diagnostics

🧾 JSON Output Contract

📤 Generated Output Artifacts

🧠 Pipeline Stages

🖼️ Screenshots & UI Gallery

🖥️ GUI Experience

⌨️ CLI Experience

🎨 Visual Graphics

🧭 Workflow Lifecycle Graphic

🧠 Capability Detection Graphic

🏛️ Architecture

🔐 Security Model

Security principles

Operational trust signals

📦 Build Targets

🛠️ Troubleshooting

GUI not starting

Local path not found

Build or dependency issues

👨‍💻 Developer Section

Maintainer Focus

🤝 Contribution Section

How to contribute

Recommended checklist before PR

Suggested PR title format

🗺️ Roadmap

Near-term

Mid-term

Long-term

`generate`

`history`

`validate`

`simulate`

Packages