ask
CommandAsk a codebase question and get a cited, synthesised answer with a confidence rating (costs an LLM call).
Export the wiki (or architecture model) to markdown, HTML, JSON, or Structurizr DSL.
> /plugin marketplace add repowise-dev/repowise> /plugin install repowise@repowise
description: Export the wiki (or architecture model) to markdown, HTML, JSON, or Structurizr DSL. allowed-tools: Bash(repowise export:*), Read disable-model-invocation: true
Export indexed wiki pages to files, or emit a Structurizr DSL architecture model. Use this when the user wants a shareable dump, a static site, a JSON archive, or a C4/Structurizr model — not when they need an interactive Q&A answer (`/repowise:ask`).
1. If `.repowise/` doesn't exist: "This repo isn't indexed yet. Run `/repowise:init` first." Stop. 2. Resolve format and output from `$ARGUMENTS` (see below). 3. Run `repowise export` and report where files were written (page count / output path). Do not invent page content.
Default — markdown under `.repowise/export`:
repowise export
Handle `$ARGUMENTS`:
(`--full` keeps tombstones and adds decisions / dead code / hotspots)
(for structurizr, a path ending in `.dsl` names the file itself)
repowise export repowise export --format html -o ./site repowise export --format json --full repowise export --format structurizr --standalone --components repowise export --format structurizr -o architecture.dsl
`workspace.dsl`. Pass `--standalone` for a complete workspace with default views.
(`--standalone` often targets `workspace.dsl`).
suggest `/repowise:init`.
Codebase intelligence for AI and humans: code health scores, auto-generated docs, git analytics, dead code detection, and architectural decisions via MCP.
Ask a codebase question and get a cited, synthesised answer with a confidence rating (costs an LLM call).
Triage card for files, modules, or symbols — layer, hotspot, fix history, freshness (relationships, not source bytes).
Ingest or inspect test-coverage reports (LCOV, Cobertura, Clover, Go cover profiles, JaCoCo, Salesforce Apex JSON, or repowise…
Report unreachable files, unused exports, and zombie packages, tiered by confidence.
Work with architectural decisions; list, check health, record, pin, or put background records in force.
Diagnose the Repowise setup — install, API keys, index/store drift — and optionally repair it.
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.