Skip to content

[PF-21] Strengthen append-i18n prompt for plan language detection - #28

Merged
chucoding merged 2 commits into
developfrom
bugfix/PF-21
Mar 14, 2026
Merged

[PF-21] Strengthen append-i18n prompt for plan language detection#28
chucoding merged 2 commits into
developfrom
bugfix/PF-21

Conversation

@chucoding

Copy link
Copy Markdown
Owner

Purpose

Clarify how the plan’s output language is chosen so that code snippets and technical identifiers (often in English) do not cause the plan to be written in English when the user’s main language is something else (e.g. Korean).

Description

  • packages/core/prompts/append-i18n.md

    • Kept the existing instruction: write the entire plan in the same language as the user’s goal.
    • Added a “Determining the target language” block with four rules:
      1. Exclude from detection: English from code snippets, variable/function names, file paths, technical identifiers, or copied text must not alone decide the language.
      2. Natural language only: Among the natural-language parts of the user’s goal, the target is the most frequently used language.
      3. All-English case: If the goal is entirely in English as natural language, then English is the target.
      4. Mixed content: Do not treat “mixed with code” as “English goal”; prefer the user’s main natural language when it is clearly present.
  • Notion (다국어 지원)
    Documented this change in a new section “4. 계획서 언어 결정(append-i18n) 보강” (background, rules table, and modified file).

How to test

  1. Run plan with a goal that mixes Korean (or another language) natural text and English code/identifiers (e.g. file paths, function foo()).
  2. Confirm the generated plan (headings and body) is in the user’s main natural language (e.g. Korean), not in English.
  3. Run plan with a goal written fully in English; confirm the plan is in English.

Review Requirement

  • Check that the new bullets in append-i18n.md are clear and that the “exclude code/identifiers” rule is easy to apply for model behavior.

Additional Info

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@chucoding chucoding self-assigned this Mar 14, 2026
@chucoding chucoding added the bug Something isn't working label Mar 14, 2026
@chucoding
chucoding merged commit eff658f into develop Mar 14, 2026
1 check passed
@chucoding
chucoding deleted the bugfix/PF-21 branch March 14, 2026 14:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant