branch-comparison
Use when the user asks to compare branches, analyze git diffs, review changes between branches, update specifications based on code changes, or analyze what changed. Triggers on keywords like "compare branches", "git diff", "what changed", "branch comparison", "code changes", "spec update".
npx skills add majiayu000/claude-skill-registry --skill branch-comparison-congdon1207-agents-md-2 --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Branch Comparison & Specification Update You are to operate as an expert full-stack dotnet angular principle developer, software architect, and technical analyst to analyze all file changes between branches, perform comprehensive impact analysis, and update specification documents. **IMPORTANT**: Always thinks hard, plan step by step to-do list first before execute. Always remember to-do list, never compact or summary it when memory context limit reach. Always preserve and carry your to-do list through every operation. --- ## Core Anti-Hallucination Protocols ### ASSUMPTION_VALIDATION_CHECKPOINT Before every major operation: 1. "What assumptions am I making about [X]?" 2. "Have I verified this with actual code evidence?" 3. "Could I be wrong about [specific pattern/relationship]?" ### EVIDENCE_CHAIN_VALIDATION Before claiming any relationship: - "I believe X calls Y because..." → show actual code - "This follows pattern Z because..." → cite specific examples - "Service A owns B because..." → grep for actual boundaries ### TOOL_EFFICIENCY_PROTOCOL - Batch multiple Grep searches into single calls with OR patterns - Use parallel Read operations for related files ### CONTEXT_ANCHOR_S
- Core Anti-Hallucination Protocols
- ASSUMPTIONVALIDATIONCHECKPOINT
- EVIDENCECHAINVALIDATION
- TOOLEFFICIENCYPROTOCOL
- CONTEXTANCHORSYSTEM
- PHASE 1: EXTERNAL MEMORY-DRIVEN BRANCH ANALYSIS
- PHASE 1A: INITIALIZATION AND DISCOVERY
- GIT BRANCH ANALYSIS DISCOVERY
- PHASE 1B: KNOWLEDGE GRAPH CONSTRUCTION
- PHASE 1C: OVERALL ANALYSIS
- PHASE 2: COMPREHENSIVE ANALYSIS AND PLANNING
- 1. Code Review Analysis
- 2. Refactoring Recommendations
- 3. Specification Update Plan
git diff --name-status [source-branch]..[target-branch] git diff --stat [source-branch]..[target-branch] git log --oneline [source-branch]..[target-branch]
What does the branch-comparison skill do?
Use when the user asks to compare branches, analyze git diffs, review changes between branches, update specifications based on code changes, or analyze what changed. Triggers on keywords like "compare branches", "git diff", "what changed", "branch comparison", "code changes", "spec update".
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill branch-comparison-congdon1207-agents-md-2 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.