/flowforge:dev:checkrules

/flowforge:dev:checkrules evaluates the project against the FlowForge rule set defined in .flowforge/RULES.md and prints a per-rule compliance report. It is the manual counterpart to the automatic checks that run as Claude Code hooks on every action.

Synopsis

/flowforge:dev:checkrules [rule-number|help|?]

From outside Claude Code:

flowforge run flowforge:dev:checkrules

Description

A FlowForge project ships with a set of rules — Rule #3 (TDD), Rule #5 (work requires a ticket), Rule #18 (no work on main/develop), Rule #33 (no AI references in git output), and so on. Eight of those rules are enforced automatically on every Claude Code action via hooks. The remaining rules require periodic verification — they are too expensive or too coarse to run on every keystroke.

/flowforge:dev:checkrules runs the full sweep manually. It loads .flowforge/RULES.md, dispatches each rule’s verifier, and prints a structured report indicating which rules pass, which fail, and which warrant a closer look. The command refuses to run outside a FlowForge project: if .flowforge/RULES.md is missing the command exits non-zero and points the user at the project root.

When invoked with a single positional argument that parses as a rule number, the sweep narrows to that rule alone. This is the fast-path workflow: catch a likely violation, confirm it with a targeted check.

Arguments

Position	Name	Required	Description
1	rule-number	no	Rule number to verify in isolation (for example 3 for the TDD rule). When omitted, all rules are checked. The literal values ? and help print an in-terminal usage block and exit 0.

Options

None. The command is positional-only.

Environment variables

Variable	Direction	Purpose
ARGUMENTS	read	Receives the rule number when invoked through the slash-command runtime.
DEBUG	read	When set to 1, enables set -x tracing.

Examples

Run the full rule sweep:

/flowforge:dev:checkrules

Check Rule #3 (TDD) only:

/flowforge:dev:checkrules 3

Check Rule #18 (no work on main/develop) only:

/flowforge:dev:checkrules 18

Print the help block:

/flowforge:dev:checkrules help

A typical full sweep produces output of this shape:

FlowForge Rule Compliance Report
────────────────────────────────
Rule #1   Documentation Organization     PASS
Rule #2   Three Options Before Implement  PASS
Rule #3   TDD First                       PASS  (152/152 tests)
Rule #5   Work Requires Ticket            PASS  (ticket #123)
Rule #18  No Work on main/develop         PASS  (branch: feature/123-...)
Rule #33  No AI References in Git Output  PASS
...
35 rules checked. 0 failures, 0 warnings.

Exit codes

Code	Meaning
0	Sweep completed; report generated. The exit code does not indicate whether all rules passed — read the report.
1	Precondition failed. Most commonly: .flowforge/RULES.md not found because the command was invoked outside a FlowForge project.

Related commands

• /flowforge:dev:status — lighter-weight project snapshot.
• /flowforge:session:start — many rules are easier to satisfy when a session is active.
• Maestro Pattern — Rule #35 mandates agent usage; the sweep reports it.
• Sessions — Rule #5 and Rule #18 are session-shaped.