diff-project

Compare registry baseline and local manifest to detect dotforge changes.

8|1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/luiseiman/dotforge --skill diff-project
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diff-project
Source: https://github.com/luiseiman/dotforge/tree/main/skills/diff-project
Command: npx skills add https://github.com/luiseiman/dotforge --skill diff-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shows what changed in dotforge since the project's last synchronization, helping teams decide whether running /forge sync is worthwhile.

Core Features & Use Cases

  • Identify the project baseline by cross-referencing registry and last_sync.
  • Detect changes in dotforge across templates and stacks and present a concise summary.
  • Recommend whether to run /forge sync based on the detected changes.

Quick Start

Run the diff-project skill in the target project directory to view changes since the last sync and determine if a /forge sync is needed.

Frequently Asked Questions about diff-project

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check what changed in my project templates and stacks since the last sync?

To check changes in templates and stacks since the last sync, compare the registry baseline with the local manifest. The diff-project skill cross-references registry/projects.yml to locate the project path and last_sync, then detects differences in dotforge_version to summarize modified files.

How do I detect dotforge configuration drift before updating my project?

Detect dotforge configuration drift by inspecting the repository against registry/projects.yml to find the last_sync timestamp. The diff-project skill compares the dotforge_version and local manifest, falling back to git history if the manifest is missing, to locate any modified template and stacks files.

When do I need to run a forge sync for my project?

You need to run a forge sync when file modifications exist in template/ or stacks/ directories. The diff-project skill identifies these changes by comparing the registry baseline and local manifest since the last_sync, recommending the sync action only if differences are detected.

Can I compare dotforge versions if the local manifest is unavailable?

You can compare dotforge versions without a local manifest by falling back to git history. When the manifest is missing, the diff-project skill inspects the repository against registry/projects.yml to identify the last_sync and uses git logs to locate modified template/ and stacks/ files.

What is the best way to monitor project management template changes across multiple stacks?

The best way to monitor template and stacks changes is to run the diff-project skill in the target project directory. It cross-references registry/projects.yml to identify the project baseline and last_sync, returning a concise summary of modified files to help decide if synchronization is necessary.

Why does my dotforge project diff show no changes after updating templates?

A dotforge project diff may show no changes if the registry baseline and local manifest are already synchronized. The diff-project skill compares the dotforge_version against registry/projects.yml since the last_sync, and if no modified template/ or stacks/ files are found, no sync action is recommended.