Skip to content
Development
Command

/export

Export the wiki (or architecture model) to markdown, HTML, JSON, or Structurizr DSL.

From plugin
repowise
8.1k17 skills17 commands1 MCP
> /plugin marketplace add repowise-dev/repowise
> /plugin install repowise@repowise

Command definition

export.md
description: Export the wiki (or architecture model) to markdown, HTML, JSON, or Structurizr DSL.
allowed-tools: Bash(repowise export:*), Read
disable-model-invocation: true

Repowise Export

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`).

Steps

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.

Choosing the invocation

Default — markdown under `.repowise/export`:

repowise export

Handle `$ARGUMENTS`:

  • "html" / "site" → `repowise export --format html`
  • "json" → `repowise export --format json`
  • "json full" / "archive" → `repowise export --format json --full`

(`--full` keeps tombstones and adds decisions / dead code / hotspots)

  • "structurizr" / "c4" / "dsl" → `repowise export --format structurizr`
  • "structurizr standalone" → `repowise export --format structurizr --standalone`
  • "structurizr components" → add `--components`
  • "to <dir>" / "-o <dir>" → pass `--output <dir>`

(for structurizr, a path ending in `.dsl` names the file itself)

  • A repo path → `repowise export <path> …`
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

Structurizr notes

  • Default structurizr output is a **model fragment** to include from your own

`workspace.dsl`. Pass `--standalone` for a complete workspace with default views.

  • `--force` overwrites an output file even if Repowise did not write it

(`--standalone` often targets `workspace.dsl`).

  • `--no-externals` leaves third-party dependencies out of the model.

Notes

  • Markdown / HTML / JSON write a directory of pages; structurizr writes DSL.
  • Never fabricate export contents. If the command reports no pages, say so and

suggest `/repowise:init`.

Read more
@repowise-dev
Ships withrepowise

Codebase intelligence for AI and humans: code health scores, auto-generated docs, git analytics, dead code detection, and architectural decisions via MCP.

8.1k9 skills1 MCP
Get the whole plugin

Stars on GitHub

Momentum

stars in total
8.1k
Star history of repowise-dev/repowise on GitHub, a chart by star-history.com

Other commands on repowise.

ask

ask

Command

Ask a codebase question and get a cited, synthesised answer with a confidence rating (costs an LLM call).

@repowise-dev@repowise-devInstall Command
context

context

Command

Triage card for files, modules, or symbols — layer, hotspot, fix history, freshness (relationships, not source bytes).

@repowise-dev@repowise-devInstall Command
coverage

coverage

Command

Ingest or inspect test-coverage reports (LCOV, Cobertura, Clover, Go cover profiles, JaCoCo, Salesforce Apex JSON, or repowise…

@repowise-dev@repowise-devInstall Command
decision

decision

Command

Work with architectural decisions; list, check health, record, pin, or put background records in force.

@repowise-dev@repowise-devInstall Command
doctor

doctor

Command

Diagnose the Repowise setup — install, API keys, index/store drift — and optionally repair it.

@repowise-dev@repowise-devInstall Command

More commands from other plugins.

build
Auto-invoked

build

Command

Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.

@addyosmani@addyosmaniInstall Command