/update
Trigger an incremental Repowise update to sync documentation with recent code changes.
> /plugin marketplace add repowise-dev/repowise > /plugin install repowise@repowise
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.
Trigger an incremental Repowise update to sync documentation with recent code changes.
Command definition
update.mddescription: Trigger an incremental Repowise update to sync documentation with recent code changes.
allowed-tools: Bash, Read
Repowise Update
Trigger an incremental update of the Repowise index.
Steps
1. Check if `.repowise/` exists. If not: "This repo isn't indexed yet. Run `/repowise:init` first."
2. Run: `repowise update`
This will:
- Detect files changed since last sync commit
- Update git metadata for changed files
- Regenerate affected wiki pages (up to cascade budget of 30)
- Decay confidence scores for indirectly affected pages
- Update dead code analysis
- Update CLAUDE.md if enabled
3. Show the output summary to the user.
Available flags
- `--provider NAME` — override the LLM provider
- `--model NAME` — override the model
- `--since REF` — base git ref to diff from (overrides saved last_sync_commit). Accepts a commit SHA, tag, or branch name.
- `--cascade-budget N` — max pages to regenerate per run (default: 30)
- `--dry-run` — show affected pages without regenerating
- `-v, --verbose` — show the full changed-file list, per-phase internals, and debug logs (the run is quiet by default)
Handling $ARGUMENTS
If the user provides arguments:
- "dry-run" or "dry run" → add `--dry-run` flag
- "force" or "full" → add `--cascade-budget 999` to regenerate all stale pages
- a git ref like a SHA or tag → add `--since {ref}`
- a file path → this is not supported by update; suggest `repowise update` which auto-detects changes
Read more
description: Trigger an incremental Repowise update to sync documentation with recent code changes. allowed-tools: Bash, Read
Repowise Update
Trigger an incremental update of the Repowise index.
Steps
1. Check if `.repowise/` exists. If not: "This repo isn't indexed yet. Run `/repowise:init` first."
2. Run: `repowise update`
This will:
- Detect files changed since last sync commit
- Update git metadata for changed files
- Regenerate affected wiki pages (up to cascade budget of 30)
- Decay confidence scores for indirectly affected pages
- Update dead code analysis
- Update CLAUDE.md if enabled
3. Show the output summary to the user.
Available flags
- `--provider NAME` — override the LLM provider
- `--model NAME` — override the model
- `--since REF` — base git ref to diff from (overrides saved last_sync_commit). Accepts a commit SHA, tag, or branch name.
- `--cascade-budget N` — max pages to regenerate per run (default: 30)
- `--dry-run` — show affected pages without regenerating
- `-v, --verbose` — show the full changed-file list, per-phase internals, and debug logs (the run is quiet by default)
Handling $ARGUMENTS
If the user provides arguments:
- "dry-run" or "dry run" → add `--dry-run` flag
- "force" or "full" → add `--cascade-budget 999` to regenerate all stale pages
- a git ref like a SHA or tag → add `--since {ref}`
- a file path → this is not supported by update; suggest `repowise update` which auto-detects changes
Codebase intelligence for AI and humans: code health scores, auto-generated docs, git analytics, dead code detection, and architectural decisions via MCP.
Repo: repowise-dev/repowise
Other commands on repowise.
- /coverage
Ingest or inspect test-coverage reports — LCOV, Cobertura/Clover, or coverage.py .coverage (builds the per-test map when contexts are present).
Open command - /dead-code
Report unreachable files, unused exports, and zombie packages, tiered by confidence.
Open command - /decision
Work with architectural decisions — list, inspect health, add, or confirm auto-proposed decisions.
Open command - /doctor
Diagnose the Repowise setup — install, API keys, index/store drift — and optionally repair it.
Open command - /health
Show Repowise code-health — KPIs, lowest-scoring files, refactoring targets, trends, or per-file markers.
Open command - /impacted-tests
Print the tests whose coverage intersects a change's changed lines — for a commit, base..head range, or staged diff.
Open command

