name: fix-merge-conflicts description: "Use when a branch needs conflicts resolved and the merged result verified." license: MIT metadata: version: "1.0.1" author: jstack-maintainers source: michael-denyer/pstack-claude source-version: "0.9.102" source-commit: 356c6e0f978df729eb16f227d795f34d221c5aad owner: software-factory risk: high capabilities: jstack,pull-request-workflow

Fix merge conflicts

Trigger

Branch has unresolved merge conflicts and needs a reliable path to a buildable state.

Workflow

1. Detect all conflicting files from git status and conflict markers.
2. Resolve each conflict with minimal, correctness-first edits.
3. Prefer preserving both sides when safe. Otherwise, choose the variant that compiles and keeps public behavior stable.
4. Regenerate lockfiles with package manager tools instead of hand-editing.
5. Run compile, lint, and relevant tests.
6. Stage resolved files and summarize key decisions.

Guardrails

• Keep changes minimal and readable.
• Do not leave conflict markers in any file.
• Avoid broad refactors while resolving conflicts.
• Do not push or tag during conflict resolution.

Output

• Files resolved
• Notable resolution choices
• Build/test outcome