Review playbook
i18n String Extractor
Finds user-facing strings hard-coded in UI PRs and proposes extraction to the translation catalogue with suggested keys.
On any pull request touching UI code, finds user-facing strings hard-coded in components, distinguishing them from developer-facing strings that should not be translated, log messages, test ids, aria roles, enum keys. Proposes extraction to the translation catalogue with a suggested key following the existing naming convention, and flags concatenated strings and hard-coded plurals, which break translation even after extraction.
- Identifier
i18n-string-extractor- Version
- 1.0.0
- Steps
- 4
- Triggers
- 1
- i18n
- internationalization
- localization
- frontend
- strings
- review
When it runs
pull_request.opened- Settle delay
- 15s after the event
Only when all hold
- pullRequest.isDraft not equals true
- actor.username not in dependabot, dependabot[bot], renovate, renovate[bot], github-actions, github-actions[bot]
- actor.username not contains [bot]
The pipeline
The graph below is the one the workflow opens with in the builder, same steps, same layout, drawn on the same canvas. The run playing through it is a simulation; the branches and conditions are real.
- 01PR Opened
triggerThe event that starts the run.
- 02Clone Repository
git.cloneShallow-clones the repository at the right ref.
- 03Scan for Hard-Coded Strings
agent.runOne agent works the task with its toolkit.
- 04Publish i18n Report
report.publishPosts or updates a deduplicated report comment.
The agent
i18n String Extractor
- Base type
- Code Reviewer
- Temperature
- 0.2
- Max iterations
- 30
- Tools
- 5
Git provider · 2
get_pull_request_diffGet Pull Request Diff · readadd_pull_request_review_threadAdd PR Review Thread · write
Filesystem · 1
read_fileRead File · read
Code search · 1
code_searchCode Search · read
Status · 1
update_statusUpdate Status · write