https://github.com/xaoscience/dev-control
A collection of powerful CLI tools, scripts and templates for streamlined Git workflow, repository management, and shell productivity.
https://github.com/xaoscience/dev-control
aliases automation bash cli developer-tools devops dotfiles git github github-actions productivity repository-management shell shell-scripts submodules templates workflow
Last synced: 19 days ago
JSON representation
A collection of powerful CLI tools, scripts and templates for streamlined Git workflow, repository management, and shell productivity.
- Host: GitHub
- URL: https://github.com/xaoscience/dev-control
- Owner: xaoscience
- License: gpl-3.0
- Created: 2025-12-12T12:20:13.000Z (2 months ago)
- Default Branch: Main
- Last Pushed: 2026-01-20T22:32:02.000Z (21 days ago)
- Last Synced: 2026-01-21T05:35:24.097Z (21 days ago)
- Topics: aliases, automation, bash, cli, developer-tools, devops, dotfiles, git, github, github-actions, productivity, repository-management, shell, shell-scripts, submodules, templates, workflow
- Language: Shell
- Homepage:
- Size: 397 KB
- Stars: 1
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: docs/README.md
- Changelog: CHANGELOG.md
- Contributing: docs/CONTRIBUTING.md
- License: LICENSE
- Code of conduct: docs/CODE_OF_CONDUCT.md
- Security: docs/SECURITY.md
Awesome Lists containing this project
README
# Dev-Control
---
🛠️ A collection of powerful CLI tools and scripts for streamlined Git workflow, repository management, and shell productivity.
---
## 📋 Table of Contents
- [Overview](#-overview)
- [Features](#-features)
- [Installation](#-installation)
- [Usage](#-usage)
- [Scripts](#-scripts)
- [Documentation](#-documentation)
- [Contributing](#-contributing)
- [Roadmap](#-roadmap)
- [Support](#-support)
- [License](#-license)
---
## 🔍 Overview
**Dev-Control** is a comprehensive toolkit designed to enhance your Git and shell workflow. It provides:
- **Alias Management**: Interactive setup of productivity-boosting shell aliases
- **Template Loading**: Quick initialisation of new repositories with standardised templates
- **Module Nesting**: Automated management of Git submodules in complex project hierarchies
- **Workflow Templates**: Pre-configured GitHub Actions for common automation tasks
### Why Dev-Control?
Managing multiple repositories, nested submodules, and maintaining consistent configurations across projects is time-consuming and error-prone. Dev-Control automates these tasks while remaining portable and easy to share across systems.
---
## ✨ Features
- 🚀 **Interactive Alias Installer** - Dynamically detects script paths and creates portable aliases
- 🔧 **Template System** - Initialise repos with docs, workflows, and configuration templates
- 📦 **Submodule Management** - Auto-generate `.gitmodules` and maintain `.tmp` for nested repos
- 🔒 **Safety Aliases** - Protective wrappers for dangerous commands (`rm`, `mv`, `cp`)
- ⚡ **Git Shortcuts** - Optimised aliases for common Git operations
- 🐳 **Container Shortcuts** - Quick access to Docker/Podman commands
- 🌐 **Network Utilities** - IP checking, port monitoring, and connectivity tools
- 📁 **Directory Operations** - Enhanced navigation and file management
- 🤖 **GitHub MCP Setup** - Automated GitHub MCP server configuration for VS Code with secure token management
- 📦 **Multi-Platform Packaging** - Build tarballs, Homebrew, Snap, Debian, Nix, and Docker packages
- 🎨 **Glamorous TUI Theming** - Charmbracelet Gum integration with matrix/hacker/cyber themes
- 🌐 **Web Terminal** - Docker packages with ttyd for browser-based access
- 🐳 **Devcontainer Setup** - Auto-configure rootless podman and generate optimised devcontainer.json with secure mounts
---
## 📥 Installation
### Prerequisites
- Bash 4.0+ or Zsh
- Git 2.0+
- Standard Unix utilities (`find`, `sed`, `grep`)
### Quick Start
```bash
# Clone the repository
git clone https://github.com/xaoscience/dev-control.git
cd dev-control
# Run the interactive alias installer
./scripts/alias-loading.sh
# Or run individual scripts
./scripts/template-loading.sh
./scripts/module-nesting.sh
```
### Manual Installation
```bash
# Add to your .bashrc or .bash_profile
source /path/to/dev-control/scripts/alias-loading.sh --source-only
```
---
## 🚀 Usage
### Main Menu
Use the main `dev-control.sh` wrapper to access all tools via interactive menu:
```bash
# Interactive menu - choose any tool
./scripts/dev-control.sh
# Or use the alias (after running alias-loading.sh)
dc-control
# Direct command mode - skip the menu
./scripts/dev-control.sh repo # Create repository
./scripts/dev-control.sh pr # Create pull request
./scripts/dev-control.sh fix # Fix commit history
```
### Alias Loading
```bash
# Interactive installation - choose which alias categories to install
./scripts/alias-loading.sh && source ~/.bashrc
# Reinstall all and automatically reload
dc-aalias
```
### Alias Usage
**Categories:**
| Category | Commands / Notes |
| --- | --- |
| **Git Control (dc-*)** | `dc-fix`, `dc-pr`, `dc-create`, `dc-mcp` |
| **Git Shortcuts** | `gs`, `ga`, `gc`, `gp`, `gl` |
| **Safety Nets** | `rm -i`, `cp -i`, `mv -i` under aliases of `rm`, `cp`, `mv`|
| **System Monitoring** | `ports`, `meminfo`, `disk` |
| **Directory Operations** | `md`, `rd`, `..`, `ll` |
| **Network Utilities** | `myip`, `ping`, `fastping` |
| **Container Shortcuts** | `dps`, `dpsa`, `drm`, `drmi` |
| **Quick Edits** | `bashrc`, `reload` |
**Examples**
```bash
# Git commit amend (no edit) and push force
gca
# Similar amend, with original author date (also restores it after gca)
gcda
# Git push force with lease
gcpf
# Decorated, oneline Git log
gl
```
*Tip: run `./scripts/alias-loading.sh` and `source ~/.bashrc` to install or refresh aliases.*
### Template Loading
Allows for creation of new $NAME-templates folders, which will be copied by default.
**Note:** During interactive setup you can specify the repository owner (GitHub username or organisation). By default `dc-init` will use the detected org from the remote or your `gh` account, but you may override it.
```bash
# Interactive mode - initialise a new repo with templates
dc-init
# Or run directly
./scripts/template-loading.sh
# CLI mode - update specific files with path support
./scripts/template-loading.sh -f docs/CONTRIBUTING.md,docs/SECURITY.md -o
# CLI options:
# -f, --files FILE1,FILE2 Process specific files (supports paths like docs/FILE.md)
# -o, --overwrite Overwrite existing files without prompting
# -h, --help Show help and list available templates
```
### Repository Creation
```bash
# Interactive creation of new GitHub repository
dc-create
# Or run directly
./scripts/create-repo.sh
```
### Pull Request Creation
```bash
# Interactive creation of pull request from current branch
dc-pr
# Or run directly
./scripts/create-pr.sh
```
### Module Nesting
```bash
# Scan current directory for git repos and generate .gitmodules
dc-modules
# Or run directly
./scripts/module-nesting.sh
# Specify a custom root directory
./scripts/module-nesting.sh /path/to/project
```
#### Extra features
Use the action flags below to manage per-module temporary folders after module-nesting (e.g. `--copy-temp`) or independently (e.g. `--only-copy-temp`). All flows support `--dry-run` for safe previews.
##### Feature breakdown
- `--copy-temp` / `--only-copy-temp`
- What it does: Collects temporary folders (e.g., `.tmp`, `tmp`, `.temp`) and merges their contents into per-parent directories under `
`$ROOT/.tmp/` non-destructively (does not overwrite existing files).
- When to use: Consolidate per-module temporary build outputs for cleanup or archiving.
- Preview: `./scripts/module-nesting.sh --only-copy-temp --dry-run /path/to/project`
- `--prune` / `--only-prune`
- What it does: Moves originals to a recycle location (or deletes with `--delete`) and replaces originals with symlinks pointing at `
`$ROOT/.tmp/`.
- If no copied record exists, `--only-prune --dry-run` simulates a `--only-copy-temp --dry-run` `
`$ROOT/.tmp/` destinations rather than ephemeral `/tmp` paths.
- Preview: `./scripts/module-nesting.sh --only-prune --dry-run /path/to/project`
- `--aggressive`
- What it does: Merges temp folders into `
`$ROOT/.tmp/`, removes original temp folders, replaces them with directory symlinks, and appends entries to the nearest `.gitignore` (except for folders named `.tmp`).
- Preview: `./scripts/module-nesting.sh --aggressive --dry-run /path/to/project` (reports merges, removals, and `.gitignore` changes; reports `already contains` when no change is needed)
- `--dry-run` behavior
- Use `--dry-run` with any flow to preview actions without modifying your workspace.
- `.gitmodules` generation now respects `--dry-run` and will report file writes/removals; enable `DEBUG=true` to preview content snippets during a dry-run.
- `--test`
- Runs a safe `copy-temp` → `prune` → `aggressive` sequence in `--dry-run` mode: `./scripts/module-nesting.sh --test`
Examples:
```bash
# Preview .gitmodules generation without making changes
./scripts/module-nesting.sh --dry-run /path/to/project -y
# Preview copy -> prune -> aggressive sequence
./scripts/module-nesting.sh --test
# Preview aggressive changes (including .gitignore simulation)
./scripts/module-nesting.sh --aggressive --dry-run /path/to/project
```
> Tip: Run with `DEBUG=true` (for example `DEBUG=true ./scripts/module-nesting.sh --dry-run /path -y`) for additional diagnostic output and a content preview of simulated `.gitmodules`.
### History Fixing
Interactively rewrite commit history with fine-grained control over commit messages, author/committer dates, signing and reconstruction strategies.
##### Feature breakdown
- `--range` / `-r`
- Select a commit range to operate on (default: `HEAD=10`). Examples: `HEAD=5`, `main..HEAD`, `abc123..def456`.
- `--amend` / `-a`
- Amend a non-tip commit while preserving dates and optionally signing the amended commit. Example: `--amend HEAD=2`.
- `--sign` / `--atomic-preserve`
- `--sign`: re-sign commits in the selected range (requires GPG).
- `--atomic-preserve`: recreate commits deterministically (including merges) with `git commit-tree`, sign them and set author/committer dates atomically.
- `--drop`
- Remove a single non-root commit from history (specify commit hash).
- Harness & safety helpers (`--harness-drop`, `--harness-sign`, `--harness-no-cleanup`)
- Run minimal harnesses that apply operations safely in a temporary branch and produce a backup bundle for inspection.
- Conflict & reconstruction options (`--auto-resolve`, `--reconstruct-auto`, `--allow-override`)
- `--auto-resolve ` will auto-add conflicted files using the chosen strategy during rebase.
- `--reconstruct-auto` retries reconstruction with common strategies on failure.
- `--allow-override` skips confirmation when replacing the original branch with a temporary branch.
- Worktree & restore helpers (`--update-worktrees`, `--restore`)
- `--update-worktrees` detects local worktrees with the branch checked out and updates them safely (creates bundle backup).
- `--restore` lists and restores backup bundles/tags interactively.
- Dry-run & diagnostic (`-d`, `--dry-run`, `-v`)
- Use `--dry-run` to preview all changes without applying them; `-v` or `--verbose` increases diagnostic output.
- Stash support (`-s`)
- `--stash N` lets you selectively apply files from `stash@{N}` into the rewritten commits.
- Cleanup options (`--no-cleanup`, `--only-cleanup`)
- `--no-cleanup`: skip the interactive cleanup prompt at the end of a run and do not offer to delete temporary backup refs or branches.
- `--only-cleanup`: only perform cleanup of temporary tags, bundles and backup branches (useful to tidy harness artifacts after a failed run).
##### Env vars vs CLI flags
Most behaviours are available either via environment variables or equivalent CLI flags. Common env vars you may use are: `PRESERVE_TOPOLOGY`, `UPDATE_WORKTREES`, `NO_EDIT_MODE`, `AUTO_FIX_REBASE`, `RECONSTRUCT_AUTO` — you can set these in your shell or pass the corresponding flags when invoking the script.
##### Examples
```bash
# Interactive: edit the last 10 commits
./scripts/fix-history.sh
# Preview changes without applying
./scripts/fix-history.sh --dry-run --range HEAD=20
# Re-sign an entire branch and show verbose output
./scripts/fix-history.sh --sign --range HEAD=all -v
# Use env-vars (equivalent to flags) for a non-interactive run
PRESERVE_TOPOLOGY=TRUE UPDATE_WORKTREES=true NO_EDIT_MODE=true AUTO_FIX_REBASE=true RECONSTRUCT_AUTO=true \
./scripts/fix-history.sh --sign --range HEAD=all -v
```
> Tip: When experimenting with large-scale rewrites, prefer `--dry-run` and harness modes to capture backups before making changes.
### GitHub MCP Server Setup
Automatically configure GitHub MCP and additional MCP servers for VS Code with secure token management:
```bash
# Full interactive setup - initialize MCP and configure servers
dc-mcp
# Or run directly
./scripts/mcp-setup.sh
# Configuration-only mode (with existing token)
./scripts/mcp-setup.sh --config-only
# Test existing MCP connection
./scripts/mcp-setup.sh --test
# Show current token info (masked)
./scripts/mcp-setup.sh --show-token
# Options:
# (no args) Initialize MCP and select servers to install (DEFAULT)
# --config-only Only generate MCP base configuration
# --test Test GitHub MCP connection
# --show-token Display current token info (masked)
# --help Show help message
```
#### What it does:
- ✅ Authenticates with your GitHub account
- ✅ Creates a Personal Access Token (PAT) with minimal required scopes
- ✅ Sets a 90-day expiration policy for security
- ✅ Generates VS Code MCP settings with secure variable substitution:
- Optimal mounts for GPG, docker/podman, git, wrangler
- Configured git user and optional GPG signing (script prompts for your key ID; no key material is embedded)
- ✅ Offers interactive server selection:
- GitHub MCP (HTTP remote) — GitHub API access
- Stack Overflow MCP (HTTP remote) — Search Q&A
- Firecrawl MCP (Docker/NPX) — Web scraping and crawling
- ✅ All servers appear consistently as manually installed
- ✅ Token is saved in the system keychain or prompted per VS Code session (secure input)
### Devcontainer Setup
Auto-configure rootless podman and generate optimised `.devcontainer/devcontainer.json`:
```bash
# Interactive setup - detects project path or prompts for input
dc-contain
# Or run directly
./scripts/containerise.sh
# Specify custom project path
./scripts/containerise.sh /path/to/project
# Options:
# (no args) Uses current directory
# /path/to/project Specify custom project path
# --help Show help message
```
#### What it does:
- ✅ Checks for rootless podman (installs if needed)
- ✅ Detects system paths (GPG, podman socket, git config, etc.)
- ✅ Generates `.devcontainer/devcontainer.json` with:
- Optimal mounts for GPG, docker/podman, git, wrangler
- Configured git user and optional GPG signing (script prompts for your key ID; no key material is embedded)
- Universal devcontainer image
- ✅ Guides VS Code reopening with devcontainer activation
- ✅ Ensures configurations persist and work across sessions
### Multi-Platform Packaging
Build and distribute dev-control (or any bash CLI tool) across multiple platforms with glamorous TUI theming:
```bash
# Interactive mode - menu-driven package selection
dc-package
# Or run directly
./scripts/packaging.sh
# Initialize packaging configuration
./scripts/packaging.sh --init
# Build specific package types
./scripts/packaging.sh --tarball # Release archive (.tar.gz)
./scripts/packaging.sh --homebrew # Homebrew formula
./scripts/packaging.sh --snap # Snap package
./scripts/packaging.sh --debian # Debian package (.deb)
./scripts/packaging.sh --nix # Nix flake
./scripts/packaging.sh --docker # Docker image with ttyd web terminal
# Build all packages at once
./scripts/packaging.sh --all
# Build with specific theme
./scripts/packaging.sh --theme cyber --all
# Options:
# --init Create .dc-package.yaml configuration
# --all Build all package types
# --tarball Build release tarball with SHA256
# --homebrew Generate Homebrew formula
# --snap Generate Snap package config
# --debian Build Debian package structure
# --nix Generate Nix flake
# --docker Build Docker image with ttyd web interface
# --theme THEME Set UI theme (matrix, hacker, cyber)
# -o, --output DIR Output directory (default: ./dist)
# --dry-run Preview without building
# --verbose Show detailed output
# --help Show help message
```
#### Supported Package Formats
| Format | Output | Install Method |
|--------|--------|----------------|
| **Tarball** | `.tar.gz` + SHA256 | `./install.sh` |
| **Homebrew** | Ruby formula | `brew install` |
| **Snap** | `snapcraft.yaml` | `snap install` |
| **Debian** | `.deb` structure | `dpkg -i` / `apt install` |
| **Nix** | `flake.nix` | `nix build` / `nix develop` |
| **Docker** | `Dockerfile` + compose | `docker run` with web terminal |
#### TUI Theming
Packaging integrates with [Charmbracelet Gum](https://github.com/charmbracelet/gum) (see [license](https://github.com/charmbracelet/gum/blob/6045525ab92f75c169d3c69596844d8748437e37/LICENSE)) for glamorous terminal UI with 3 built-in themes:
| Theme | Style | Colour |
|-------|-------|--------|
| **matrix** | Green fluorescent terminal | 🟢 `#00ff00` |
| **hacker** | Orange/amber retro | 🟠 `#ff8c00` |
| **cyber** | Blue cyberpunk neon | 🔵 `#00d4ff` |
Set theme via environment variable or CLI:
```bash
# Environment variable (persists for session)
export DC_THEME=matrix
# CLI flag (per-command)
./scripts/packaging.sh --theme hacker --docker
# Docker with theme
docker run -p 8080:8080 -e DC_THEME=cyber dev-control
```
#### Configuration File
Run `--init` to create `.dc-package.yaml`:
```yaml
# .dc-package.yaml
name: my-tool
version: 1.0.0
description: "My awesome CLI tool"
homepage: https://github.com/user/repo
license: MIT
maintainer: "Name "
entry_point: ./main.sh
theme: matrix
include:
- scripts/
- config/
- docs/
- README.md
- LICENSE
dependencies:
- git
- gh
- jq
- gum
```
#### Docker Web Terminal
The Docker package includes [ttyd](https://github.com/tsl0922/ttyd) for browser-based terminal access:
```bash
# Build and run
cd dist/docker
docker build -t dev-control .
docker run -p 8080:8080 -e DC_THEME=matrix dev-control
# Access at http://localhost:8080
# Or run all themed instances with docker-compose
docker-compose --profile themed up --build
# Matrix: http://localhost:8081
# Hacker: http://localhost:8082
# Cyber: http://localhost:8083
```
---
## 📜 Scripts
| Script | Description |
|--------|-------------|
| [`dev-control.sh`](../scripts/dev-control.sh) | **Main entry point** - Interactive menu for all tools |
| [`alias-loading.sh`](../scripts/alias-loading.sh) | Interactive alias installer with category selection |
| [`template-loading.sh`](../scripts/template-loading.sh) | Repository template initialisation tool |
| [`create-repo.sh`](../scripts/create-repo.sh) | Interactive GitHub repository creator |
| [`create-pr.sh`](../scripts/create-pr.sh) | Interactive pull request creator |
| [`module-nesting.sh`](../scripts/module-nesting.sh) | Automated `.gitmodules` generator for nested repos |
| [`fix-history.sh`](../scripts/fix-history.sh) | Interactive commit history rewriting tool |
| [`mcp-setup.sh`](../scripts/mcp-setup.sh) | GitHub & additional MCP server setup for VS Code with token management |
| [`containerise.sh`](../scripts/containerise.sh) | Rootless podman setup and devcontainer.json generator with mount configuration |
| [`packaging.sh`](../scripts/packaging.sh) | Multi-platform package builder with TUI theming (tarball, Homebrew, Snap, Debian, Nix, Docker) |
| [`git-control.sh`](../scripts/git-control.sh) | Unified git operations wrapper (staging, committing, pushing, PRs) |
### Shared Libraries
| Library | Description |
|---------|-------------|
| [`lib/tui.sh`](../scripts/lib/tui.sh) | Gum-based TUI wrapper with 3 themes (matrix, hacker, cyber) and fallback support |
| [`lib/colors.sh`](../scripts/lib/colors.sh) | ANSI colour definitions for terminal output |
| [`lib/print.sh`](../scripts/lib/print.sh) | Formatted print functions (headers, info, success, errors) |
| [`lib/config.sh`](../scripts/lib/config.sh) | Configuration file loading and validation |
| [`lib/git-utils.sh`](../scripts/lib/git-utils.sh) | Git helper functions (branch detection, remote parsing) |
| [`lib/validation.sh`](../scripts/lib/validation.sh) | Input validation utilities |
### Doc Templates
| Template | Description |
|----------|-------------|
| [`README.md`](../docs-templates/README.md) | Full-featured README with badges and sections |
| [`CONTRIBUTING.md`](../docs-templates/CONTRIBUTING.md) | Contribution guidelines template |
| [`CODE_OF_CONDUCT.md`](../docs-templates/CODE_OF_CONDUCT.md) | Community code of conduct |
| [`SECURITY.md`](../docs-templates/SECURITY.md) | Security policy template |
### License Templates
| Template | Description |
|----------|-------------|
| [`Apache License 2.0`](../license-templates/Apache-2.0) | Permissive with explicit patent grant and NOTICE handling |
| [`BSD 3-Clause`](../license-templates/BSD-3-Clause) | Permissive license with non-endorsement clause |
| [`GNU GPL v3.0`](../license-templates/GPL-3.0) | Strong copyleft — modifications must be released under GPLv3 |
| [`MIT License`](../license-templates/MIT) | Very permissive, minimal requirements |
### GitHub Templates
| Template | Description |
|----------|-------------|
| [`ISSUE_TEMPLATE/bug_report.md`](../github-templates/ISSUE_TEMPLATE/bug_report.md) | Bug report issue template |
| [`ISSUE_TEMPLATE/feature_request.md`](../github-templates/ISSUE_TEMPLATE/feature_request.md) | Feature request issue template |
| [`PULL_REQUEST_TEMPLATE.md`](../github-templates/PULL_REQUEST_TEMPLATE.md) | Pull request template |
### Workflow Templates
| Workflow | Description |
|----------|-------------|
| [`dependabot-automerge.yml`](../workflows-templates/dependabot-automerge.yml) | Auto-merge Dependabot PRs |
| [`init.yml`](../workflows-templates/init.yml) | Standalone workflow - copy to any repo |
| [`remote-init.yml`](../workflows-templates/remote-init.yml) | Calls the reusable workflow remotely |
### Workflows
| Workflow | Description |
|----------|-------------|
| [`central-loader.yml`](../.github/workflows/central-loader.yml) | Reusable workflow (call from other repos) |
---
## 🔄 GitHub Actions Workflows
In addition to initialising from local (dc-init), Dev-Control provides two ways to initialise templates via GitHub Actions:
### Option 1: Standalone Workflow (Recommended)
Copy `workflows-templates/init.yml` to your repo's `.github/workflows/` folder.
```bash
# From your target repository
mkdir -p .github/workflows
curl -sL https://raw.githubusercontent.com/xaoscience/dev-control/main/workflows-templates/init.yml \
-o .github/workflows/init.yml
git add .github/workflows/init.yml
git commit -m "Add template initialisation workflow"
git push
```
Then go to **Actions** → **Initialise Repository Templates** → **Run workflow**
### Option 2: Reusable Workflow (Remote)
Copy `workflows-templates/remote-init.yml` or call Dev-Control's reusable workflow directly:
```yaml
# .github/workflows/remote-init.yml
name: Initialise Documentation
on:
workflow_dispatch:
permissions:
contents: write
pull-requests: write
jobs:
init-templates:
uses: xaoscience/dev-control/.github/workflows/central-loader.yml@main
with:
project_name: 'My Project'
short_description: 'A cool project'
license_type: 'MIT'
stability: 'experimental'
templates: 'all'
create_pr: true
```
### Workflow Features
- ✅ **No PAT required** - Uses standard `GITHUB_TOKEN`
- ✅ **Creates PR by default** - Review before merging
- ✅ **Configurable** - Choose templates, license, stability
- ✅ **Auto-populates** - Fills in repo name, org, URLs automatically
- ✅ **Dynamic folders** - Scans all `*-templates` folders for future expansion
---
## 📚 Documentation
| Document | Description |
|----------|-------------|
| [📖 README](docs/README.md) | This file - project overview |
| [🤝 Contributing](docs/CONTRIBUTING.md) | How to contribute |
| [📜 Code of Conduct](docs/CODE_OF_CONDUCT.md) | Community guidelines |
| [🔒 Security](docs/SECURITY.md) | Security policy |
---
## 🤝 Contributing
Contributions are welcome! Please read our [Contributing Guidelines](CONTRIBUTING.md) before submitting PRs.
1. Fork the repository
2. Create your feature branch (`git checkout -b feature/AmazingFeature`)
3. Commit your changes (`git commit -m 'Add some AmazingFeature'`)
4. Push to the branch (`git push origin feature/AmazingFeature`)
5. Open a Pull Request
See also: [Code of Conduct](CODE_OF_CONDUCT.md) | [Security Policy](SECURITY.md)
---
## 🗺️ Roadmap
- [x] Core alias loading script with interactive selection
- [x] Template system for repository documentation
- [x] Submodule nesting management
- [x] Dependabot automerge workflow
- [x] GitHub Actions workflow for remote template initialisation
- [x] Reusable workflow for cross-repo template loading
- [x] Config file support for persistent preferences
- [x] Multi-platform packaging (tarball, Homebrew, Snap, Debian, Nix, Docker)
- [x] Glamorous TUI theming with Charmbracelet Gum
- [x] Web terminal support via ttyd in Docker packages
- [ ] Zsh compatibility layer
- [ ] Fish shell support
- [ ] GUI wrapper / desktop app (Tauri, Wails, or Bubble Tea)
- [ ] Plugin system for custom alias categories
See the [open issues](https://github.com/xaoscience/dev-control/issues) for a full list of proposed features and known issues.
---
## 💬 Support
- 💻 **Issues**: [GitHub Issues](https://github.com/xaoscience/dev-control/issues)
- 💬 **Discussions**: [GitHub Discussions](https://github.com/xaoscience/dev-control/discussions)
---
## 📄 License
Distributed under the GPL-3.0 License. See [`LICENSE`](../LICENSE) for more information.
---
