fix-merge-conflicts

Featured

Resolve merge conflicts non-interactively, validate build and tests, and finalize conflict resolution

Code & Development 333 stars 40 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 88/100

Stars 20%
84
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
42
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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

Details

Author
michael-denyer
Repository
michael-denyer/pstack-claude
Created
3 months ago
Last Updated
2 days ago
Language
TypeScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category