Our review
Checks for drift between the repository and the running system, inspecting app signing, symlinks, scripts, and source code.
Strengths
- Automated detection of inconsistencies between source code and active environment.
- Verifies app signing with correct Team ID.
- Checks symlinks, script consistency, and source matching.
Limitations
- Specific to the Samara system and its repository structure.
- Cannot automatically fix all detected issues.
- Requires the 'fork' context to operate.
Use this skill after making script changes, before or after a rebuild, or when the system behaves unexpectedly.
Avoid using it if no changes have been made and the system is working fine, as it may unnecessarily consume resources.
Security analysis
SafeThe skill only runs a read-only check script and outputs results; no destructive or exfiltrating commands are executed.
No concerns found
Examples
Check for drift between the repo and the running system.Is the system in sync with the repository? Run a drift check before updating.name: sync description: Check for drift between repo and running system. Use when checking if scripts or Samara are out of sync, verifying system integrity, or before/after rebuilds. Trigger words: sync, organism sync, check drift, system drift, repo sync. context: fork allowed-tools:
- Bash
- Read
- Grep
Sync Skill
Check for drift between the repo and running system, and optionally fix it.
What This Does
Runs the sync-organism script to detect differences between:
~/Developer/samara-main/(the repo/genome)~/.claude-mind/(the running organism)/Applications/Samara.app(the built app)
Running the Check
~/.claude-mind/system/bin/sync-organism
What It Checks
- Samara.app Signing - Correct Team ID (G4XVD3J52J)
- Skills Symlinks - All skills properly linked from repo
- Script Drift - Differences between repo and runtime scripts
- Samara Source - Whether installed app matches source code
When to Use
- After making changes to scripts in either location
- Before/after
update-samararebuilds - During wake cycles (for monitoring)
- When something "should work but doesn't"
Output Example
## Samara.app Signing
[OK] Samara.app signed with correct Team ID: G4XVD3J52J
## Skills Symlinks
[OK] 10 skills properly symlinked
## Script Drift Analysis
[OK] All shared scripts are identical
## Samara.app Source Check
[OK] Samara.app is up to date with source
SUMMARY
Total drift: 0 issues
Fixing Drift
If drift is detected, the script shows commands to fix it. Common fixes:
- Copy runtime script to repo:
cp ~/.claude-mind/system/bin/X ~/Developer/samara-main/scripts/ - Rebuild Samara:
~/.claude-mind/system/bin/update-samara - Recreate symlinks: Run
sync-skillsor manually create symlinks
Docker Compose Architect
DevOps
Designs optimized Docker Compose configurations.
Incident Postmortem Writer
DevOps
Writes structured and blameless incident postmortem reports.
Runbook Creator
DevOps
Creates clear operational runbooks for common DevOps procedures.