Generate Personal Shell Aliases for Your Repetitive Commands
If you find yourself typing the same long commands over and over, you should have aliases for them. But writing aliases is one of those things that never quite makes it to the top of the to-do list. Let Claude batch them up for you.
Here are the commands I type most often. Write shell aliases for all of them,
use sensible short names, and add a comment explaining each one:
- git status
- git diff --staged
- php artisan migrate
- php artisan migrate:fresh --seed
- docker compose up -d
- docker compose down
- npm run dev
- cd ~/Projects/myapp
Claude will produce a clean block of aliases ready to paste into your .zshrc or .bashrc:
alias gs='git status'
alias gds='git diff --staged'
alias mig='php artisan migrate'
alias migf='php artisan migrate:fresh --seed' # Full reset with seeding
alias dcu='docker compose up -d'
alias dcd='docker compose down'
alias dev='npm run dev'
alias myapp='cd ~/Projects/myapp'
You can go further and ask for shell functions for anything that needs arguments:
I often run `git log --oneline -N` where N is a number I vary. Write a shell
function that accepts a number and defaults to 10.
Claude will write the function, handle the default, and explain how to add it.
The best alias is the one you actually use — let Claude figure out the names.
Log in to leave a comment.
Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.
Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.
Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.