Skill

bash-aliases

Install
1
Install the plugin
$
npx claudepluginhub melodic-software/claude-code-plugins --plugin git

Want just this skill?

Add to a custom plugin, then install with one command.

Description

Manage git and Claude Code bash aliases. Run without flags for interactive wizard.

Tool Access

This skill is limited to using the following tools:

BashReadWriteGlobGrepAskUserQuestion
Skill Content

Bash Aliases Management

Manage git shortcuts (g, gco, gb, etc.) and Claude Code aliases (claude-yolo, claude-cont, etc.) with bash tab completion.

Usage

/git:bash-aliases                # Interactive setup wizard
/git:bash-aliases --setup        # Same as above
/git:bash-aliases --status       # Check installation status
/git:bash-aliases --audit        # Comprehensive health check
/git:bash-aliases --uninstall    # Show uninstall instructions

Workflow

Step 1: Parse Arguments

Parse $ARGUMENTS to determine operation mode:

  • No arguments or --setup -> Interactive mode (Step 2)
  • Direct flag (--status, --audit, --uninstall) -> Direct mode (Step 3)

Step 2: Interactive Mode (no flag or --setup)

Use AskUserQuestion to let user select alias sets:

Use AskUserQuestion with:
- question: "Which bash aliases do you want to install?"
- header: "Alias Sets"
- multiSelect: true
- options:
  1. "Git aliases" - "Shortcuts (g, gco, gb, gm, etc.) with tab completion"
  2. "Claude aliases" - "Claude Code shortcuts (claude-yolo, claude-cont, etc.)"

Based on user selections, execute corresponding script operations:

  • Git aliases selected -> Run script with --install-git-aliases
  • Claude aliases selected -> Run script with --install-claude-aliases

Report aggregate results.

Step 3: Direct Mode

Execute the script with the specified flag:

FlagScript Operation
--status--status
--audit--audit
--uninstall--uninstall

Step 4: Report Results

Show operation results to user. Include next steps if applicable:

  • After install: "Run source ~/.bashrc or restart your shell"
  • For audit warnings: Suggest remediation

Script Location

The underlying bash script is at:

plugins/git/skills/setup/scripts/bash-aliases.sh

Execute using:

bash "plugins/git/skills/setup/scripts/bash-aliases.sh" <operation>

Alias Sets

Git Aliases

Common shortcuts with tab completion:

AliasCommand
ggit
gsgit status
gcogit checkout
gbgit branch
gmgit merge
gpgit pull
gpsgit push
gdgit diff
glgit log --oneline --graph --decorate
gstgit stash
gagit add
gcmgit commit
grgit rebase
gcpgit cherry-pick

Claude Code Aliases

AliasCommand
claude-contclaude -c
claude-cont-yoloclaude -c --dangerously-skip-permissions
claude-yoloclaude --dangerously-skip-permissions
claude-planclaude --permission-mode plan
claude-opusclaude --model opus
claude-sonnetclaude --model sonnet
claude-opus-yoloclaude --model opus --dangerously-skip-permissions
claude-headlessclaude -p --output-format json

Examples

Interactive Setup

/git:bash-aliases
-> "Which bash aliases do you want to install?"
  [x] Git aliases
  [x] Claude aliases
-> Installing selected alias sets...
-> Done! Run: source ~/.bashrc

Check Status

/git:bash-aliases --status

Bash Aliases Status
-------------------

Git Aliases:
[OK] Configured in ~/.bashrc
    Aliases: g, gs, gco, gb, gm, gp, gps, gd, gl, gst, ga, gcm, gr, gcp

Claude Code Aliases:
[OK] Configured in ~/.bashrc
    Aliases: claude-cont, claude-yolo, claude-plan, claude-opus, claude-sonnet

Audit

/git:bash-aliases --audit

Bash Aliases Audit Report
=========================
[OK] Git aliases: PASS - Configured
[OK] git-completion.bash: PASS - Found
[OK] Claude aliases: PASS - Configured
[OK] claude CLI: PASS - Found

Overall: PASS

Notes

  • Aliases are added to ~/.bashrc with idempotent markers
  • Git aliases include tab completion via git-completion.bash
  • Safe to run multiple times (won't duplicate entries)
  • Requires source ~/.bashrc or new shell to take effect
Stats
Stars40
Forks6
Last CommitFeb 15, 2026
Actions

Similar Skills

cache-components

Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.

138.4k