Skip to main content
command CX Codex

visual · gmickel — Claude Code command: what it does, how to install

Summarizes a spec, task, git diff, or topic into a concise Markdown visual digest directly in your chat.

MIT ★ 730 updated 2026-10-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add gmickel/flow-next
/plugin install flow-next@flow-next
Open on GitHub

What visual does

The visual command is part of the flow-next repository and serves as a direct trigger for the flow-next-visual skill. It forwards its inputs without alterations, accepting a spec ID, a task ID, a git revision range, or an arbitrary topic.

All work happens strictly in read-only mode. It never writes to repository files, emitting Markdown directly to the chat conversation. The underlying skill automatically detects target types and prepares the formatted digest. Without flow-next-visual installed, the command cannot function because it performs no standalone processing.

What it helps with

  • turn a broad git diff into a concise chat digest
  • inspect spec or task state without writing project files
  • generate a structured summary for any free-form topic

Example prompts for the agent

  • /visual spec-42
  • /visual HEAD~3..HEAD
  • /visual authentication system architecture

How to install visual

1Plugin marketplace

/plugin marketplace add gmickel/flow-next
/plugin install flow-next@flow-next

2Manually: put the files in place

.claude/commands/visual.md

Call it with /visual. For all projects use ~/.claude/commands/

Questions about visual

How to install visual in Claude Code?

Run /plugin marketplace add gmickel/flow-next first, then run /plugin install flow-next@flow-next.

What does visual do?

It passes user arguments directly to flow-next-visual to produce a concise Markdown summary in your chat.

Does visual modify project files?

No. The command is strictly read-only and displays output exclusively in the current session.

Source text

visual.md · MIT
---
name: visual
description: Restate a spec, task, diff, or the current topic as a compact markdown visual digest
argument-hint: "[spec id | task id | git range | free-form topic]"
disable-model-invocation: true
---

# IMPORTANT: This command MUST invoke the skill `flow-next-visual`

The ONLY purpose of this command is to call the `flow-next-visual` skill. You MUST use that skill now.

**Arguments:** $ARGUMENTS

Pass the arguments to the skill verbatim. The skill handles target detection (spec / task / diff / ad-hoc), state reads, shape selection, and the digest. It is read-only — chat output only.

© Gordon Mickel · MIT · gmickel/flow-next

Similar slash commands

All slash commands for Notes, tasks and projects →

visual by other authors comes first.

visual syahiidkamil The visual command turns a discussion into a self-contained HTML document with diagrams, wireframes and matrices the agent implements from in plan mode. CX Codex +1 ★ 406repo stars visual-recap BuilderIO visual-recap turns a PR, branch, or git diff into an interactive visual plan with diagrams, file maps, and annotated diffs. Built for reviewing large multi-file changes. CX Codex +1 1,000installs operator-scorecard aeonfun operator-scorecard generates agent activity summaries: rolls up a weekly system health scorecard, drafts daily ops recaps, and inspects git push diffs. CX Codex +1 ★ 797repo stars caveman-review JuliusBrussee caveman-review turns code review comments into one line per finding: location, problem, fix. Useful when a diff or PR needs a fast pass without the filler. CX Codex +1 437,600installs visual-explainer vercel-labs visual-explainer turns bugs, PRs and features into step-by-step infographics with diagrams, syntax-highlighted code and a clear before/after boundary. CX Codex +1 235installs visual-pr humanlayer visual-pr — a skill that automates pull request descriptions: reads the diff, gathers context, and fills a template so reviewers understand why the change exists and how it's shaped. CX Codex +1 4,500installs understand-diff Egonex-AI understand-diff analyzes Git diffs against the project knowledge graph to identify affected dependencies, architectural layers, and merge risks. Useful before reviewing pull requests. CX Codex +1 4,200installs

From the same set70

The whole set →

Project sponsors

Companies that keep this analytics open