Diff Project
Skill Verifiziert AktivShows 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.
Funktionen
- 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
Anwendungsfälle
- 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.
Nicht-Ziele
- 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.
Installation
Zuerst Marketplace hinzufügen
/plugin marketplace add luiseiman/claude-kit/plugin install claude-kit@dotforgeQualitätspunktzahl
VerifiziertVertrauenssignale
Ähnliche Erweiterungen
Sync Profiles
100Verwenden Sie dies, wenn der Benutzer Konfigurations-Synchronisationsprofile auflisten, erstellen, wechseln, löschen, vergleichen oder inspizieren möchte.
Sync Setup
100Wird verwendet, wenn der Benutzer zum ersten Mal die Konfigurationssynchronisierung einrichten, eine Verbindung zu GitHub herstellen oder das Backup-Repository neu initialisieren möchte.
Sync Pull
100Verwenden Sie dies, wenn der Benutzer seine Claude Code-Konfiguration von GitHub auf diesem Computer wiederherstellen, herunterladen oder pullen möchte.
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.