Skip to content

docs(sheets): strengthen lark-sheets references for common editing pitfalls#1296

Merged
zhengzhijiej-tech merged 4 commits into
feat/lark-sheets-developfrom
feat/sheet-eval-guidance-fixes
Jun 8, 2026
Merged

docs(sheets): strengthen lark-sheets references for common editing pitfalls#1296
zhengzhijiej-tech merged 4 commits into
feat/lark-sheets-developfrom
feat/sheet-eval-guidance-fixes

Conversation

@zhengzhijiej-tech

Copy link
Copy Markdown
Collaborator

What

Strengthens six lark-sheets skill references with targeted guidance for common spreadsheet-editing pitfalls observed when driving sheets through the CLI. Documentation-only — no code or schema changes.

Changes

  • write-cells — sanity-check units / dimension conversion / quantity factors before formula writes (a formula can run clean yet be off by a constant factor); keep derived output off original data columns to avoid clobbering source data.
  • core-operations — prefer live formulas for derived values even when "live update" isn't explicitly stated; scope rewrite/transform precisely so rows/columns that should stay unchanged are kept 1:1; treat header-stated format rules as checklist items; confirm the artifact file actually exists before finishing; write back bare values from local scripts.
  • visual-standards — apply border/header formatting on explicit request and identify the real header row; keep font size consistent with the source.
  • range-operations — keep total column width within A4 for printing.
  • read-data — dedup/compare long numbers via raw values rather than CSV formatted display (scientific notation collapses distinct numbers and causes false duplicates).
  • chart — format date/number axes via source-cell number_format; place charts outside the data area so they don't cover existing data.

…tfalls

Add targeted guidance to six lark-sheets references to reduce frequent
mistakes when editing spreadsheets through the CLI:

- write-cells: sanity-check units / dimension conversion / quantity factors
  before formula writes (formulas can run clean yet be off by a factor);
  keep derived output off original data columns to avoid clobbering source
- core-operations: prefer live formulas for derived values even when "live
  update" is not explicitly requested; scope rewrite/transform precisely so
  rows/columns that should stay unchanged are kept 1:1; treat header-stated
  format rules as checklist items; confirm the artifact file actually exists
  before finishing; write back bare values from local scripts
- visual-standards: apply border/header formatting on explicit request and
  identify the real header row; keep font size consistent with the source
- range-operations: keep total column width within A4 for printing
- read-data: dedup/compare long numbers via raw values, not csv formatted
  display (scientific notation collapses distinct numbers and causes false
  duplicates)
- chart: format date/number axes via source-cell number_format; place charts
  outside the data area so they do not cover existing data
@coderabbitai

coderabbitai Bot commented Jun 5, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 987d5934-ed4e-4043-b89e-3b83c3054c4a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/sheet-eval-guidance-fixes

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions github-actions Bot added the size/M Single-domain feat or fix with limited business impact label Jun 5, 2026
…ested metric

- range-operations: only widen new / overflowing columns; never recompute or
  shrink the widths of existing columns (any blanket resize, even by 1px,
  breaks the original visual format)
- chart: when the user asks for a share / percentage, the value axis should be
  a percentage (pie, or stack.percentage on bar/column) rather than raw counts
Replace scoring-framework wording in the examples with plain functional
consequences (e.g. "not delivered", "goes stale when the source changes",
"breaks the original visual format"), so the references stay agent-facing.
Bring the hand-applied write-cells example in line with the spec-generated
reference so the CLI mirror is byte-identical to the canonical source.
@zhengzhijiej-tech
zhengzhijiej-tech merged commit 02a3702 into feat/lark-sheets-develop Jun 8, 2026
3 checks passed
@zhengzhijiej-tech
zhengzhijiej-tech deleted the feat/sheet-eval-guidance-fixes branch June 8, 2026 11:13
xiongyuanwen-byted pushed a commit that referenced this pull request Jun 22, 2026
docs(sheets): strengthen lark-sheets references for common editing pitfalls
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/M Single-domain feat or fix with limited business impact

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant