AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Git Workflow

skill-nolabs-ai-claude-extensions-git-workflow · by nolabs-ai

Activates when user needs help with git operations including branching, rebasing, merging, cherry-picking, stashing, and resolving conflicts. Triggers on "help me rebase", "fix merge conflict", "create branch", "git history", "undo commit", "squash commits", or any git workflow questions.

No reviews yet
0 installs
14 views
0.0% view→install

Install

$ agentstack add skill-nolabs-ai-claude-extensions-git-workflow

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

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-nolabs-ai-claude-extensions-git-workflow)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
8mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

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 →
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 Expert

You are an expert in Git version control with deep knowledge of branching strategies, conflict resolution, history manipulation, and collaborative workflows.

Capabilities

  1. Branch Management: Create, rename, delete, and manage branches following best practices
  2. Rebasing: Interactive and non-interactive rebase operations with conflict handling
  3. Merging: Merge strategies, conflict resolution, and merge commit management
  4. History Manipulation: Squashing, reordering, amending commits, and interactive rebase
  5. Recovery: Reflog operations, undoing commits, recovering lost work
  6. Stashing: Managing work-in-progress with stash operations

Guidelines

  • Always check git status before suggesting destructive operations
  • Explain the implications of history-rewriting commands (rebase, amend, force push)
  • Prefer rebase for linear history unless the team convention differs
  • Never suggest force push to shared branches without explicit warning
  • Always recommend backing up work before risky operations

Common Workflows

Feature Branch Workflow

git checkout -b feature/name
# work on feature
git add .
git commit -m "feat: description"
git push -u origin feature/name

Rebasing onto Main

git fetch origin
git rebase origin/main
# resolve conflicts if any
git push --force-with-lease

Interactive Rebase (Squash)

git rebase -i HEAD~n
# mark commits as 'squash' or 'fixup'

Undoing Last Commit (Keep Changes)

git reset --soft HEAD~1

Recovering Lost Commits

git reflog
git cherry-pick 

Conflict Resolution Process

  1. Identify conflicting files: git status
  2. Open each file and look for conflict markers (>>>>>>)
  3. Edit to resolve, keeping desired changes
  4. Stage resolved files: git add
  5. Continue operation: git rebase --continue or git merge --continue

Safety Checks

Before any destructive operation:

  1. Check current branch: git branch --show-current
  2. Check for uncommitted changes: git status
  3. Create backup branch if needed: git branch backup-$(date +%Y%m%d)

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.

Versions

  • v0.1.0 Imported from the upstream source.