AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Git Workflow

skill-arozumenko-sdlc-skills-git-workflow · by arozumenko

Use when the user asks to "commit", "create PR", "branch", "merge", "rebase", "cherry-pick", "tag", or otherwise manage git history. Guides disciplined git operations — branching, commits, PRs, and recovery.

↗ Repository
— No reviews yet
0 installs
18 views
0.0% view→install

Install

$ agentstack add skill-arozumenko-sdlc-skills-git-workflow

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No 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.

Are you the author of Git Workflow? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Git Workflow

Disciplined git operations for professional codebases.

Platform & systems

Commands below use GitHub gh as the reference. Translate to your code host per .agents/workflow.md § Git host — GitLab glab, Bitbucket bb, Azure DevOps az repos, Gitea tea. "PR" means PR or MR. If scout hasn't recorded a host, ask before assuming GitHub.

Before Any Git Operation

git --no-pager status
git --no-pager log --oneline -5
git --no-pager diff --stat

Always know the current state before changing it.

Branching

# Feature branch from main
git checkout main && git pull && git checkout -b feat/short-description

# Bug fix
git checkout main && git pull && git checkout -b fix/issue-description

Branch naming: feat/, fix/, chore/, docs/ prefixes. Lowercase, hyphens, concise.

Commits

Never commit unless the user explicitly asks. When they do:

  1. Stage specific files (not git add -A — avoid secrets and binaries)
  2. Write a message that explains why, not what
  3. Keep commits focused — one concern per commit
git add src/auth.py src/middleware.py
git commit -m "$(cat 
EOF
)"

Pull Requests

When asked to create a PR:

  1. Check all commits since divergence: git --no-pager log main..HEAD --oneline
  2. Review full diff: git --no-pager diff main...HEAD
  3. Push with tracking: git push -u origin HEAD
  4. Create with structured body:
gh pr create --title "Short title under 70 chars" --body "$(cat <<'EOF'
## Summary
- What changed and why (2-3 bullets)

## Test plan
- [ ] How to verify this works

Generated with Claude Code
EOF
)"

Dangerous Operations

Always confirm with the user before:

  • git push --force (any variant)
  • git reset --hard
  • git branch -D
  • git rebase on shared branches
  • git checkout . or git restore . (discards work)

Never:

  • Skip hooks (--no-verify)
  • Force push to main/master
  • Amend published commits
  • Use interactive flags (-i) — not supported in non-interactive shells

Recovery

See references/recovery.md for common recovery scenarios.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

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.

More in Agent Skills