skills.rest
aleen42
aleen42COMMUNITY
Explore all skills by this author →
Website𝕏@aleen42GitHub

trim-related-i18n-diffs

Filter uncommitted locale file diffs to match baseline zh_CN.js key changes.

3|Updated Feb 14, 2026
Search Tags:#git#localization#diff#i18n#baseline#keys
One-click install
npx skills add https://github.com/aleen42/PersonalContext --skill trim-related-i18n-diffs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trim-related-i18n-diffs
Source: https://github.com/aleen42/PersonalContext/tree/main/skills/trim-related-i18n-diffs
Command: npx skills add https://github.com/aleen42/PersonalContext --skill trim-related-i18n-diffs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps translation updates in sync with a baseline Chinese file by filtering out unrelated edits across sibling locale files.

Core Features & Use Cases

  • Diff-based filtering: Identify and apply only the keys that changed in the baseline zh_CN.js.
  • Cross-file trimming: Remove uncommitted edits from other locale files in the same directory that do not map to the baseline changes.
  • Safety & integrity: Preserve the HEAD state for unchanged keys and correctly handle added, removed, or renamed keys.

Quick Start

Provide the baseline zh_CN.js diff range and run the trim to keep only still-uncommitted changes that correspond to that baseline.

Frequently Asked Questions about trim-related-i18n-diffs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep only i18n changes across locale files that match a baseline zh_CN.js diff?▼

To keep only matching i18n changes, provide the baseline zh_CN.js diff range to filter uncommitted edits across sibling locale files, discarding unrelated changes while preserving HEAD state for unchanged keys.

How does cross-file diff trimming handle added, deleted, or renamed i18n keys?▼

Cross-file diff trimming enforces key-based changes by mapping additions, deletions, and renames against the baseline modification, ensuring sibling locale files reflect only the relevant semantic key updates.

Do I need to provide a git diff range to filter uncommitted localization changes?▼

Yes, you need to provide a baseline zh_CN.js diff range so the trim operation can identify and preserve only the still-uncommitted i18n changes that semantically correspond to that baseline across locale files.

What is the best way to remove unrelated uncommitted edits from sibling locale files?▼

The best way to remove unrelated uncommitted edits is cross-file trimming against a baseline zh_CN.js diff, which produces a minimal diff reflecting only relevant keys while maintaining HEAD integrity.

Can I narrow git diffs to only reflect i18n keys modified in a baseline file?▼

Yes, you can narrow git diffs to only reflect i18n keys modified in a baseline file by applying key-based filtering, which ensures unchanged keys retain their HEAD state across all sibling locale files.

Related Skills

Explore More Software Engineering Skills→
Alex1980AlexAlex1980Alex

db-load-git

Load changed 1C configuration files from Git into a target database.

Community
Advanced
Arbab1308Arbab1308

i18n-localization

No, I won't help with that.

Community
Intermediate
fnsalinasfnsalinas
1

i18n-localization

Audits React, Vue, Python codebases for hardcoded strings and missing translations.

Community
Intermediate
FriendlyInternetFriendlyInternet
10

i18n-check

Scan changed files for hardcoded labels and missing locale keys.

Official
Intermediate