Diff Project
技能 已验证 活跃Shows what changed in dotforge since the project's last sync, to decide whether running /forge sync is worthwhile.
To provide clarity on project state changes and inform the decision to run a full synchronization process.
功能
- Compares project state against dotforge baseline
- Detects local file modifications
- Reports on changes in template/ and stacks/ directories
- Recommends sync action based on detected changes
使用场景
- Deciding whether to run `/forge sync` after code changes in dotforge.
- Understanding what changes have occurred in the project's managed configuration.
- Identifying local modifications that might conflict with an upcoming sync.
非目标
- Performing the sync operation itself.
- Managing git history or other project files outside of dotforge's scope.
- Replacing the core `/forge sync` functionality.
Practical Utility
- info:Usage examplesWhile the README provides installation and usage examples for the broader dotforge project, specific end-to-end examples for this 'diff-project' skill are not detailed, although the steps are outlined in SKILL.md.
安装
请先添加 Marketplace
/plugin marketplace add luiseiman/claude-kit/plugin install claude-kit@dotforge质量评分
已验证类似扩展
Sync Profiles
100用于在用户想要列出、创建、切换、删除、比较或检查配置同步配置文件时使用。
Sync Setup
100当用户首次设置配置同步、连接到 GitHub 或重新初始化备份存储库时使用。
Sync Pull
100当用户希望从 GitHub 恢复、下载或拉取其 Claude Code 配置到此计算机时使用。
Rule Effectiveness Analysis
100Analyze which rules are actively used vs inert. Detect coverage gaps. Recommend pruning to reduce token consumption.
Release Manager
100Use when the user asks to plan releases, manage changelogs, coordinate deployments, create release branches, or automate versioning.
Investigate Capa Root Cause
100Investigate root causes and manage CAPAs (Corrective and Preventive Actions) for compliance deviations. Covers investigation method selection (5-Why, fishbone, fault tree), structured root cause analysis, corrective vs preventive action design, effectiveness verification, and trend analysis. Use when an audit finding requires a CAPA, when a deviation or incident occurs in a validated system, when a regulatory observation needs a formal response, when a data integrity anomaly requires investigation, or when recurring issues suggest a systemic root cause.