dyoshikawa/rulesync/.rulesync/skills/diff-analyze/SKILL.md
diff-analyze
Analyze the differences between the current branch and origin/main, and summarize the current work progress
- Source repository stars
- 1,263
- Declared platforms
- 0
- Static risk flags
- 1
- Last source update
- 2026-07-28
- Source checked
- 2026-07-28
Decision brief
What it does—and where it fits
Analyze the differences between the current branch and origin/main, and summarize the current work progress.
Not for
- Tasks that require unconfirmed production actions or broad system permissions.
- Environments where the pinned source and install steps cannot be inspected.
Compatibility matrix
Platform support, with evidence labels
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
Inspect first. Install second.
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/dyoshikawa/rulesync --skill ".rulesync/skills/diff-analyze"Inspect the Agent Skill "diff-analyze" from https://github.com/dyoshikawa/rulesync/blob/310b711fbe8cffc14debb276ade8a384c2b89083/.rulesync/skills/diff-analyze/SKILL.md at commit 310b711fbe8cffc14debb276ade8a384c2b89083. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
What the source asks the agent to do
- 01
Step 1: Refresh Main Branch
Fetch the latest main branch state:
Fetch the latest main branch state: - 02
Step 2: Inspect the Diff
Get the differences between the current branch and main:
Get the differences between the current branch and main: - 03
Step 3: Inspect Commit History
Get the commit history of the current branch since it diverged from main:
Get the commit history of the current branch since it diverged from main:
Permission review
Static risk signals and limitations
Runs scripts
The documentation asks the agent to run terminal commands or scripts.
git fetch origin mainRuns scripts
The documentation asks the agent to run terminal commands or scripts.
git diff origin/main...HEADEvidence record
Why each signal appears
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 64/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 1,263 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | catalog record | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Provenance and original SKILL.md
- Repository
- dyoshikawa/rulesync
- Skill path
- .rulesync/skills/diff-analyze/SKILL.md
- Commit
- 310b711fbe8cffc14debb276ade8a384c2b89083
- License
- MIT
- Collected
- 2026-07-28
- Default branch
- main
View the original SKILL.md
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:
git fetch origin main
Step 2: Inspect the Diff
Get the differences between the current branch and main:
git diff origin/main...HEAD
Step 3: Inspect Commit History
Get the commit history of the current branch since it diverged from main:
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.
Alternatives
Compare before choosing
coreyhaines31/marketingskills
ab-testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
coreyhaines31/marketingskills
churn-prevention
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o
event4u-app/agent-config
design-review
Use when the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. Uses a 7-phase methodology covering interaction, responsiveness, accessibility, and more.
K-Dense-AI/scientific-agent-skills
dask
Distributed computing for larger-than-RAM pandas/NumPy workflows. Use when you need to scale existing pandas/NumPy code beyond memory or across clusters. Best for parallel file processing, distributed ML, integration with existing pandas code. For out-of-core analytics on single machine use vaex; for in-memory speed use polars.