korean-writing-refiner

Refines Korean sentences for clarity, natural phrasing, and structural consistency in publishable text.

111|73|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/autopus-ai/autopus-adk --skill korean-writing-refiner-autopus-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: korean-writing-refiner
Source: https://github.com/autopus-ai/autopus-adk/tree/main/.omp/skills/korean-writing-refiner
Command: npx skills add https://github.com/autopus-ai/autopus-adk --skill korean-writing-refiner-autopus-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Korean text written by developers or translated from English often suffers from translationese, noun-heavy phrasing, particle misuse, awkward loanwords, and unclear subject-predicate relationships. This Skill polishes such sentences into natural, clear final copy that readers can understand immediately. ## Core Features & Use Cases - Translationese and noun-phrase reduction: Converts action-noun constructions into verb-centered sentences and breaks up chained possessives like -의 and -에 대한. - Structural and semantic checks: Fixes subject-predicate mismatches, parallel structure errors in comparisons, tense scope issues, and redundant expressions while strictly preserving original meaning. - Document-type tone control: Applies appropriate tone and sentence endings for READMEs, PR bodies, GitHub comments, commit messages, UI strings, and error messages. - Use Case: Before publishing a GitHub issue or PR description written in Korean, run this Skill to produce a polished final version with consistent tone and no awkward phrasing. ## Quick Start Refine this Korean PR description so it reads naturally and uses a consistent 합니다체 tone.

Frequently Asked Questions about korean-writing-refiner

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

FAQPage Schema
How do I fix awkward Korean sentences translated from English?▼

Identify translationese patterns such as chained possessives (-의), phrases like -에 대한 and -를 위한, and action nouns followed by empty verbs. Rewrite them as verb-centered sentences and split long sentences so the subject-predicate relationship stays clear.

How to polish Korean text for GitHub issues and pull requests?▼

Use a neutral 합니다체 for PR and issue bodies, keep commit messages short with non-conclusive endings, and ensure terminology stays consistent across the document. Preserve the original meaning and avoid adding emphasis or scope changes not present in the source.

When should Korean writing refinement not be applied?▼

Skip refinement when the request is analysis-only, such as PR reviews, issue analysis, strategy summaries, or feedback without edits. It also does not apply to code writing, debugging, refactoring, or test authoring where prose is not the deliverable.

Does Korean text refinement change the original meaning?▼

No, meaning preservation is the top priority. If a stylistic improvement would alter the original meaning, the change is withheld, and no new emphasis, hedging, or scope narrowing is added beyond the source text.

What tone should Korean UI strings and error messages use?▼

UI labels, buttons, and menus use short non-conclusive forms with consistent tone within a screen. Error messages and help text default to 합니다체 and should state the problem, possible cause, and next action.