git-commands

Git command conventions. Use when running any git commands to avoid blocking on interactive pager.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 3, 2026

When & Why to Use This Skill

This Claude skill optimizes Git command execution for AI agents by enforcing the use of the '--no-pager' flag. It ensures that terminal operations remain non-blocking, preventing the agent from getting stuck in interactive pagers during tasks like viewing logs, diffs, or commit history. By standardizing command conventions, it streamlines automated version control workflows and improves the reliability of terminal-based interactions.

Use Cases

  • Automated Log Review: Efficiently retrieving and analyzing commit history without manual terminal intervention.
  • Non-blocking Code Diffs: Comparing file changes during debugging or code reviews without triggering interactive UI elements.
  • Repository Inspection: Quickly displaying branch details, object information, or status reports in a clean, text-only format.
  • CI/CD and Scripting: Ensuring Git commands run smoothly in automated environments where interactive input is not possible.
namegit-commands
descriptionGit command conventions. Use when running any git commands to avoid blocking on interactive pager.

Git Commands

Always use --no-pager BEFORE the git command to avoid blocking on interactive pager:

git --no-pager log -10
git --no-pager diff
git --no-pager show

The --no-pager flag must come before the subcommand (log, diff, show, etc.), not after.