/ flydocs-update
Pull the latest skills, hooks, commands, and configuration from the server.
The /flydocs-update command pulls the latest skills, hooks,
commands, and configuration from the server. It updates all managed
artifacts to their newest versions, equivalent to running
flydocs sync from the terminal but invocable from within
your AI session.
Usage
/flydocs-updateupdate flydocs to the latest versionWhat Happens
- Sync triggered: Calls
flydocs syncto pull config and artifacts from the server - Managed files replaced: Skills, hooks, commands, and cursor rules are updated to server versions
- User files preserved: Your
project.md, knowledge base, and context files are not touched - Change report: Shows what was updated so you know what changed
What Gets Updated
| Updated (server-owned) | Preserved (user-owned) |
|---|---|
| Skills and stage procedures | project.md |
| Hooks and commands | Knowledge base |
| Cursor rules | Session history |
| Issue and PR templates | service.json |
Protecting Local Changes
If you're actively developing skills or hooks locally, managed artifact
sync will overwrite your changes. To prevent this, add paths to
artifactOverrides.skipPaths in
.flydocs/config.json:
{
"artifactOverrides": {
"skipPaths": [".claude/skills/flydocs-workflow/"]
}
}
Paths listed in skipPaths are excluded from sync. This
setting is local only and not visible in the portal.
When to Use It
- When you see a notification that updates are available
- After an admin changes workspace configuration in the portal
- Periodically to ensure your local files match the server
- After resolving a conflict between local and server artifacts