diff-analyze
Analyze the differences between the current branch and origin/main, and summarize the current work progress
npx skills add dyoshikawa/rulesync --skill diff-analyze --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.
# Diff Analyze Analyze the differences between the current branch and `origin/main`, and summarize the current work progress. ## Step 1: Refresh Main Branch Fetch the latest main branch state: ```bash git fetch origin main ``` ## Step 2: Inspect the Diff Get the differences between the current branch and main: ```bash git diff origin/main...HEAD ``` ## Step 3: Inspect Commit History Get the commit history of the current branch since it diverged from main: ```bash git log origin/main..HEAD --oneline ``` ## Step 4: Summarize the Work Based on the diff and commit history, summarize: - The main purpose of the current changes - The notable files or areas affected - The current implementation progress - Any obvious risks, gaps, or follow-up work Keep the summary concise and practical.
- Step 1: Refresh Main Branch
- Step 2: Inspect the Diff
- Step 3: Inspect Commit History
- Step 4: Summarize the Work
git fetch origin main git diff origin/main...HEAD git log origin/main..HEAD --oneline
What does the diff-analyze skill do?
Analyze the differences between the current branch and origin/main, and summarize the current work progress
How do I install it?
Run `npx skills add dyoshikawa/rulesync --skill diff-analyze --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 dyoshikawa/rulesync, a repository with 1,285 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.