diff-analyze · dyoshikawa — Claude Code skill: what it does, how to install
Fetches origin/main, examines your branch changes, and summarizes current progress. Useful before opening a pull request.
npx skills add dyoshikawa/rulesync --skill diff-analyze -a claude-codeWhat diff-analyze does
This skill inspects work in progress within the active Git branch. The workflow runs in four steps. First, it pulls the latest main branch data with git fetch origin main. Then it runs git diff origin/main...HEAD to review code modifications and git log origin/main..HEAD --oneline to check commit history.
Using the diff and commit logs, the agent prepares a concise summary. The report highlights the purpose of the work, modified files, implementation status, and noticeable risks or follow-up tasks. Because the instructions hardcode origin/main, the workflow will fail on repositories using master as their default branch.
What it helps with
- summarize branch progress before opening a pull request
- spot implementation gaps and potential risks in unmerged code
- inspect Git diff and commit logs against origin/main in one run
- list affected files and review status during ongoing development
Example prompts for the agent
- Run diff-analyze to summarize my branch progress against origin/main
- Compare my current changes with origin/main and point out any remaining risks
- Use diff-analyze to prepare a quick status report from my recent commits
How to install diff-analyze
1Skills CLI (Vercel)
npx skills add dyoshikawa/rulesync --skill diff-analyze -a claude-code2Manually: put the files in place
~/.claude/skills/diff-analyze/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/diff-analyze/
1Skills CLI (Vercel)
npx skills add dyoshikawa/rulesync --skill diff-analyze -a codex2Manually: put the files in place
.agents/skills/diff-analyze/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add dyoshikawa/rulesync --skill diff-analyze -a cursor2Manually: put the files in place
.cursor/skills/diff-analyze/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install dyoshikawa/rulesync diff-analyze2Manually: put the files in place
.github/skills/diff-analyze/SKILL.md1Skills CLI (Vercel)
npx skills add dyoshikawa/rulesync --skill diff-analyze -a gemini-cli2Platform CLI
gemini skills install https://github.com/dyoshikawa/rulesync --path .rulesync/skills/diff-analyzeManually: put the files in place
.devin/skills/diff-analyze/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add dyoshikawa/rulesync --skill diff-analyze -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about diff-analyze
How do I install diff-analyze in Claude Code?
Run npx skills add dyoshikawa/rulesync --skill diff-analyze -a claude-code in your terminal. The skill file is placed in ~/.claude/skills/diff-analyze/SKILL.md.
What does the diff-analyze skill do?
It refreshes origin/main, inspects differences and commit history on your current branch, and drafts an actionable summary of changes.
Which target branch does diff-analyze inspect?
The skill compares your current branch specifically against origin/main.
Source text
SKILL.md · MIT
--- name: diff-analyze description: >- Analyze the differences between the current branch and origin/main, and summarize the current work progress targets: - "*" --- # 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.
© dyoshikawa · MIT · dyoshikawa/rulesync
Similar skills
All skills for Git and GitHub →diff-analyze by other authors comes first.