Elgato_dark/lobehub
1
0
Fork 0
mirror of https://github.com/lobehub/lobehub synced 2026-04-21 09:37:28 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 70
lobehub/.claude/prompts/translate-comments.md
Innei 8b3c871d08
♻️ refactor(onboarding): add OnboardingContextInjector and wire context engine (#13518) 
* ♻️ refactor(onboarding): add OnboardingContextInjector and wire context engine

Made-with: Cursor

* 🔧 refactor(onboarding): update tool call references to use `lobe-user-interaction________builtin`

Modified onboarding documentation and utility functions to standardize the use of the `lobe-user-interaction________builtin` tool call for structured input collection, enhancing clarity and consistency across the codebase.

Signed-off-by: Innei <tukon479@gmail.com>

* 🔧 refactor(onboarding): standardize tool call references to `lobe-user-interaction____askUserQuestion____builtin`

Updated documentation and utility functions to replace instances of the `lobe-user-interaction________builtin` tool call with `lobe-user-interaction____askUserQuestion____builtin`, ensuring consistency in structured input collection across the onboarding process.

Signed-off-by: Innei <tukon479@gmail.com>

* ♻️ refactor(onboarding): move onboarding context before first user

* ♻️ refactor(context-engine): add virtual last user provider

* update v3

* 🐛 fix(onboarding): add early exit escape hatch for boundary cases

The `<next_actions>` directive only prompted finishOnboarding in the
summary phase, but phase transition required all fields + 5 discovery
exchanges — a condition extreme cases rarely meet. This left the model
stuck in discovery, never calling finishOnboarding.

- Add EARLY EXIT hint in discovery phase next_actions
- Add universal completion-signal REMINDER across all phases
- Add minimum-viable discovery fallback in systemRole
- Add explicit completion signal list in Early Exit section
- Add off-topic redirect limit in Boundaries
- Add CRITICAL persistence rule in toolSystemRole

* ✅ test(context-engine): fix OnboardingContextInjector tests to match BaseFirstUserContentProvider

Remove brittle MessagesEngine onboarding test that hardcoded XML content.

---------

Signed-off-by: Innei <tukon479@gmail.com>
2026-04-07 19:25:16 +08:00

3.5 KiB
Raw Blame History

Code Comment Translation Assistant

You are a code comment translation assistant. Your task is to find non-English comments in the codebase and translate them to English.

Target Directories

  • apps/desktop/src/
  • packages/*/src/
  • src

Workflow

0. Pre-check: Scan Existing Translation PRs

Before selecting a module, MUST scan existing PRs to avoid duplicate work:

  1. List in-flight PRs:

    gh pr list --search "automatic/translate-comments-" --state open --json number,title,headRefName,mergeable

  2. Close conflicting PRs: For any PR where mergeable is "CONFLICTING", close it with a comment:

    gh pr close <number> --comment "Closing: this PR has merge conflicts with main and is outdated. A new translation PR may be created for this module."

  3. Build exclusion list: Extract module names from the remaining open PR branch names (automatic/translate-comments-<module-name>-<date>), and exclude those modules from selection in the next step.

  4. Output summary (for logging):

    • Total open translation PRs found
    • PRs closed due to conflicts
    • Modules currently in-flight (excluded from selection)

1. Select a Module to Process

  • MUST skip modules that already have an open PR (from step 0's exclusion list)

Module granularity examples:

  • A single package: packages/database
  • A desktop module: apps/desktop/src/modules/auth
  • A service directory: src/services/user

2. Find Non-English Comments

  • Search for files containing non-English characters in comments (excluding test files)
  • File types to check: .ts, .tsx
  • Exclude: *.test.ts, *.test.tsx, *.spec.ts, *.spec.tsx, node_modules, dist, build

3. Translate Comments

  • Translate all non-English comments to English while preserving:
    • Code functionality (do not change any code)
    • Comment structure and formatting
    • JSDoc tags and annotations
    • Markdown formatting in comments
  • Translation guidelines:
    • Keep technical terms accurate
    • Maintain professional tone
    • Preserve line breaks and indentation
    • Keep TODO/FIXME/NOTE markers in English

4. Limit Changes

  • CRITICAL: Ensure total changes do not exceed 500 lines
  • If a module would exceed 500 lines, process only part of it
  • Count lines using: git diff --stat
  • Stop processing files once approaching the 500-line limit

5. Create Pull Request

  • Create a new branch: automatic/translate-comments-[module-name]-[date]

  • Commit changes with message format:

    🌐 chore: translate non-English comments to English in [module-name]

  • Push the branch

  • Create a PR with:

    • Title: 🌐 chore: translate non-English comments to English in [module-name]
    • Body following this template:
    ## Summary

- Translated non-English comments to English in `[module-name]`
- Total lines changed: [number] lines
- Files affected: [number] files

## Changes

- [ ] All non-English comments translated to English
- [ ] Code functionality unchanged
- [ ] Comment formatting preserved

## Module Processed

`[module-path]`

---

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Important Rules

  • DO NOT modify any code logic, only comments
  • DO NOT translate non-English strings in code (only comments)
  • DO NOT exceed 500 lines of changes in one PR
  • DO NOT process test files or generated files
  • DO preserve all code formatting and structure
  • DO ensure translations are technically accurate
  • DO verify changes compile without errors