AGENT SKILL
merge-conflicts
Resolve merge conflicts by rebasing. Use when PR mergeable status is CONFLICTING.
- License 许可
- MIT
- 最近更新
- 2026-03-11
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- merge-conflicts
- description
- Resolve merge conflicts by rebasing. Use when PR mergeable status is CONFLICTING.
- allowed-tools
- Bash
02 资源文件 14
- 参考文档references/animations.md4.6 KB
- 参考文档references/controls.md4.9 KB
- 参考文档references/form-sheet.md6.2 KB
- 参考文档references/gradients.md2.7 KB
- 参考文档references/icons.md4.7 KB
- 参考文档references/media.md6.1 KB
- 参考文档references/route-structure.md5.0 KB
- 参考文档references/search.md5.1 KB
- 参考文档references/storage.md2.9 KB
- 参考文档references/tabs.md13.0 KB
- 参考文档references/toolbar-and-headers.md7.9 KB
- 参考文档references/visual-effects.md4.2 KB
- 参考文档references/webgpu-three.md14.1 KB
- 参考文档references/zoom-transitions.md4.7 KB
03 SKILL.md 正文
Merge Conflict Resolution
Check Status
gh pr view <PR_NUMBER> --json mergeable --jq '.mergeable'
- MERGEABLE → No conflicts
- CONFLICTING → Must resolve conflicts FIRST
- UNKNOWN → Wait 30 seconds and retry
Resolve
git fetch origin main # or your base branch
git rebase origin/main
# For each conflicting file:
# 1. Find markers: <<<<<<<, =======, >>>>>>>
# 2. Edit to keep correct code
# 3. git add <file>
# 4. git rebase --continue
git push --force-with-lease
Critical
- Always resolve conflicts BEFORE other changes
- Use
--force-with-lease(never--force) - After resolving, verify the build still works
04 同仓库更多 Skills
story-workflow
9-phase workflow for implementing user stories. Covers requirements through verification.
★ 0
rfs-proposal
File a Request for Skill (RFS) when a skill gap is detected during execution.
★ 0
review-handling
Process review comments from AI review or human reviewers. Evaluate, respond, and resolve or escalate.
★ 0
pr-creation
Create GitHub pull requests with proper format.
★ 0
playwright-verify
Browser verification using Playwright MCP. Navigate, interact, screenshot.
★ 0
mandatory-gates
Pre-implementation gates. MUST be followed before writing any code. Investigation, confidence assessment, and scope confirmation.
★ 0