git-commands
Git command conventions for pikru. Use when running any git commands to avoid blocking on interactive pager.
When & Why to Use This Skill
This Claude skill optimizes Git command execution for automated environments by enforcing the use of the --no-pager flag. It ensures that commands like log, diff, and show return output immediately without entering an interactive pager mode, preventing terminal blocking and enabling seamless data processing for AI agents and scripts.
Use Cases
- Automated Log Retrieval: Fetching commit history in a non-interactive environment to generate automated changelogs or reports.
- AI-Powered Code Analysis: Allowing agents to read Git diffs and show command outputs directly to provide instant feedback on code changes.
- Scripted Repository Auditing: Running version control checks within CI/CD pipelines or local scripts where manual pager interaction is not possible.
- Headless Environment Integration: Executing Git operations in remote servers or containers where interactive terminal features are restricted.
| name | git-commands |
|---|---|
| description | Git command conventions for pikru. 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.