Git workflow

Skill subhansh-dev/agent-maxxing/workflows/git-workflow

95+ agent skills, 19 UI components, 7 system prompts from Claude Fable 5, GPT-5.5, Gemini CLI & more. Self-fine-tune your agent: paste one prompt and it reads every skill, internalizes patterns, and becomes elite. Works with Claude Code, Codex, Cursor, OpenCode + 60 more agents.

Install

npx -y skills add subhansh-dev/agent-maxxing --skill git-workflow

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

29 days oldThe repository was created 29 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Git workflow patterns — commit messages, branching, PR workflow, and conflict resolution.

SKILL.md

1.8 KB, 467 tokens by cl100k_base, as published. Nobody here has run it

Git Workflow — How to Use Git Properly

Commit Messages

Format: <type>(<scope>): <description>

Types:

feat — new feature
fix — bug fix
refactor — code restructuring without behavior change
style — formatting, no code change
docs — documentation only
test — adding or updating tests
chore — maintenance tasks
perf — performance improvement

Examples:

feat(auth): add OAuth2 login flow
fix(api): handle null response from payment gateway
refactor(parser): extract validation into separate module
perf(db): add index for user lookup query

Rules:

Subject line: imperative mood, no period, max 72 chars
Body: explain WHAT and WHY, not HOW (the code shows HOW)
Reference issues: Closes #123, Fixes #456

Branching

main — always deployable
feat/<name> — new features
fix/<name> — bug fixes
refactor/<name> — refactoring
chore/<name> — maintenance

Create branch from main, merge back via PR.

PR Workflow

Create branch from main
Make changes, commit incrementally
Push branch
Create PR with description
Request review
Address feedback
Merge (squash for clean history)

Conflict Resolution

git fetch origin
git rebase origin/main
Fix conflicts in files
git add <resolved-files>
git rebase --continue
git push --force-with-lease

Never merge main into your branch — rebase instead.

Interactive Rebase

Clean up commits before PR:

git rebase -i HEAD~5
# squash, reword, edit commits
git push --force-with-lease

Stashing

git stash push -m "WIP: login form"
git stash list
git stash pop

Stash before switching branches. Pop when you return.