compuse-git

Diagnose and prevent common git pitfalls in commits, pushes, hooks, and multi-repo workflows.

1|Updated Jun 23, 2026
One-click install
npx skills add https://github.com/bitranox/bitranox-skills --skill compuse-git-bitranox
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: compuse-git
Source: https://github.com/bitranox/bitranox-skills/tree/main/plugins/bitranox/skills/compuse-git
Command: npx skills add https://github.com/bitranox/bitranox-skills --skill compuse-git-bitranox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Git commands fail in confusing, silent, or destructive ways: rev-parse --short rejects multiple revisions, chmod +x is ignored when core.fileMode=false, CRLF line endings break scripts, and shared checkouts let commits land on the wrong branch. This Skill provides a quick-reference table and in-depth sections covering these failure modes so an agent avoids them or diagnoses them deterministically. ## Core Features & Use Cases - Quick-reference table of git footguns: Covers rev-parse pitfalls, rerere stale resolutions, merge-tree --write-tree trial merges, checkout -- discarding uncommitted work, exec-bit handling, line endings, interactive flags, and multi-key --sort ordering. - Safe commit and push procedures: Chain quality gates with &&, commit only your own paths when sessions share a checkout, review the full push range for leaked secrets, and use .git/info/exclude for private tooling on forks. - CI and hook guidance: Configure read-only PATs with URL rewrites for private git dependencies in CI, and clear GIT_DIR in hooks triggered from linked worktrees. - Use Case: Before pushing a release, run the pre-push review to scan git diff @{push}..HEAD for credentials, verify the branch and upstream sync state, and confirm hooks are committed with mode 100755. ## Quick Start Ask the agent to check why a committed shell hook is not executable after cloning, or to verify the current repo state before committing.

Frequently Asked Questions about compuse-git

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

FAQPage Schema
Why is my committed git hook not executable after cloning?▼

When core.fileMode=false, git ignores chmod +x, so the file is committed as 100644 and clones non-executable. Fix it with git update-index --chmod=+x <file> and verify git ls-files -s shows 100755.

How do I check if a git ref exists without false positives?▼

Use git rev-parse --verify -q <ref>, which prints nothing and exits non-zero for a missing ref. A plain git rev-parse echoes the name back on stdout, so capturing it in a variable makes an equality test report a confident false result.

How can I test whether a branch still merges cleanly without touching my checkout?▼

Use git merge-tree --write-tree <base> <branch> (git 2.38+). It writes the merge into the object store, prints the merged tree sha, and exits non-zero listing conflicted paths, with no ref, index, or working-tree changes.

Why does my bash script fail with bad interpreter after committing on Windows?▼

The script was committed with CRLF line endings, so the shebang reads as /usr/bin/env bash\r. Pin LF with .gitattributes entries like *.sh text eol=lf, since a Windows checkout or core.autocrlf=true reintroduces CRLF.

How do I commit safely when multiple agents share one git checkout?▼

Verify git branch --show-current and ahead/behind state with git rev-list --left-right --count HEAD...@{upstream}, then commit only your paths via git commit -m "msg" -- <paths>. Never use git add -A; a per-session git worktree is the durable fix.

How do I fix private git dependencies failing in CI with could not read Username?▼

The CI runner lacks read access to the other private repos. Add a read-only PAT as a secret and configure a url.insteadOf rewrite to https://<token>@github.com/<Org>/, loading the token from a file via stdin so it never appears in argv or logs.