fix(commands): translate /pf:help body to English (narrow partial #113)#118
fix(commands): translate /pf:help body to English (narrow partial #113)#118
Conversation
Scope narrowed from the original #113 to just commands/help.md, the only command whose Korean prose actually leaks into user-visible output (per the original bug report screenshot). The other 14 command files stay Korean for now — Layer-0 Rule 10 in methodology/global.md already enforces English output regardless of command-body language, so the visible-leak surface for those is nearly zero, and translating them carries non-trivial behavior-change risk (each body acts as a system prompt for Claude when its slash command runs, with no end-to-end behavioral test suite to catch subtle drift). Also updates the help.md "What's new" section that was frozen at v1.10.0 — now covers v1.11 (defense-in-depth + regex hardening), v1.12 (cinematic preview + auto-rec + reference example), v1.13 (H1 → SpecDD auto-advance, H2 → preview-server auto-launch, new /pf:preview), v1.14 (Rule 10 + default-profile fix). The section ends with a maintenance pointer to CHANGELOG.md so future releases get reflected without ad-hoc edits. The "14 commands" count in help.md is corrected to 15 (matches the v1.13 addition of /pf:preview). Layer-0 Rule 10 enforcement, single-file change, low blast radius. #113 stays open for a follow-up that translates the remaining 13 command bodies after a proper behavioral regression pass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 9 minutes and 38 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request translates the help.md documentation for the preview-forge plugin from Korean to English and updates the "What's new" section to reflect changes through version 1.14.1. Review feedback identifies several documentation inconsistencies, including a reference to a non-existent FAQ section, mismatches between the version descriptions and the plugin's changelog, and an incorrect relative path for the changelog link.
| ## Behavior | ||
|
|
||
| 14 명령어 요약 + 자주 묻는 질문 (FAQ). | ||
| Summary of the 15 commands plus a frequently asked questions (FAQ) section. |
There was a problem hiding this comment.
The behavior description mentions a "frequently asked questions (FAQ) section", but no such section exists in this file. Additionally, while the command count is correctly updated to 15 here, plugins/preview-forge/README.md still references "14 slash commands" (line 13). Documentation designated as an authoritative source must be free of errors to maintain credibility and trustworthiness.
| Summary of the 15 commands plus a frequently asked questions (FAQ) section. | |
| Summary of the 15 commands. |
References
- Documentation designated as an 'authoritative source' must be free of errors, including typos, to maintain its credibility and trustworthiness.
| ## What's new (through semver v1.14.1) | ||
|
|
||
| > "v1.6 audit" · "v1.7 audit"은 ComBba feature umbrella 이름이고, 실제 release tag는 release-please가 Conventional Commits로 자동 부여한 v1.6.0·v1.10.0 등 semver. 자세한 매핑은 [CHANGELOG.md](../../../CHANGELOG.md) 참조. | ||
| > "v1.6 audit" / "v1.7 audit" are ComBba feature umbrella names; the actual release tags are the semver values that release-please assigns from Conventional Commits (v1.6.0, v1.10.0, v1.14.1, and so on). For the per-tag mapping see [CHANGELOG.md](../../../CHANGELOG.md). |
There was a problem hiding this comment.
There are several inconsistencies between this section and the plugins/preview-forge/CHANGELOG.md:
- Version Mismatch: The changelog currently ends at
1.11.0, but this file referencesv1.14.1as a completed release. - Content Mismatch: The description for
v1.11here ("Defense-in-depth + regex hardening") does not match the changelog entry for1.11.0("Phase 8 — Requirements Expansion"). Per repository rules, explicitly document the mapping between internal feature names (like 'Phase 8') and semantic versioning tags to prevent confusion. - Changelog Link: The link points to the root
CHANGELOG.md(../../../CHANGELOG.md), but the plugin-specificplugins/preview-forge/CHANGELOG.md(../CHANGELOG.md) contains the detailed feature umbrella mappings mentioned in the text. Consider linking to the plugin-specific changelog instead.
References
- To prevent confusion from versioning inconsistencies, explicitly document the distinction between internal feature/audit names and the final semantic versioning tags, and clarify their mapping in relevant documentation.
1 participant
Summary
Narrows the original #113 scope to a single file:
plugins/preview-forge/commands/help.md. This is the one command whose Korean prose actually leaks into user-visible output (per the bug report screenshot of/pf:helpin the issue body). The other 14 command bodies stay Korean for now and are deferred to a follow-up PR with proper behavioral regression coverage.Why narrowed (risk argument)
Each
commands/*.mdbody is loaded by Claude Code as a system prompt when its slash command runs. Translating prose changes the system prompt, which can change Claude's behavior in subtle ways (different reasoning, different tool calls, different output formatting). There is no end-to-end behavioral test suite for these commands today, so a 15-file translation lands with no rollback signal short of manual e2e testing per command.Meanwhile, Layer-0 Rule 10 (
Output language: English, inplugins/preview-forge/methodology/global.md) already enforces English output regardless of command-body language. So the visible-Korean-leak surface for the 14 non-help commands is near zero.Marginal benefit of translating the 14 remaining commands: small. Marginal risk: real. Decision: ship the one file that actually has a user-visible leak (
/pf:helprendering Korean tables per the original screenshot), defer the rest.Resolves
Partially closes #113. The issue stays open for a follow-up PR that translates the remaining 13 command bodies after end-to-end behavioral testing.
Changes
plugins/preview-forge/commands/help.md:/pf:previewslash command added in v1.13).This section is regenerated each release; see CHANGELOG.md for the canonical per-tag mapping.Test plan
bash scripts/verify-plugin.shpasses locally (59/59)help.mdreturns 0 charactersgit show origin/main:plugins/preview-forge/commands/help.md)Notes for reviewers
The original #113-scope PR (#117) was closed in favor of this narrowed PR. The rationale is documented in #117's close comment and in the commit body of
edaac42.The remaining 13 command bodies (Korean) are tracked under #113. A follow-up PR can translate them once we have behavioral regression coverage — at that point the risk of subtle prompt drift is bounded.