Repository navigation
Define translation agent skill guidelines for Portuguese (pt) locale #62001
Description
Activity
Hi @jason810496, I'd like to take this issue
Please assign it to me if possible. Ready to start working on the pt.md skill file.Hi @jason810496,
Thanks a lot for assigning me!
Just wanted to quickly check if my plan looks good before I open the PR:
- I'll create
.github/skills/airflow-translations/locales/pt.md(matching the structure from Define Translation Agent Skills for Airflow Terminology #61984 and the ongoing add SKILL.md and zh-CN agent skill instruction #62059 for zh-CN/global) - The file will include:
- A short intro about the pt locale and that it's based on the existing JSON files
- Summary/sync with global rules (once SKILL.md lands, or just reference it)
- Specific Portuguese guidelines: correct gender/plural agreement, natural phrasing, preferred spellings/vocab as seen in current files
- A good number of real examples pulled straight from the existing pt/*.json (both kept-English terms like "Dag", "XCom", "Asset" and translated ones like "Tarefa", "Execução do Dag", "Excluir", etc.)
- Clear DOs and DON'Ts section so agents can follow it reliably
Does this direction feel right? Any feedback on the folder name, how much detail to include, or things I should add/remove?
Thanks again!
- I'll create
Feel free to directly submit a draft PR then the current maintainers of Portuguese will give further detailed suggestion about the skill. The overall direction LGTM. Thanks!
- added 4 commits that reference this issue
on Feb 17, 2026 @Jayantparashar10 We are unassigning you from this issue as part of our updated assignment policy.
This is not meant to discourage your contribution — quite the opposite! You are still very welcome to work on this issue and submit a PR for it. Simply comment that you are working on it and open a PR when ready.
We found that formal assignments were not working well, as they often prevented others from contributing when the assignee was not actively working on the issue.
- added a commit that references this issue
on Mar 26, 2026
The context for this issue is described in #61984.