Stats
Actions
Tags
From jarvis
Applies pending JaRVIS data-dir schema migrations when the plugin is not seeing recent data, after upgrading, or when SessionStart reports a migration failure.
How this skill is triggered — by the user, by Claude, or both
Slash command
/jarvis:jarvis-migrateThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Bring the JaRVIS data directory's schema up to date with the current plugin version.
Bring the JaRVIS data directory's schema up to date with the current plugin version.
This skill is normally invoked automatically by the SessionStart hook, by /jarvis-reflect (via finalize-reflection.sh), and by /jarvis-reload. You only invoke it manually when those automatic paths are unavailable or have failed.
JARVIS_DIR=$(bash <skill-path>/scripts/resolve-dir.sh)
If the resolved directory doesn't exist, tell the user to run /jarvis-init first, then stop.
bash <skill-path>/scripts/migrate.sh "$JARVIS_DIR"
Behavior:
JaRVIS data dir migrated v<old> → v<new> and a bullet list = migrations applied. Surface this to the user.Briefly tell the user what the runner did. If migrations ran, summarize each bullet. If it was a no-op, say "data dir already current."
npx claudepluginhub epicrunze/jarvis --plugin jarvisCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.