Lite Mode Commands

Updated on Oct 5, 2026

Lite mode (--lite) runs a focused, reduced-output version of a workflow operation. Use it for simple changes, quick feedback loops, or CI checks where a full analysis isn't needed.

Supported commands

--lite and --lite-edit are available only on the operations below. The descriptions are the --help text.

Command	`--lite`	`--lite-edit [<INSTRUCTIONS>]`
`frg issue draft`	Generate lightweight draft with essential details only (faster, minimal analysis)	Lightweight draft with edit instructions (fast output + custom refinements)
`frg issue review`	Focused review on actionable items only (gaps, risks, recommendations). Excludes positive observations.	Focused review with edit instructions (actionable items + custom refinements)
`frg issue plan`	Generate lightweight plan with core essentials only (faster, single-phase, no diagrams)	Lightweight plan with edit instructions (fast output + custom refinements)
`frg code review`	Focused review on critical issues only (bugs, security, breaking changes). Reduces token usage by 30-50%.	Focused review with edit instructions (critical issues + custom refinements)
`frg pr draft`	Concise PR description with essential information only. Reduces token usage by 30-50%.	Concise PR description with edit instructions
`frg pr review`	Actionable review feedback only (blocking issues, failing tests, conflicts). Single output file.	Focused PR review with edit instructions

--lite takes no value. --lite-edit takes instructions inline or reads them from a lite-edit.md file. For how instruction files work, see Modifiers.

Other operations, such as issue publish, code create, or pr merge, don't accept --lite.

Run a lite command

bash

frg issue draft --lite
frg issue plan --lite
frg code review --lite
frg pr draft --lite
frg pr review --lite

To add your own instructions, use --lite-edit instead of combining --lite with --edit. Forge accepts only one modifier per run:

bash

frg code review --lite-edit "Focus on performance-critical code paths"
frg issue plan --lite-edit "Include database migration steps"

When to use lite mode

Bug fixes, small features, and configuration or documentation changes.
CI pipelines that need a fast pass or fail signal.
Iterations during development, before you run the full review.

Use the standard mode for security-sensitive code, architectural changes, or reviews where detailed feedback matters. Each run is independent, so you can run frg pr review after frg pr review --lite to get the full output.

How lite output affects later commands

Lite plans

When frg issue plan --lite produces a single-phase plan, Forge detects the lite plan and skips input file validation for the code commands that consume the plan.

Lite PR reviews

frg pr review --lite writes only pr_review.md. A standard review writes five files:

pr_review.md
status_check_fixes.md
code_quality_improvements.md
minor_merge_conflicts.md
high_risk_merge_conflicts.md

frg pr merge always requires pr_review.md. When it detects a lite review, it validates only pr_review.md.

In a standard review, each of the other four files is optional. frg pr merge proceeds from pr_review.md for any file that is missing.

If pr_review.md is missing, Forge prints:

text

Hint: Run 'frg pr review' to generate review files
 Or use 'frg pr review --lite' for a focused review (single file)

Lite mode and app commands

Don't use --lite with frg app commands. The help for direct-execution app commands (for example, frg app code review) states:

text

NOTE: The --lite flag is not supported for app commands.
App commands always use full execution mode.