Git Workflow And Versioning
Use when making code changes that should stay atomic, reversible and easy to review through disciplined Git workflow and versioning.
Install
$ agentstack add skill-mmccalla-coding-agent-skill-library-git-workflow-and-versioning ✓ 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-mmccalla-coding-agent-skill-library-git-workflow-and-versioning) 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 Workflow and Versioning
When to use
Use this skill when creating commits, branching work, preparing changes for review, or planning version-aware changes and migrations.
Objective
Keep change history small, coherent and easy to understand while preserving the ability to revert or bisect if needed.
Procedure
- Keep each commit or change slice focused on one logical purpose.
- Avoid mixing unrelated fixes, refactors and documentation changes.
- Use descriptive commit messages or change notes.
- Preserve a clean working tree before handing off work.
- Treat versioned or compatibility-sensitive changes deliberately.
Rules
- Do not rewrite shared history unless explicitly authorised.
- Do not combine unrelated changes just to reduce the number of commits.
- Do not hide partial work in ambiguous commit messages.
- Do not change versioning semantics without checking downstream impact.
Example
For a phased refactor, branch from updated main, commit one phase at a time, run validation before hand-off and merge only after approval. If a hook rewrites files, review the resulting diff before committing. Prefer a clear revertable commit over a broad mixed commit that hides documentation, tests and implementation together.
References
Verification
- [ ] Logical change boundaries described.
- [ ] Working tree state reported.
- [ ] Versioning or compatibility considerations noted.
- [ ] Reversibility of the change confirmed.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: mmccalla
- Source: mmccalla/coding-agent-skill-library
- License: Apache-2.0
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.