/flowforge:dev:status
/flowforge:dev:status is the at-a-glance command for a FlowForge work session. It assembles a single report from git, the test runner (if available), the time tracker, and project-health indicators, then prints it to the terminal. Use it to confirm what the framework thinks the session looks like before, during, or after work.
Synopsis
Section titled “Synopsis”/flowforge:dev:status [--verbose|--brief|help|?]From outside Claude Code:
flowforge run flowforge:dev:statusDescription
Section titled “Description”The command runs a sequence of read-only probes and prints a structured overview. The default output covers four sections:
- Git status — current branch, ahead/behind counts, dirty file count.
- Test status — last test run results, when a recognized runner is detected in the project.
- Time tracking — active task, elapsed time on the current session, and accumulated time on the ticket.
- Project health — FlowForge-specific indicators (rules drift, missing manifest, stale session).
The output is shaped by mode flags:
--verboseincludes per-file change details, full provider task data, and any non-fatal warnings.--briefcollapses each section to a single line.- The literal values
?andhelpprint an in-terminal usage block and exit0.
The command is read-only: it does not mutate .flowforge/, the working tree, or the timer. It is safe to run mid-session, mid-pause, or before a session has started.
Arguments
Section titled “Arguments”This command is option-driven. Positional arguments other than ?/help are ignored.
Options
Section titled “Options”| Flag | Description |
|---|---|
--verbose | Show detailed status including per-file diffs and full provider task data. |
--brief | Single-line per section. Optimized for terminals constrained vertically. |
help, ? | Print the help block and exit 0. |
When neither --verbose nor --brief is supplied, the command prints the standard overview.
Environment variables
Section titled “Environment variables”| Variable | Direction | Purpose |
|---|---|---|
ARGUMENTS | read | Receives the option string when invoked through the slash-command runtime. |
DEBUG | read | When set to 1, enables set -x for the bash body. |
Examples
Section titled “Examples”Standard overview:
/flowforge:dev:statusVerbose overview:
/flowforge:dev:status --verboseSingle-line summary:
/flowforge:dev:status --briefPrint help:
/flowforge:dev:status ?A typical standard overview looks like:
FlowForge Project Status─────────────────────────Git: feature/123-add-cli-reference-page (ahead 2, behind 0) 3 modified, 1 untrackedTests: 152 passed, 0 failed (last run: 6 minutes ago)Time: ticket #123 — 01:42:18 this session, 04:11:05 totalHealth: OKExit codes
Section titled “Exit codes”| Code | Meaning |
|---|---|
0 | Status report completed. The status itself may indicate problems; the exit code does not. |
| Non-zero | A probe failed catastrophically — typically not in a git repository, or a missing dependency for one of the section helpers. The error message identifies which section failed. |
Related commands
Section titled “Related commands”/flowforge:dev:checkrules— run the full rule sweep instead of a status snapshot./flowforge:session:start— start a session if status reports the timer is not running./flowforge:session:end— end the current session.- Sessions — what the time-tracking section reports against.