fix-entry

Fix an existing Lucen Track entry

Use this skill to update fields on a time entry that's already been written. Never delete-and-recreate to fix a mistake — update-time-entry is the right tool.

Workflow

1. Find the entry. Call get-time-entries for the date or user the correction applies to. If multiple entries match the user's description ("yesterday's 2h entry" when there are two 2h entries), ask which one before changing anything.

2. Resolve any new references.

   • New project / phase / todo: use search-todos first if there's a ticket reference, otherwise get-projects.
   • New tags: use search-tags to resolve tag names to ids.

3. Update with only the fields that change. Call update-time-entry with the entry_id and ONLY the fields the user is changing. Do not re-send unchanged fields — that risks overwriting values the user didn't intend to touch.

   To detach a todo or remove tags, pass an explicit null or empty value for that field.

Rules

• Never fabricate project, phase, todo, entry, or tag IDs. Always look them up first.
• If the user describes the entry ambiguously, list candidates from get-time-entries and ask before updating.
• Durations are in minutes unless the tool documents otherwise. Confirm ambiguous phrases like "a bit shorter" before writing.
• Send only the changed fields. Do not re-send the full entry.
• If a tool returns an authentication error, tell the user they may need to re-authorize the Lucen Track connector — do not retry repeatedly.

Do not

• Do not call create-time-entry to "fix" an entry by replacement. That creates a duplicate. Use update-time-entry.
• Do not modify the timer from this skill — route timer changes to /track-timer.