fix-merge-conflicts
FeaturedResolve merge conflicts non-interactively, validate build and tests, and finalize conflict resolution
Code & Development 333 stars
40 forks Updated 2 days ago MIT
Install
Quality Score: 88/100
Stars 20%
Recency 20%
Frontmatter 20%
Documentation 15%
Issue Health 10%
License 10%
Description 5%
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
Code & Development Listed
fix-merge-conflicts
Resolve merge conflicts non-interactively, validate build and tests, and finalize conflict resolution
16 Updated today
ulises-jeremias Code & Development Listed
resolve-merge-conflicts
Resolve git merge/rebase conflicts safely by preserving both sides' intent and validating the result.
15 Updated today
Pythoughts-labs Code & Development Listed
resolving-merge-conflicts
Use when you need to resolve an in-progress git merge/rebase conflict.
1 Updated 1 weeks ago
JacobStephens2