git-workflow

Use when committing, branching, splitting changes, managing stacks, creating worktrees, or cleaning up branches — detects Graphite or Git and guides the agent through best-practice workflows via CLI.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "git-workflow" with this command: npx skills add hjewkes/agent-skills/hjewkes-agent-skills-git-workflow

Git Workflow

Unified git workflow skill. Detects Graphite (gt) or plain Git, prefers Graphite when available.

First step in any git operation: Run scripts/git-workflow status to detect the environment.

Quick Reference

SituationAction
Need repo state / tool detectiongit-workflow status
Ready to commit staged changesgit-workflow commit --message "feat: ..."
Large diff needs decompositionRead references/splitting-changes.md, then git-workflow split
View or manage branch stackgit-workflow stack
Need isolated workspacegit-workflow worktree --branch feat/name
Stale local branchesgit-workflow clean
Graphite command referencereferences/graphite-guide.md
Commit/branch conventionsreferences/git-best-practices.md

CLI Reference

CommandDescription
git-workflow statusDetect gt/git, report branch, dirty files, stack state
git-workflow commitGuided commit (conventional format, gt create or git commit)
git-workflow splitAnalyze diff, suggest split points, guide decomposition
git-workflow stackShow stack state, create/restack/sync branches
git-workflow worktreeCreate isolated worktree with dep install + test baseline
git-workflow cleanRemove merged/gone branches and associated worktrees

Workflow Integration

WorkflowUsage
Feature developmentstatus → work → commitstack (if stacking)
Large change decompositionstatus → read splitting-changes.md → split
Parallel agent workworktree → work in isolation → finish
Post-merge cleanupclean to remove stale branches
PR creationUse github-pr skill after committing/pushing

Safety Guardrails

  • Never git push --force to main/master
  • Never git add . or git add -A (stage specific files)
  • Never skip hooks with --no-verify
  • Never git reset --hard without explicit user instruction
  • Always verify staged files before committing

Reference Files

ReferencePurpose
references/graphite-guide.mdGraphite commands, stacking patterns, pitfalls
references/git-best-practices.mdCommit format, branch naming, safety rules
references/splitting-changes.mdStrategies for decomposing large diffs

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

github-pr

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

code-review

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

subagent-driven-development

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

test-driven-development

No summary provided by upstream source.

Repository SourceNeeds Review