Catch Up on Branch Changes
This command reviews all changes between the current branch and master, analyzes key files, and provides a comprehensive summary to help you catch up on what's been done.
Steps:
- •Run
git statusto get the current branch name and verify we're not on master - •Run
git fetch origin masterto ensure we have the latest master branch - •Run
git diff master...HEAD --name-onlyto get list of changed files - •Run
git diff master...HEAD --statto get a summary of changes - •Run
git log master..HEAD --onelineto get the commit history for this branch - •Read and analyze the most important changed files (prioritize: manifests, configs, core logic files)
- •Provide a high-level summary including:
- •Branch purpose and scope of changes
- •Key files modified and their significance
- •Potential impact areas
- •Any notable patterns or architectural changes
- •Suggested review focus areas