auto">Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed July 4, 2026, 10:40 PM ET / 02:40 UTC.

Summary
Keep open: current main has first-class Sheets conditional formatting for boolean rules, but the add path still cannot create a gradientRule, and no duplicate or merged fix owns that remaining feature.

Reproducibility: not applicable. as a bug reproduction; this is a feature request. Source inspection gives high confidence that current main lacks a gradientRule add path because the planner only builds BooleanRule conditional format requests.

Ways to help us reproduce this

Add a screenshot or short recording showing the behavior.
Add expected vs actual behavior.
Share version, platform, channel/provider, and relevant config details.

Next step
This is a focused feature candidate because the affected Sheets conditional-format planner, CLI command, docs, and tests are clear.

Review details

Best possible solution:

Extend sheets conditional-format with a narrow gradient-rule JSON path that preserves existing boolean-rule behavior, updates docs/generated command docs, and includes unit, dry-run, and live Google validation.

Do we have a high-confidence way to reproduce the issue?

Not applicable as a bug reproduction; this is a feature request. Source inspection gives high confidence that current main lacks a gradientRule add path because the planner only builds BooleanRule conditional format requests.

Is this the best way to solve the issue?

Yes: extending the existing sheets conditional-format command is the narrowest maintainable direction. A general values batch-update command does not cover the spreadsheet formatting request needed here.

AGENTS.md: found and applied where relevant.

Remaining risk / open question:

The issue body is empty, so the exact CLI shape for accepting gradient definitions should follow existing --*-json patterns unless a maintainer wants a higher-level shortcut API.
Live Google Sheets proof will be needed before merge because the feature depends on spreadsheets.batchUpdate behavior.

Codex review notes: model internal, reasoning high; reviewed against c0aac99f6be6.

Label changes

Label changes:

add P3: This is a low-risk feature request for an existing Sheets command family, with limited blast radius and no evidence of a blocked user workflow.
add issue-rating: 🦞 diamond lobster: Current issue advisory state selects this label.
add clawsweeper:source-repro: Current issue advisory state selects this label.
add clawsweeper:queueable-fix: Current issue advisory state selects this label.
add clawsweeper:fix-shape-clear: Current issue advisory state selects this label.

Label justifications:

P3: This is a low-risk feature request for an existing Sheets command family, with limited blast radius and no evidence of a blocked user workflow.

Evidence reviewed

Acceptance criteria:

go test ./internal/sheetsconditional ./internal/cmd -run 'SheetsConditional|SheetsAdvanced'
make docs-commands
make fmt

What I checked:

Repository policy read: AGENTS.md was read fully before review; its Sheets/testing/output guidance applies to the repair path. (AGENTS.md:1, c0aac99f6be6)
Current command shape only exposes boolean-rule inputs: SheetsConditionalAddCmd requires --type and --format-json, parses a CellFormat, and calls BuildAddRequest; there is no gradient-rule input path. (internal/cmd/sheets_conditional.go:23, c0aac99f6be6)
Planner constructs only BooleanRule: BuildAddRequest creates sheets.ConditionalFormatRule{BooleanRule: ...} and never sets GradientRule, so the requested API field is not implemented on main. (internal/sheetsconditional/conditional.go:54, c0aac99f6be6)
Docs list only boolean conditional shortcuts: The Sheets formatting docs list text, number, blank, not-blank, and custom-formula shortcuts, with no gradient conditional format example or flag. (docs/sheets-formatting.md:88, c0aac99f6be6)
No raw spreadsheet batch-update escape hatch found: The existing sheets batch-update command is documented as a values batch update, not a general spreadsheets.batchUpdate request path that could cover addConditionalFormatRule.gradientRule. (docs/commands/gog-sheets-batch-update.md:5, c0aac99f6be6)
Vision fit: VISION.md says small useful primitives in already-supported Workspace areas, including Sheets, fit the project, while live Google proof is expected for API behavior. (VISION.md:12, c0aac99f6be6)

Likely related people:

Peter Steinberger: Current-main blame and history show the Sheets conditional-format implementation, docs, and v0.32.0 release commit on this path under this author. (role: recent area contributor; confidence: high; commits: f20a26cd9e26, c0aac99f6be6; files: internal/cmd/sheets_conditional.go, internal/sheetsconditional/conditional.go, docs/sheets-formatting.md)
codBang: The historical conditional-format/banding proposal at feat(sheets): add conditional-format, banding, and chart list commands #378 covered the same Sheets formatting command family, and the release notes credit that work even though the submitted PR closed unmerged. (role: adjacent feature proposer; confidence: medium; commits: c3699717a3ff; files: internal/cmd/sheets.go, internal/cmd/sheets_advanced.go)

How this review workflow works

ClawSweeper keeps one durable marker-backed review comment per issue or PR.
Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
Maintainers can also comment @clawsweeper review to request a fresh review only.
Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

Uh oh!

gog sheets should support conditional formatting with gradients (gradientRule) #900

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions

gog sheets should support conditional formatting with gradients (`gradientRule`) #900