LogoAkhshy

AliasMate

Your terminal command management companion

Save, manage, and re-run shell commands with their working directories. Eliminate repetitive typing and boost your productivity.

Lightning Fast
Save Time
Context Aware
Cross Platform

Quick Install

npm install -g aliasmate

Why Use AliasMate?

The main purpose is simple: eliminate repetitive terminal work and reduce errors

Stop Retyping Complex Commands

Save long, complex commands once and run them with a simple alias. No more scrolling through history or remembering intricate syntax.

Boost Your Productivity

Reduce command execution time from minutes to seconds. Focus on building, not on typing or remembering paths.

Perfect for Team Workflows

Export and share command sets with your team. Onboard new developers faster with standardized workflows.

Never Lose Context

Commands remember their working directory. Run project-specific commands from anywhere in your filesystem.

Real-World Impact

80%

Time saved on repetitive commands

95%

Reduction in typing errors

60%

Faster team onboarding

How to Use

Simple commands for powerful workflow automation

Save the Last Command

Just ran a command? Save it instantly with the name you choose.

aliasmate prev <name>

💡 Perfect for capturing that command you just perfected

Example

$ aliasmate prev build

Run a Saved Command

Execute any saved command from anywhere. Optionally override the directory.

aliasmate run <name> [path]

💡 Add '.' to run in current directory: aliasmate run build .

Example

$ aliasmate run build

View All Commands

See all your saved commands with their directories and details.

aliasmate list

💡 Alias: Use 'aliasmate ls' for quick listing

Example

$ aliasmate list

Find Commands Fast

Search through names, commands, or directories to find what you need.

aliasmate search <query>

💡 Alias: Use 'aliasmate find deploy' as a shortcut

Example

$ aliasmate search deploy

Update Commands

Modify the command, directory, or path mode interactively.

aliasmate edit <name>

💡 Current values are shown as defaults for easy editing

Example

$ aliasmate edit build

Share with Your Team

Export commands to JSON for backup or sharing. Import to load commands.

aliasmate export/import

💡 Version control your exports for team-wide consistency

Example

$ aliasmate export team.json

Quick Start Workflow

1.

# Run your command

npm run build:production

2.

# Save it instantly

aliasmate prev build-prod

3.

# Run from anywhere, anytime

aliasmate run build-prod

Core Features

Powerful capabilities designed for developers

Path Mode Intelligence

Each command can run in its saved directory or your current directory

  • ▸Saved mode: Always runs in the original directory
  • ▸Current mode: Runs wherever you are now
  • ▸Perfect for project-specific vs general utilities

Persistent Storage

All commands stored in ~/.config/aliasmate/config.json

  • ▸Survives terminal restarts and system reboots
  • ▸JSON format for easy manual editing if needed
  • ▸Includes metadata: creation date, last modified

Complex Command Support

Save and execute multi-line scripts and pipelines

  • ▸Support for pipes, redirects, and chains
  • ▸Environment variables preserved
  • ▸Works with any shell command or script

Team Collaboration

Export and import command sets for seamless sharing

  • ▸Export to version-controlled JSON files
  • ▸Import prompts before overwriting
  • ▸Perfect for onboarding and standardization

Command Structure

{
  "build-prod": {
    "command": "npm run build:production",
    "directory": "/Users/dev/my-project",
    "pathMode": "saved",
    "createdAt": "2026-01-12T10:30:00Z",
    "updatedAt": "2026-01-12T10:30:00Z"
  }
}

Clean JSON structure makes manual editing and version control easy

Use Cases

See how AliasMate fits into your workflow

Frontend Development

Manage dev servers, builds, and tests across multiple projects

dev→
npm run dev

Start development server

build→
npm run build

Production build

test→
npm test -- --coverage

Run tests with coverage

Backend & APIs

Server management, database operations, and migrations

api→
npm start

Start API server

migrate→
npm run migrate:latest

Run database migrations

seed→
npm run seed:dev

Seed development data

DevOps & Deployment

Deployment scripts, monitoring, and infrastructure commands

deploy-prod→
./scripts/deploy.sh production

Deploy to production

logs→
tail -f /var/log/app.log

Stream application logs

health→
curl http://localhost:3000/health

Check service health

Multi-Project Workflows

Switch between projects and run context-specific commands

api-test→
npm test

Test API project

web-dev→
npm run dev

Start web frontend

mobile-build→
expo build:ios

Build mobile app

🚀

Startup Teams

Move fast with standardized commands across the team

🏢

Enterprise

Maintain consistency across large, distributed teams

👨‍💻

Solo Developers

Boost personal productivity and reduce context switching

Hacks & Pro Tips

Level up your AliasMate game with these expert strategies

Naming Conventions

Use prefixes for grouping

Organize commands with consistent prefixes like 'test-', 'deploy-', 'db-'

test-unit, test-integration, test-e2e

Environment suffixes

Add environment indicators to deployment commands

deploy-dev, deploy-staging, deploy-prod

Action-first naming

Start with the action verb for better searchability

build-frontend, start-api, clean-cache

Workflow Optimization

Chain related commands

Save complex pipelines as single commands with proper error handling

npm run build && npm run test && npm run deploy

Use path mode strategically

'saved' for project-specific, 'current' for generic utilities

build commands → saved, git helpers → current

Backup regularly

Create automated backups with date stamps

aliasmate export ~/backups/aliases-$(date +%Y%m%d).json

Power User Tips

Combine with shell aliases

Create ultra-short shell aliases for your most-used AliasMate commands

alias amr='aliasmate run' → amr build

Version control your exports

Keep team command sets in git for easy distribution and updates

git/team-commands.json → aliasmate import team-commands.json

Document complex commands

Use descriptive names that explain what the command does

'rebuild-docker-clear-cache' > 'rdc'

Advanced Techniques

Environment-specific commands

Save commands with environment variables for different contexts

NODE_ENV=production npm start

Conditional execution

Use && and || for smart command chaining

npm run lint && npm test || echo 'Failed'

Interactive commands

Save commands that prompt for input during execution

npm run deploy -- --interactive

Quick Pro Tips

💡 After saving a command, test it immediately with 'aliasmate run' to verify

💡 Use 'aliasmate search' instead of 'list' when you have many commands

💡 Export your commands monthly as a safety net against config corruption

💡 Team leads: Create a starter pack export for new developers

💡 Prefix debugging commands with 'debug-' for easy identification

💡 Save git worktree commands to quickly switch between feature branches

🎯 Real-World Hack: The 5-Second Rule

If you`ve typed a command more than twice in a day, it deserves an alias. Train yourself to save immediately—your future self will thank you.

$ docker-compose up -d && docker logs -f my-app
$ aliasmate prev docker-dev
# Next time, just:
$ aliasmate run docker-dev

Get Started

Install AliasMate and start saving time in under a minute

Installation

npm (recommended)

npm install -g aliasmate

yarn

yarn global add aliasmate

pnpm

pnpm add -g aliasmate

First Steps

# 1. Verify installation

$ aliasmate --version
1.3.1

# 2. Save your first command

$ npm run dev
$ aliasmate prev dev
✓ Command `dev` saved successfully

# 3. Run it from anywhere

$ cd ~/anywhere
$ aliasmate run dev
Running: npm run dev

GitHub Repository

View source, report issues, contribute

Full Documentation

Complete API reference and guides

Requirements

🖥️

Cross Platform

Linux, macOS, Windows

⚡

Node.js

Version 14.0.0 or higher

🎯

TypeScript

Built with TypeScript

Ready to supercharge your terminal workflow?

npm install -g aliasmate