Agent skill
git-merge
[Git] ⚠️ Merge code from one branch to another
Install this agent skill to your Project
npx add-skill https://github.com/duc01226/EasyPlatform/tree/main/.claude/skills/git-merge
SKILL.md
[IMPORTANT] Use
TaskCreateto break ALL work into small tasks BEFORE starting — including tasks for each file read. This prevents context loss from long files. For simple tasks, AI MUST ask user whether to skip.
Quick Summary
Goal: Merge code from one branch to another with safety checks and conflict resolution.
Workflow:
- Validate -- Check source/target branches, verify clean working tree
- Merge -- Execute git merge with appropriate strategy
- Resolve -- Handle conflicts if any, verify merge result
Key Rules:
- WARNING: destructive operation -- always confirm with user first
- Verify clean working tree before merge
- Use
/git-conflict-resolveif conflicts arise
Be skeptical. Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence percentages (Idea should be more than 80%).
Variables
TO_BRANCH: $1 (defaults to main)
FROM_BRANCH: $2 (defaults to current branch)
Workflow
Step 1: Sync with remote (CRITICAL)
git fetch origin
git checkout {TO_BRANCH}
git pull origin {TO_BRANCH}
Step 2: Merge from REMOTE tracking branch
# Use origin/{FROM_BRANCH} to merge remote state, not local WIP
git merge origin/{FROM_BRANCH} --no-ff -m "merge: {FROM_BRANCH} into {TO_BRANCH}"
Why origin/{FROM_BRANCH}: Ensures merging only committed+pushed changes, not local uncommitted work.
Step 3: Resolve conflicts if any
- If conflicts exist, resolve them manually
- After resolution:
git add . && git commit
Step 4: Push merged result
git push origin {TO_BRANCH}
Notes
- If
ghcommand is not available, instruct the user to install and authorize GitHub CLI first. - If you need more clarifications, use
AskUserQuestiontool to ask the user for more details. - Always fetch and pull latest remote state before merging to avoid stale conflicts.
Closing Reminders
- MUST break work into small todo tasks using
TaskCreateBEFORE starting - MUST search codebase for 3+ similar patterns before creating new code
- MUST cite
file:lineevidence for every claim (confidence >80% to act) - MUST add a final review todo task to verify work quality
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
fix-parallel
[Implementation] Analyze & fix issues with parallel fullstack-developer agents
ask
[Utilities] Answer technical and architectural questions.
claude-code
[Utilities] Claude Code CLI setup, configuration, troubleshooting, and feature guidance. Triggers on claude code setup, hook not firing, MCP connection, context limit, skill creation, slash command setup.
workflow-deployment
[Workflow] Trigger Deployment & Infrastructure workflow — CI/CD pipelines, Docker, Kubernetes setup and deployment.
workflow-idea-to-pbi
[Workflow] Trigger Idea to PBI workflow — po/ba workflow: capture idea, refine to pbi, create stories, prioritize.
easy-claude-help
[Utilities] Configuration guide for the easy-claude framework — explain settings, guide users through configuring .ck.json.
Didn't find tool you were looking for?