docs(git-master): make language handling generic (incl. Japanese examples)

[s2mr]

Summary

The git-master skill had English/Korean-centric wording throughout its language detection and commit message guidance, making it unclear whether other languages (e.g., Japanese) are supported. This PR makes all language-related guidance fully language-agnostic.

Fixes #3097

Changes

• Mode detection triggers: replaced hardcoded Korean examples with generic "any language" phrasing, adding Japanese examples alongside existing ones
• Language profile detection (Phase 1.1): removed binary Korean/English detection logic; replaced with language-agnostic "dominant language pattern" approach that works for any repository language
• Commit message generation (Phase 5.4): removed KOREAN/ENGLISH branching; now shows multilingual examples (English, Japanese, Korean) as illustrative only
• History search triggers: added Japanese example phrases alongside Korean ones
• Rebase mode triggers: added Japanese example phrases alongside Korean ones
• Quick reference cheat sheet: added Japanese example (xxxを追加) alongside Korean (xxx 추가)
• Synced src/features/builtin-skills/git-master/SKILL.md to match all section-template changes

Testing

• bun test src/features/opencode-skill-loader/git-master-template-injection.test.ts — 10 pass ✅
• bun run typecheck ✅
• bun run build ✅

[github-actions]

All contributors have signed the CLA. Thank you! ✅
_{Posted by the CLA Assistant Lite bot.}

[s2mr]

I have read the CLA Document and I hereby sign the CLA

[cubic-dev-ai]

1 issue found across 6 files

Confidence score: 3/5

• There is some regression risk: src/features/builtin-skills/skills/git-master-sections/commit-workflow.ts appears mid-migration, where new multilingual/profile instructions conflict with legacy single-language validation logic.
• Because this is a concrete behavior mismatch (severity 6/10 with high confidence 9/10), users may hit incorrect validation outcomes until both paths are aligned.
• Pay close attention to src/features/builtin-skills/skills/git-master-sections/commit-workflow.ts - resolve validation/instruction consistency during the language-profile migration.

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="src/features/builtin-skills/skills/git-master-sections/commit-workflow.ts">

<violation number="1" location="src/features/builtin-skills/skills/git-master-sections/commit-workflow.ts:96">
P2: Language-profile migration is incomplete: new multilingual/profile instructions conflict with remaining single-language validation checks.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[cubic-dev-ai]

P2: Language-profile migration is incomplete: new multilingual/profile instructions conflict with remaining single-language validation checks.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At src/features/builtin-skills/skills/git-master-sections/commit-workflow.ts, line 96:

<comment>Language-profile migration is incomplete: new multilingual/profile instructions conflict with remaining single-language validation checks.</comment>

<file context>
@@ -93,7 +93,7 @@ Reference examples from repo:
   3. "actual commit message from log"
 
-All commits will follow: [LANGUAGE] + [STYLE]
+All commits will follow: [DOMINANT_LANGUAGE_OR_SCRIPT] + [STYLE]
 \`\`\`
 
</file context>