cli

Standardize Bash CLI navigation and Git commands with long-form flags.

14|4|Updated Oct 20, 2025
One-click install
npx skills add https://github.com/motlin/claude-code-plugins --skill cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cli
Source: https://github.com/motlin/claude-code-plugins/tree/main/plugins/code/skills/cli
Command: npx skills add https://github.com/motlin/claude-code-plugins --skill cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inefficient or inconsistent command-line usage, such as unnecessary cd commands or short flag names, can slow down development workflows and make scripts harder to read. This Skill streamlines your terminal interactions.

Core Features & Use Cases

  • Efficient Navigation: Advises against unnecessary cd commands, preferring git -C <dir> <subcommand> for directory-specific operations.
  • zoxide Integration: Notes the replacement of cd with zoxide and the need to prefix cd with command when explicitly required.
  • Long Flag Names: Promotes the use of long flag names (e.g., --message instead of -m) for improved readability and clarity in commands.
  • Use Case: When interacting with the terminal, let the AI automatically refactor your commands to adhere to these best practices, ensuring efficient, clear, and consistent command execution, especially for Git operations.

Quick Start

Refactor the following command to use best practices: cd my-project && git commit -m 'feat: add new feature'

Frequently Asked Questions about cli

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

FAQPage Schema
How do I optimize my Git workflow to avoid unnecessary directory changes?

Use `git -C <dir> <subcommand>` to scope Git commands to specific directories without changing your current location. This eliminates redundant `cd` commands and keeps your working directory stable, improving script readability and reducing navigation overhead.

Should I replace cd with zoxide for command-line navigation?

Zoxide replaces `cd` with smarter directory jumping based on frecency. When you need explicit `cd` behavior, prefix it with `command cd` to bypass zoxide. This hybrid approach balances efficiency with control over your navigation.

Why should I use long-form flag names in terminal commands?

Long flags like `--message` instead of `-m` improve command clarity and maintainability, especially in scripts and shared workflows. They make intent explicit and reduce errors from flag confusion, enhancing team communication and debugging.

What's the best way to standardize command-line practices across my development workflow?

Standardize by prefixing only `cd` with `command`, avoiding prefix for Git commands, minimizing directory changes, and using descriptive long-form flags. This creates consistent, readable terminal interactions that scale across scripts and team collaboration.

Can I apply command-line optimization to existing Bash scripts?

Yes. Refactor scripts by replacing `cd && git` patterns with `git -C`, adopting zoxide for navigation, and converting short flags to long-form equivalents. These changes improve readability and execution efficiency without altering script logic.