Skip to content

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

Open
zhengzhijiej-tech wants to merge 1 commit into
feat/lark-sheets-developfrom
feat/sheet-eval-guidance-fixes
Open

docs(sheets): strengthen lark-sheets references for common editing pitfalls#1296
zhengzhijiej-tech wants to merge 1 commit 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
Copy link
Copy Markdown

coderabbitai Bot commented Jun 5, 2026

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: 599e8047-3484-42eb-8019-a7242bb47499

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
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