repowiseDecisions in repowise are linked to graph nodes, surfaced via
get_why, and tracked for staleness as code
evolves. Three sources feed them: git archaeology (auto-proposed),
inline # DECISION: markers in source, and the CLI commands below.
repowise decision add
Interactively capture a new decision. Prompts for title, context, decision, rationale, alternatives, consequences, affected files, and tags.
repowise decision add [PATH]repowise decision list
List decision records. By default shows everything; flags filter the view.
repowise decision list [PATH] [OPTIONS]| Parameter | Type | Default | Description |
|---|---|---|---|
--status | string | all | proposed, active, deprecated, superseded, all |
--source | string | all | git_archaeology, inline_marker, readme_mining, cli, all |
--proposed | boolean | false | Shortcut for --status proposed |
--stale-only | boolean | false | Show only stale decisions |
repowise decision list
repowise decision list --status active
repowise decision list --proposed
repowise decision list --stale-onlyrepowise decision show
Show full details of one decision.
repowise decision show DECISION_ID [PATH]repowise decision confirm
Confirm a proposed decision, setting status to active.
repowise decision confirm DECISION_ID [PATH]repowise decision deprecate
Deprecate an active decision. Optionally link the decision that replaces it.
repowise decision deprecate DECISION_ID [PATH] [OPTIONS]| Parameter | Type | Description |
|---|---|---|
--superseded-by | string | ID of the decision that replaces this one. |
repowise decision dismiss
Dismiss (delete) a proposed decision. Requires confirmation.
repowise decision dismiss DECISION_ID [PATH]repowise decision health
The dashboard view: stale decisions, proposed-awaiting-review, ungoverned hotspots.
repowise decision health [PATH]The same data is available to your AI agent through get_why() (no
arguments); that's the agent-facing equivalent of this command.