.codex/skills/fix-merge-conflicts/SKILL.md
Resolve all merge conflicts on the current branch non-interactively, validate the build, and commit. Use when the user says "fix merge conflicts", "resolve conflicts", or when git status shows conflicting files.
npx skillsauth add bitsocialnet/5chan fix-merge-conflictsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Resolve all merge conflicts on the current branch non-interactively and leave the repo buildable.
git status --porcelain
Collect files with U statuses or containing <<<<<<< / ======= / >>>>>>> markers.
Open each conflicting file and remove conflict markers. Merge both sides logically when feasible.
When sides are mutually exclusive, pick the variant that:
File-type strategies:
| File type | Strategy |
|-----------|----------|
| package.json | Merge keys conservatively, then corepack yarn install to regenerate yarn.lock |
| yarn.lock | Never manually edit — regenerate with corepack yarn install |
| Config files (.json, .yaml) | Preserve union of safe settings; don't delete required fields |
| Markdown / text | Include both unique sections, deduplicate headings |
| Binary files | Prefer current branch (ours) |
| Generated / build artifacts | Prefer current branch (ours), or regenerate |
Run all three checks. Fix any failures before proceeding.
corepack yarn build && corepack yarn lint && corepack yarn type-check
If package.json was modified, run corepack yarn install first.
rg '<<<<<<<|=======|>>>>>>>' --type ts --type tsx --type json
If any markers remain, go back and resolve them.
git add -A
git commit -m "chore: resolve merge conflicts"
npx oxfmt <file> if they're .ts/.tsx/.js.corepack yarn build && corepack yarn lint && corepack yarn type-checkchore: resolve merge conflictstools
Profile app performance while browsing, collecting Web Vitals and React rerender data via react-scan. Orchestrates parallel profiler subagents via playwright-cli to capture navigation timing, long tasks, layout shifts, LCP, React commit counts, render bursts, and per-component render data. Use when profiling browsing performance, finding bottlenecks, diagnosing excessive rerenders, or auditing page performance.
tools
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
tools
Create a GitHub issue from recent changes, commit only relevant diffs on a short-lived task branch, push that branch, and open a PR into master that will close the issue on merge. Use when the user says "make closed issue", "close issue", or wants to create a tracked, already-resolved GitHub issue for completed work.
development
Formats GitHub issue titles and descriptions for tracking problems that were fixed. Use when proposing or implementing code changes, creating GitHub issues, or when the user asks for issue suggestions.