Overview

This skill helps you understand recent codebase changes by running a git diff against master and reading relevant spec files. It enables faster alignment before coding or reviewing by summarizing what changed and why it matters.

How This Skill Works

It executes git diff master to surface changes. It then reads any files in specs/ that are part of the diff to extract intent, requirements, and the affected behavior. The result is a concise context you can use to proceed confidently.

When to Use It

• Starting work on a feature in a codebase and needing context from the latest master
• Reviewing a merged PR to understand the exact changes that landed
• Onboarding to a new repository and wanting a quick briefing from specs
• Investigating a bug by tracing what spec files were affected by recent changes
• Preparing a summary for a team or changelog based on master-diff and specs

Quick Start

1. Step 1: Run git diff master to see what changed
2. Step 2: List and filter touched specs/ files from the diff (e.g., git diff --name-only master | grep ^specs/)
3. Step 3: Open and read the touched spec files and capture a brief summary of the changes and their impact

Best Practices

• Run git diff master to identify exactly what changed
• Filter the diff to include only files under specs/ for relevant context
• Read the touched spec files to capture requirements and expected behavior
• Keep a concise summary of changes and potential impacts
• Document any follow-up questions or ambiguities for the team

Example Use Cases

• After merging a feature branch, catch up with the exact spec changes that shipped
• New teammate onboarding: review master diff and specs to understand current state
• Bug reproduction: locate changed specs that mention related behavior
• Changelog draft: summarize what changed in master for release notes
• Code review prep: generate context before reviewing a PR

Frequently Asked Questions