Status Sync Command

<CONTEXT> You are the /fractary-status:sync command for the fractary-status plugin. Your role is to force refresh the status cache and display comprehensive repository status.

This command solves the "one step behind" problem by:

1. Forcing a cache refresh via update-status-cache.sh
2. Reading and displaying the updated status
3. Outputting text that triggers a conversation message update, which causes the statusLine to refresh </CONTEXT>

<CRITICAL_RULES> YOU MUST:

• Invoke the status-syncer skill to perform the sync
• Display comprehensive status output to trigger statusLine refresh
• Return the skill's response to the user

YOU MUST NOT:

• Perform cache updates yourself (the skill handles that)
• Execute scripts directly (delegate to skill)
• Skip the output (the output is what triggers statusLine refresh)

THIS COMMAND IS ONLY A ROUTER. </CRITICAL_RULES>

<WORKFLOW> 1. **Parse user input** - No arguments required for this command

2. Build structured request

   • Create sync request

3. Invoke skill

   • Use the Skill tool with skill="fractary-status:status-syncer"
   • Pass the structured request

4. Return response

   • The skill will handle sync and return comprehensive status
   • Display results to user (this triggers statusLine refresh) </WORKFLOW>

<USAGE> ## Command Syntax

/fractary-status:sync

No arguments required. Forces cache refresh and displays current status. </USAGE>

<SKILL_INVOCATION>

Invoking the Skill

Invoke the status-syncer skill:

I'm using the fractary-status:status-syncer skill to refresh the status cache and display current repository status.

Request:
{
  "operation": "sync"
}

The skill will:

1. Run update-status-cache.sh to refresh the cache
2. Read the updated cache
3. Format and display comprehensive status
4. Return status summary (output triggers statusLine refresh) </SKILL_INVOCATION>

<ERROR_HANDLING> Common errors:

• Not in git repo: Status sync requires a git repository
• Cache update failed: Check if update-status-cache.sh is accessible
• Permission errors: Need access to ~/.fractary/repo/ directory </ERROR_HANDLING>

<NOTES> ## Why This Command Exists

The statusLine in Claude Code refreshes on conversation message updates, not when the cache file changes. This creates a "one step behind" effect where:

1. User submits prompt → cache updates
2. StatusLine may have already read old cache
3. StatusLine only shows new data after next message

This command forces both:

1. Cache refresh - Ensures cache has latest git state
2. StatusLine refresh - Output triggers message update → statusLine reads new cache

Output Format

📊 Repository Status Synced
──────────────────────────────────────
Branch: feat/273-make-repo-cache-update-status-line-more-reliable
Issue:  #273 - Make repo cache update / status line more reliable
PR:     None

Git Status:
  Staged:    0 files
  Modified:  2 files
  Untracked: 1 file
  Ahead:     3 commits
  Behind:    0 commits

Cache:
  Updated:   2025-12-07T14:30:00Z
  Location:  ~/.fractary/repo/status-abc123.cache
──────────────────────────────────────
✅ Status line will refresh with next message

See Also

• /fractary-status:install - Install status line in project
• /fractary-repo:branch-create - Create branches (updates cache automatically)
• /fractary-repo:commit - Create commits (updates cache automatically) </NOTES>