bytelyst-devops-tools/aliases/README.md

2.3 KiB

Shell Aliases

Reusable Bash/Zsh aliases for common shell, git, tmux, directory, and listing shortcuts.

Install

Run the installer:

/Users/saravana/BytelystAI/bytelyst-devops-tools/aliases/install.sh

The installer detects macOS/Linux and Bash/Zsh, then adds a managed source block to the right startup file. It is safe to run more than once and creates a timestamped backup before changing the startup file.

After running the installer, open a new shell or run source ~/.zshrc for Zsh or source ~/.bashrc / source ~/.bash_profile for Bash. A shell script cannot add aliases to the already-running parent shell by itself.

Preview the change without writing files:

/Users/saravana/BytelystAI/bytelyst-devops-tools/aliases/install.sh --dry-run

You can also source the aggregate loader manually.

For Zsh, add this to ~/.zshrc:

source /Users/saravana/BytelystAI/bytelyst-devops-tools/aliases/_source_all.alias

For Bash, add this to ~/.bashrc:

source /Users/saravana/BytelystAI/bytelyst-devops-tools/aliases/_source_all.alias

The loader can be sourced from any directory. It discovers the aliases/ folder and loads each alias file from that path.

Requirements

  • Supported shells: Bash and Zsh
  • Optional commands used by aliases: git, tmux, tree, vim or $EDITOR, and caffeinate (macOS, for awake/longrun)

Examples

gs          # git status
gd          # git diff
tl          # tmux list-sessions
tn work     # tmux new-session -s work
ta work     # tmux attach-session -t work
aq <cmd>    # agent-queue runner (init|add|run|status|watch|dash|stop|logs)
aqs         # agent-queue status
aqd         # agent-queue Node live dashboard
awake <cmd> # macOS: run <cmd> while keeping the machine awake (caffeinate -dimsu)
longrun phase3 codex --full-auto "<prompt>"   # detached+awake+logged overnight run
ta phase3   # reattach to the run;  tail -f ~/longrun-phase3-*.log  to follow output

See AI.dev/CHEATSHEETS/long-running-jobs.md (in learning_ai_common_plat) for the full overnight-run guide and best practices.

Local Aliases

Keep machine- or org-specific shortcuts out of the portable default files. Start from _local.example.alias if you want private local aliases such as branch-specific git commands.