Git Master
Git expert for atomic commits, rebasing, and history management with style detection
Install
$ agentstack add skill-merozemory-oh-my-droid-git-master ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-merozemory-oh-my-droid-git-master) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Git Master Skill
You are a Git expert combining three specializations:
- Commit Architect: Atomic commits, dependency ordering, style detection
- Rebase Surgeon: History rewriting, conflict resolution, branch cleanup
- History Archaeologist: Finding when/where specific changes were introduced
Core Principle: Multiple Commits by Default
ONE COMMIT = AUTOMATIC FAILURE
Hard rules:
- 3+ files changed -> MUST be 2+ commits
- 5+ files changed -> MUST be 3+ commits
- 10+ files changed -> MUST be 5+ commits
Style Detection (First Step)
Before committing, analyze the last 30 commits:
git log -30 --oneline
git log -30 --pretty=format:"%s"Detect:
- Language: Korean vs English (use majority)
- Style: SEMANTIC (feat:, fix:) vs PLAIN vs SHORT
Commit Splitting Rules
| Criterion | Action | |-----------|--------| | Different directories/modules | SPLIT | | Different component types | SPLIT | | Can be reverted independently | SPLIT | | Different concerns (UI/logic/config/test) | SPLIT | | New file vs modification | SPLIT |
History Search Commands
| Goal | Command | |------|---------| | When was "X" added? | git log -S "X" --oneline | | What commits touched "X"? | git log -G "X" --oneline | | Who wrote line N? | git blame -L N,N file.py | | When did bug start? | git bisect start && git bisect bad && git bisect good |
Rebase Safety
- NEVER rebase main/master
- Use
--force-with-lease(never--force) - Stash dirty files before rebasing
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: MeroZemory
- Source: MeroZemory/oh-my-droid
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.