git-workflow-standards
/git-workflow-standards
Use for branch hygiene, merge conflict resolution, and worktree cleanup.
- Author
- dryvist ↗
- Repository
- claude-code-plugins ↗
- Licence
- Apache-2.0
- Last repository change
- 25.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Use for branch hygiene, merge conflict resolution, and worktree cleanup.
Original author description
Use for branch hygiene, merge conflict resolution, and worktree cleanup.
How it works
- Branch Hygiene
- Merge Conflict Resolution
- Related Skills
SKILL.md preview
--- name: git-workflow-standards description: Use for branch hygiene, merge conflict resolution, and worktree cleanup. --- # Git Workflow Standards For branch creation and PR-branch sync, follow the [Git Town rule](https://github.com/dryvist/ai-llm-prompts/blob/main/auto-ai-agent/instructions/agentsmd/rules/on-demand/git-flow.md). Every branch with commits MUST have an associated PR. Orphaned branches must get a PR or be deleted. **Stale branch** (worktree-paired, bare local, or remote-only — see `prune-branches`, github-workflows, for the full procedure): a non-default branch, checked out nowhere, unreferenced by any open PR (`--head` or `--base`), with no uncommitted changes (when a worktree exists), and either a merged PR whose `headRefOid` matches the branch tip, or zero commits ahead of the default branch. Use `git worktree remove` (never `--force`) for worktree-paired branches — Git blocks removal of dirty worktrees — and `git push origin --delete` for a live remote ref, only after `prune-branches`'s pre-push ancestry re-check. ## Branch Hygiene - Use conventional-commit prefixes without emoji (see `pr-standards`). ## Merge Conflict Resolution **NEVER assume newer is correct.** Analyze both versions. 1. **Understand** — read full file, check `git log --oneline -10 -- <file>` 2. **Analyze** — identify what each side changed and why, check compatibility 3. **Resolve** — use the resolution table below 4. **Verify** — run `pre-commit run --files <file>`, read resolved file | Scenario | Resolution | | --- | --- | | Additive changes | Keep both | | Same logic modified | Combine intent of both | | One is a bug fix | Always include the fix | | One is a refactor | Apply refactor, then add other change | | Truly incompatible | Prefer branch's changes, add comment | Escalate to human review for complex business logic, fundamental contradictions, or security-sensitive code. | Command | Purpose | | --- | --- | | `git diff --name-only --diff-filter=U` | List conflicted files | | `git log --merge -p <file>` | Show commits causing conflict | | `git show :1:<file>` | Common ancestor version | | `git show :2:<file>` | HEAD (your branch) version | | `git show :3:<file>` | Incoming (their branch) version | | `git merge --abort` | Abort and return to pre-merge state | ## Related Skills - **refresh-repo** (github-workflows) — PR readiness and local default-branch fast-forward - **prune-branches** (github-workflows) — Stale branch and worktree cleanup - **pr-stacks** (github-workflows) — PR stack submission and merge tracking - **gh-cli-patterns** (github-workflows) — Canonical default-branch detection (trunk vs git-flow) - **pr-standards** (github-workflows) — PR creation guards, issue linking, and review standards
Versions
The database has no other skills named git-workflow-standards.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 1147c311446a (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 80vc:merge-worktree
Merge a git worktree branch back into the main Flowser checkout and clean up the worktree. Use when the user asks to merge, archive, or clean up a completed worktree. - 100merge-conflict-resolution
Detect, classify, and resolve git merge conflicts through structured analysis of conflict markers, per-file strategy selection, and post-resolution verification. Use when a branch has conflicts with its merge target, when rebasing onto an updated base, or when gh-merge detects an unmergeable PR. - 90git-cleanup
Use when a git worktree is dirty or another local branch or worktree exists. Ask before cleanup unless the session is unattended. - 90git-worktree-manager
Manage parallel development with Git worktrees: creation with port allocation, environment sync, branch isolation, and cleanup. Use when working multiple branches at once, running parallel CI validations, or isolating agent workspaces. - 100merge-conflict-resolution-three-way-diff
Use this skill when resolving complex Git merge conflicts and rebases safely using three-way diff inspection tools. - 100roo-conflict-resolution
Provides comprehensive guidelines for resolving merge conflicts intelligently using git history and commit context. Use when tasks involve merge conflicts, rebasing, PR conflicts, or git conflict resolution. This skill analyzes commit messages, git blame, and code intent to make…