git-workflow
Git best practices, branching strategies, commit conventions, and code review patterns
Profile →npx skills add cosmicstack-labs/mercury-agent-skills --skill git-workflow --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Git Workflow Master the fundamentals of version control collaboration — from branching strategy to commit hygiene to review culture. ## Core Principles ### 1. Commits Are Communication Every commit message is a message to your future self and your teammates. Write for the reader who needs to understand *why* a change was made, not just *what* changed. ### 2. Branch Intentionally Your branching strategy should match your team size, release cadence, and deployment model. The best strategy is the one your team actually follows consistently. ### 3. Review With Empathy Code review is a conversation, not an inspection. The goal is shared understanding and improved quality, not catching mistakes. ### 4. Rebase Thoughtfully History matters. Clean history helps debugging and release management. But never rebase shared branches without team coordination. --- ## Git Workflow Maturity Model | Level | Branching | Commits | Reviews | CI | |-------|-----------|---------|---------|-----| | **1: Ad-hoc** | All on main | "Update" messages | None | None | | **2: Basic** | Feature branches | Some context in messages | Occasional | Lint checks | | **3: Standard** | Trunk-based or GitFlow | Convention
- Core Principles
- 1. Commits Are Communication
- 2. Branch Intentionally
- 3. Review With Empathy
- 4. Rebase Thoughtfully
- Git Workflow Maturity Model
- Actionable Guidance
- Branching Strategies
- Commit Conventions
- Code Review Patterns
- Git Hygiene
- Common Mistakes
Implements Google and GitHub OAuth providers. Closes #142 BREAKING CHANGE: Drops support for password-based auth Stage related changes only git add -p # Interactive staging — commit only what's relevant Review your diff before committing git diff --staged Write the commit message first, then commit git commit # Opens editor — write a good message Rebase on latest main
What does the git-workflow skill do?
Git best practices, branching strategies, commit conventions, and code review patterns
How do I install it?
Run `npx skills add cosmicstack-labs/mercury-agent-skills --skill git-workflow --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From cosmicstack-labs/mercury-agent-skills, a repository with 364 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.