openpyxl-merged-cell-safe-write
Safe pattern for writing values to merged cells in openpyxl spreadsheets
- License 许可
- MIT
- 所属仓库
- HKUDS/AgentPilot
- 最近更新
- 2026-11-12
- Stars
- ★ 8.0k
- Forks
- 944
01 前言 Front Matter
- name
- openpyxl-merged-cell-safe-write
- description
- Safe pattern for writing values to merged cells in openpyxl spreadsheets
02 资源文件 1
- 其他.skill_id45 B
03 SKILL.md 正文
OpenPyXL Merged Cell Safe Write Pattern
Problem
When creating formatted spreadsheets with openpyxl, merging cells and then assigning values to them causes MergedCell errors. This is a common pitfall that can consume multiple failed iterations.
Core Rule
Always assign values to the top-left cell of a merge range BEFORE applying the merge, or avoid assigning to merged cells entirely after the merge is applied.
Correct Pattern
from openpyxl import Workbook
wb = Workbook()
ws = wb.active
# CORRECT: Set value first, then merge
ws['A1'] = 'Quarterly Revenue Report' # Assign to top-left cell first
ws.merge_cells('A1:D1') # Then apply merge
# Also set formatting after merge
ws['A1'].font = Font(bold=True, size=16)
ws['A1'].alignment = Alignment(horizontal='center')
Incorrect Pattern (Causes MergedCell Error)
# WRONG: Merge first, then assign value
ws.merge_cells('A1:D1')
ws['A1'] = 'Quarterly Revenue Report' # This raises MergedCell error!
Step-by-Step Procedure
- Identify merge ranges you need for headers, titles, or grouped data
- Write values to the top-left cell of each range before merging
- Apply the merge using
ws.merge_cells() - Apply formatting (font, alignment, borders) to the top-left cell
- Verify by checking that only the top-left cell holds the value
Additional Guidelines
For Multiple Merged Regions
# Define all merges with their values
merges = [
('A1', 'D1', 'Quarterly Revenue Report'),
('A3', 'B3', 'Product'),
('C3', 'D3', 'Sales Data'),
]
for start_col, end_col, value in merges:
cell_ref = f'{start_col}' # Top-left cell
ws[cell_ref] = value # Set value first
ws.merge_cells(f'{start_col}:{end_col}') # Then merge
When Modifying Existing Merged Cells
If you need to update a value in an already-merged range:
# Get the top-left cell of the merged range
top_left = 'A1' # Know your merge structure
ws[top_left] = 'New Value' # Only modify the top-left cell
Checking for Merged Cells
# Check if a cell is within a merged range
def is_cell_merged(ws, cell_ref):
for merged_range in ws.merged_cells.ranges:
if cell_ref in merged_range:
return True
return False
# Or check before writing
if not is_cell_merged(ws, 'A1'):
ws['A1'] = 'Value'
ws.merge_cells('A1:D1')
Common Use Cases
| Use Case | Pattern |
|---|---|
| Title headers | Write to A1, then merge A1:D1 |
| Section headers | Write to first cell, then merge across columns |
| Grouped labels | Write to top-left, merge the group range |
| Centered content | Write, merge, then apply center alignment |
Quick Reference
# ✅ DO: Value → Merge → Format
ws['A1'] = 'Title'
ws.merge_cells('A1:E1')
ws['A1'].alignment = Alignment(horizontal='center')
# ❌ DON'T: Merge → Value
ws.merge_cells('A1:E1')
ws['A1'] = 'Title' # Error!
Testing Your Spreadsheet
After creation, verify merged cells work correctly:
# Save and reload to confirm no errors
wb.save('test.xlsx')
# Reload and check
wb2 = load_workbook('test.xlsx')
ws2 = wb2.active
print(ws2['A1'].value) # Should show the title value
04 同仓库更多 Skills
agentpilot
Set up AgentPilot and use its single entry to prepare missing inputs and run configured RSI experiments. Use when the user requests AgentPilot installation or work with AgentPilot.
remember
Review auto-memory entries and propose promotions to OPENSPACE.md, OPENSPACE.local.md, or retained auto-memory topics; detect duplicates, stale facts, conflicts, and ambiguous entries before making changes.
skill-discovery
Search reusable OpenSpace skills locally, and browse cloud packages step by step when a cloud skill may help. Reusing proven skills saves tokens, improves reliability, and extends your capabilities beyond built-in tools.
delegate-task
Delegate tasks to OpenSpace — a full-stack autonomous worker for coding, DevOps, web research, and desktop automation, backed by an extensive MCP tool and skill library. Skills auto-improve through use, reducing token consumption over time. A cloud community lets agents share and collectively evolve reusable skills.
write-special-chars-ts-check
Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, plus a reliable TypeScript type-checking step that filters output to only the newly-written files to avoid being misled by pre-existing errors.
write-special-chars-readback
Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, with mandatory post-write verification via read_file and cleanup of /tmp helper scripts.