Merge School

Merge School Entries

You help the user merge school entries in data/school.txt that were incorrectly split into separate records. Always merge into the earlier-appearing entry (lower line number), adding unique aliases from the later entry, then marking the later entry as invalid with ,,.

Data Format

Each non-comment, non-empty line has comma-separated fields:

省份,城市,正式名称,别名1,别名2,...

• Lines starting with # are comments.
• The first three fields are required: province, city, official name.
• All subsequent fields are aliases (can be empty or numerous).
• A line containing only ,, is an invalid/deprecated entry — the parser skips it.

Example:

湖南,长沙市,长沙市雅礼中学,湖南省长沙市雅礼中学,湖南省长沙雅礼中学,长沙雅礼中学,雅礼中学

How Merging Works

When two lines represent the same school:

1. Keep the earlier entry (lower line number) — it becomes the primary.
2. Collect unique aliases from the later entry: its official name (if different from the primary's) plus all its aliases not already present in the primary.
3. Append unique aliases to the end of the primary line, comma-separated.
4. Mark the later entry as invalid by replacing the entire line content with ,,.

The primary's province, city, and official name are never changed. If the two entries have different cities, flag this to the user — it may mean they are genuinely different schools.

Pre-step: Fetch issue context (if applicable)

If the user provides a GitHub issue number (e.g., "merge school #123"), fetch it first:

gh issue view <number>

Extract school names, line numbers, provinces, and any merge instructions. Proceed to Step 1 with all collected information.

Workflow

Step 1: Locate the schools

From the user's input, extract school names or hints. Use grep with line numbers to find candidates — never read the entire file:

grep -n '学校名' data/school.txt

For more precise matching on the official name (3rd field):

awk -F',' '!/^#/ && $3=="正式名称" {print NR": "$0}' data/school.txt

To search across all fields (name or alias):

grep -n '关键词' data/school.txt

Step 2: Identify and assess

Review all matching lines. Determine:

• Which lines represent the same school (duplicates/incorrectly split).
• Which is the earlier entry (lower line number) — this will be the merge target.
• Whether province and city match. If cities differ, surface this to the user before proceeding.
• What aliases the later entry has that the earlier entry lacks.

Step 3: Propose the merge plan

Present a clear summary showing both entries in full, then propose:

• Primary (keep): earlier entry (line N) — show full content.
• Secondary (invalidate): later entry (line M) — show full content.
• Aliases to add: list the names from the secondary not already in the primary.
• Result: show what the merged primary line will look like after the change.

If the two entries have conflicting province/city, or if it's unclear they are the same school, ask the user for clarification.

Use AskUserQuestion to confirm the plan before making any changes. Never proceed without explicit user approval.