My First Open Source PR: How a Korean README Fix Merged in Under an Hour

Description and use

The author fixed Korean README drift in oh‑my‑opencode‑slim by filing an issue first and submitting a single‑file PR, which merged in under an hour, illustrating a low‑risk entry path for new contributors.

Problem

The Korean README of oh‑my‑opencode‑slim was out of sync with the English version, causing confusion for Korean users.

Outcome

The Korean README was synchronized with the English version in a single PR, merged in under an hour, demonstrating a low‑risk, documentation‑only contribution path.

Workflow

• 1. Opened issue #1422 listing specific drift items and referencing prior sync efforts.
• 2. Waited for maintainer response (none).
• 3. Opened PR #1423 with a single file change, +149/-132 diff.
• 4. Ran local checks (git diff --check, link verification).
• 5. Addressed bot review finding about Council keyword.
• 6. Maintainer merged PR within 59 minutes.

Evidence

The Korean README had fallen behind the English one. The gaps weren't dramatic, but they added up: Setup instructions still described a --skills=force command and installer-managed skill updates that no longer matched how the plugin handles bundled skills.

Source

I opened issue #1422 first. The issue did four things: It itemized the drift. It showed history. It set the scope. It claimed the work.

Source

The translation itself took not that long. The interesting constraint wasn't vocabulary, it was voice.

Source

Issue to merge: 59 minutes.

Source