Agent skill
diff-project
Shows what changed in dotforge since the project's last sync, to decide whether running /forge sync is worthwhile.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/diff-project
SKILL.md
Diff Project
Show what changed in dotforge since the last synchronization of the current project.
Step 1: Identify project baseline
- Read
$DOTFORGE_DIR/registry/projects.yml - Find the current project by
path(compare with$PWD) - Get
dotforge_versionandlast_sync - If no
dotforge_versionis registered (null), report:And stop.Project not synced — no baseline to compare against. Run /forge sync to establish baseline.
Step 2: Verify local manifest
If .claude/.forge-manifest.json exists in the current project:
- Read it and get the version and file hashes
- For each file in the manifest, calculate
shasum -a 256 <file> | cut -d' ' -f1 - Compare against the registered hash
- Report locally modified files (hash differs) and deleted files
- Use the manifest version as baseline (more precise than the registry)
If manifest does NOT exist, continue to Step 3 using git log.
Step 3: Detect changes in dotforge
Run in $DOTFORGE_DIR/:
git log --oneline v<version>..HEAD -- template/ stacks/
Where <version> is the tag corresponding to the project's dotforge_version.
If the tag does not exist, use last_sync as reference:
git log --oneline --since="<last_sync>" -- template/ stacks/
If there are no relevant commits, report:
dotforge has no changes in template/stacks since v<version>.
Project is up to date.
Step 4: Show change summary
For each modified file in template/ or relevant stacks/ for the project:
═══ DIFF dotforge: v<previous> → v<current> ═══
Project: <name> (last sync: <date>)
Files modified in dotforge:
template/hooks/block-destructive.sh — <diff summary>
template/rules/_common.md — <diff summary>
stacks/python-fastapi/rules/backend.md — <diff summary>
Local files with modifications (vs manifest):
.claude/rules/_common.md — hash differs from deployed
Filter stacks/ to show only the stacks used by the project (read from registry).
Step 5: Recommend action
If there are relevant changes:
Recommendation: run /forge sync to incorporate these changes.
If there are only cosmetic changes or changes in unused stacks:
Changes do not affect this project. Sync is not necessary.
Installation
This skill is installed automatically if the skills/ symlink already exists in ~/.claude/skills/. If not, create the symlink:
ln -sf $DOTFORGE_DIR/skills ~/.claude/skills
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?