Dev10x:git-alias-setup

Configure git aliases to wrap subshell commands into stable prefixes.

7|2|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/Dev10x-Guru/Dev10x-Claude --skill dev10x-git-alias-setup-dev10x-guru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Dev10x:git-alias-setup
Source: https://github.com/Dev10x-Guru/Dev10x-Claude/tree/main/skills/git-alias-setup
Command: npx skills add https://github.com/Dev10x-Guru/Dev10x-Claude --skill dev10x-git-alias-setup-dev10x-guru

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the issue of unnecessary permission prompts when using $(git merge-base ...) subshells in git commands, by setting up git aliases to wrap these subshells into stable command prefixes.

Core Features & Use Cases

  • Git Alias Configuration: Sets up global git aliases to avoid extra permission prompts and enhance productivity.
  • Branch Comparison Aliases: Provides branch comparison aliases ({base}-log, {base}-diff, {base}-rebase) and a non-interactive autosquash alias (autosquash-{base}).
  • Non-Paging/Non-Color Reads: Offers git nopager and git nocolor aliases for non-paging and non-color reads.

Quick Start

Run the setup script to configure git aliases:

${CLAUDE_PLUGIN_ROOT}/skills/git-alias-setup/scripts/git-alias-setup.sh

Frequently Asked Questions about Dev10x:git-alias-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does git ask for permission when running subshell commands like git merge-base?

Git subshell commands trigger permission prompts because the shell execution breaks stable command prefixes. Setting up git aliases wraps these subshells into stable prefixes to eliminate the permission friction.

How do I configure git aliases for branch comparison without manual setup?

Run the setup script to configure global git aliases for branch comparison. This automatically provides log, diff, and rebase aliases alongside a non-interactive autosquash alias for your workflow.

Can I get non-paging and non-color git output using aliases?

Yes, you can use the git nopager and git nocolor aliases for non-paging and non-color reads. These aliases are configured globally to provide clean terminal output without interactive paging.

Do I need additional tools to set up these git aliases?

No additional tools are required beyond the git command line. The setup script configures the aliases directly within your global git configuration to avoid permission prompts.

What is the best way to avoid permission prompts in git subshell workflows?

The best way to avoid permission prompts is by setting up git aliases that wrap subshell commands into stable command prefixes. This targets the root cause of the permission friction in git workflows.