/arnold:update
Sync docs after code changes. Arnold scans git diffs and proposes doc updates.
When to use it
After making code changes that should be reflected in your docs. Arnold looks at what changed in the code and proposes matching updates to the relevant doc files.
Usage
> /arnold:update
🦕 ARNOLD UPDATE
━━━━━━━━━━━━━━━━
Scanning recent git changes...
Modified: src/models/booking.rb
+ MAX_CAPACITY changed from 20 → 30
Modified: src/config/auth.rb
+ SESSION_TTL changed from 86400 → 259200
Proposed doc updates:
~ booking-overview.md: "Maximum 20 spots" → "Maximum 30 spots"
~ auth-overview.md: "24 hours" → "72 hours"
✓ 2 doc updates proposed. Review and approve.
What it does
- Scans recent git diffs for meaningful code changes
- Identifies which doc files reference the changed values
- Proposes specific text changes to bring docs in line with code
- Waits for your approval before making changes
💡 Tip
Use /arnold:update after a coding session to keep docs in sync. Use /arnold:check first if you're not sure what drifted.
See also
- /arnold:check - Find drift before updating
- /arnold:resolve - Fix drift items interactively