/update
Update THRUNT to latest version with changelog display
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/update
Context preview
What this command does when you run it.
Update THRUNT to latest version with changelog display
Command definition
update.mdname: thrunt:update description: Update THRUNT to latest version with changelog display allowed-tools: - Bash - AskUserQuestion
<objective> Check for THRUNT updates, install if available, and display what changed.
Routes to the update workflow which handles:
- Version detection (local vs global installation)
- npm version checking
- Changelog fetching and display
- User confirmation with clean install warning
- Update execution and cache clearing
- Restart reminder
</objective>
<execution_context> @~/.claude/thrunt-god/workflows/update.md </execution_context>
<process> **Follow the update workflow** from `@~/.claude/thrunt-god/workflows/update.md`.
The workflow handles all logic including: 1. Installed version detection (local/global) 2. Latest version checking via npm 3. Version comparison 4. Changelog fetching and extraction 5. Clean install warning display 6. User confirmation 7. Update execution 8. Cache clearing </process>
Repo: backbay-labs/thrunt-god
Other commands on thrunt-god.
map-environment
Map available telemetry, query surfaces, tenants, retention windows, and investigation blind spots
new-case
Initialize a threat hunting case from a signal, detection, intel lead, or analyst suspicion
new-program
Initialize a threat hunting program with an environment map, tool inventory, huntmap, and empty execution directories
plan
Create phase plans for a threat hunt with exact telemetry tasks, receipts, and query outputs
publish
Publish a hunt as a case report, escalation, detection promotion, or leadership summary

