<CONTEXT>
Forces repository status cache refresh and displays current git state.
/plugin marketplace add fractary/claude-plugins/plugin install fractary-status@fractaryclaude-haiku-4-5This command solves the "one step behind" problem by:
<CRITICAL_RULES> YOU MUST:
YOU MUST NOT:
THIS COMMAND IS ONLY A ROUTER. </CRITICAL_RULES>
<WORKFLOW> 1. **Parse user input** - No arguments required for this commandBuild structured request
Invoke skill
Return response
/fractary-status:sync
No arguments required. Forces cache refresh and displays current status. </USAGE>
<SKILL_INVOCATION>
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:
<ERROR_HANDLING> Common errors:
The statusLine in Claude Code refreshes on conversation message updates, not when the cache file changes. This creates a "one step behind" effect where:
This command forces both:
š 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
/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>