Docs/add brazilian portuguese translation#736
Merged
affaan-m merged 15 commits intoMar 22, 2026
Conversation
Contributor
|
Contributor
Analysis Failed
Troubleshooting
Retry: |
Contributor
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
📝 WalkthroughWalkthroughAdds Portuguese (pt-BR) localization: README language entries updated and ~60 new pt-BR documentation files (CONTRIBUTING, TERMINOLOGY, agents, commands, examples, rules). All edits are documentation-only; no source code or public API entities changed. Changes
Sequence Diagram(s)(omitted) Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
Contributor
Greptile SummaryThis PR adds a full Brazilian Portuguese ( Key observations:
Confidence Score: 4/5
Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[Root README.md] -->|Language switcher| B[docs/pt-BR/README.md]
B --> C[docs/pt-BR/CONTRIBUTING.md]
B --> D[docs/pt-BR/TERMINOLOGY.md]
B --> E[docs/pt-BR/agents/]
B --> F[docs/pt-BR/commands/]
B --> G[docs/pt-BR/examples/]
B --> H[docs/pt-BR/rules/]
E --> E1[12 agent docs]
F --> F1[18 command docs]
G --> G1[6 example docs]
H --> H1[8 rule docs]
Reviews (5): Last reviewed commit: "Update docs/pt-BR/commands/eval.md" | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
13 issues found across 48 files
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="docs/pt-BR/examples/django-api-CLAUDE.md">
<violation number="1" location="docs/pt-BR/examples/django-api-CLAUDE.md:145">
P1: `select_for_update()` is used outside `transaction.atomic()`, causing `TransactionManagementError` at runtime in Django autocommit mode. The row lock acquisition and stock validation should both happen inside the atomic block to prevent race conditions and runtime errors.</violation>
</file>
<file name="docs/pt-BR/agents/go-build-resolver.md">
<violation number="1" location="docs/pt-BR/agents/go-build-resolver.md:27">
P1: The lint diagnostic commands conflate tool execution failures with lint findings by using `||` which triggers on any non-zero exit code. Both `staticcheck` and `golangci-lint` return non-zero when they find issues, causing the documentation to falsely report "not installed" when tools are actually installed but have findings to report. The rust reviewers in this codebase use a better pattern with `command -v` to check for tool availability.</violation>
</file>
<file name="docs/pt-BR/examples/go-microservice-CLAUDE.md">
<violation number="1" location="docs/pt-BR/examples/go-microservice-CLAUDE.md:184">
P1: Test example missing mock expectation verification with AssertExpectations - allows silent test passes when expected calls are not made</violation>
</file>
<file name="docs/pt-BR/commands/tdd.md">
<violation number="1" location="docs/pt-BR/commands/tdd.md:40">
P1: Nested fenced code blocks require longer outer fence: change opening ``` to ```` (four backticks) to prevent inner code blocks from breaking the outer container</violation>
</file>
<file name="docs/pt-BR/agents/doc-updater.md">
<violation number="1" location="docs/pt-BR/agents/doc-updater.md:99">
P2: A seção `## Quando Atualizar` está incompleta/truncada - o arquivo termina imediatamente após o título sem conteúdo. Comparando com o arquivo-fonte em inglês (agents/doc-updater.md), esta seção deveria conter orientações sobre quando executar atualizações (ALWAYS para novas funcionalidades, mudanças de API, etc. e OPTIONAL para correções menores).</violation>
</file>
<file name="docs/pt-BR/commands/go-review.md">
<violation number="1" location="docs/pt-BR/commands/go-review.md:67">
P2: Nested fenced code block has inconsistent fence length (4 backticks to open, 3 to close). The closing fence should match the 4-backtick opening when containing nested code blocks.</violation>
</file>
<file name="docs/pt-BR/commands/build-fix.md">
<violation number="1" location="docs/pt-BR/commands/build-fix.md:17">
P2: The `python -m py_compile` command is missing required file arguments. `py_compile` requires filenames as positional arguments; without them it exits with a usage error.</violation>
<violation number="2" location="docs/pt-BR/commands/build-fix.md:54">
P2: The 'Estratégias de Recuperação' table contains English headers ('Situation', 'Action') and all English content instead of Portuguese. For consistency with other translations (zh-CN, ko-KR) and the PR goal of complete Brazilian Portuguese localization, this table should be fully translated.</violation>
</file>
<file name="docs/pt-BR/commands/go-build.md">
<violation number="1" location="docs/pt-BR/commands/go-build.md:44">
P1: Nested fenced code blocks require longer outer fence delimiter</violation>
</file>
<file name="docs/pt-BR/agents/refactor-cleaner.md">
<violation number="1" location="docs/pt-BR/agents/refactor-cleaner.md:80">
P2: The 'Métricas de Sucesso' section is empty and missing the success metrics content that exists in other language translations (Chinese and Korean variants contain 4 bullet points: all tests pass, build succeeds, no regressions, bundle size reduced). This indicates an incomplete/truncated translation that removes expected operational guidance for evaluating agent task completion.</violation>
</file>
<file name="docs/pt-BR/CONTRIBUTING.md">
<violation number="1" location="docs/pt-BR/CONTRIBUTING.md:103">
P2: Nested code blocks should use longer outer fences (````) instead of escaped backticks. The escaped backticks will render as literal backslashes in the documentation, causing invalid markdown when users copy-paste the templates.</violation>
</file>
<file name="docs/pt-BR/agents/security-reviewer.md">
<violation number="1" location="docs/pt-BR/agents/security-reviewer.md:79">
P2: Document appears truncated at the final section 'Resposta a Emergências' with no body content, suggesting incomplete translation/parity loss compared to other language versions.</violation>
</file>
<file name="docs/pt-BR/README.md">
<violation number="1" location="docs/pt-BR/README.md:363">
P1: Manual installation instructions reference inconsistent path (.agents/skills/*) compared to documented repository structure (skills/). These are different directories with different contents, causing users to install incorrect/incomplete skills.</violation>
</file>
Since this is your first cubic review, here's how it works:
- cubic automatically reviews your code and comments on bugs and improvements
- Teach cubic by replying to its comments. cubic learns from your replies and gets better over time
- Add one-off context when rerunning by tagging
@cubic-dev-aiwith guidance or docs links (includingllms.txt) - Ask questions if you need clarification on any suggestion
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 11
🧹 Nitpick comments (4)
docs/pt-BR/agents/architect.md (1)
29-29: Optional: Consider "desempenho" instead of "performance".Static analysis suggests using "desempenho" (Portuguese) instead of "performance" (lines 29, 76). While "performance" is widely accepted in technical Portuguese, using "desempenho" would align with more formal Portuguese style guides.
This is a style preference rather than an error - both are acceptable in technical documentation.
Also applies to: 76-76
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/pt-BR/agents/architect.md` at line 29, Replace the term "performance" with the Portuguese-equivalent "desempenho" in the string "Requisitos não-funcionais (performance, segurança, escalabilidade)" and any other occurrences of that exact token (e.g., the instance at line mentioning "performance" later in the document) so the phrase reads "Requisitos não-funcionais (desempenho, segurança, escalabilidade)"; ensure both occurrences are updated for consistent formal Portuguese usage.docs/pt-BR/rules/git-workflow.md (1)
20-20: Evite incentivar plano de teste com placeholders.Em Line 20, “plano de teste com TODOs” tende a gerar PRs com validação incompleta. Recomendo exigir plano executável (comandos + resultado esperado/obtido) em vez de placeholders.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/pt-BR/rules/git-workflow.md` at line 20, Replace the phrase "plano de teste com TODOs" with a requirement for an executable test plan: require concrete steps/commands to run, expected results and how to record actual results (no placeholders or TODOs); update the rule text (the line containing "plano de teste com TODOs") to state "plano de teste executável (comandos, resultado esperado e resultado obtido) — sem placeholders/TODOs".docs/pt-BR/commands/update-docs.md (1)
7-13: Considere padronizar os cabeçalhos/títulos para pt-BR.Há mistura frequente de inglês e português (ex.:
Source,Generates,Command,Description,Variable,Required). Não quebra o conteúdo, mas padronizar melhora consistência da tradução.Also applies to: 22-27, 37-40
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/pt-BR/commands/update-docs.md` around lines 7 - 13, Padronize os cabeçalhos no arquivo de documentação pt-BR trocando os textos em inglês por equivalentes em português (por exemplo: "Source" → "Fonte", "Generates" → "Gera" ou "Gerados", "Command" → "Comando", "Description" → "Descrição", "Variable" → "Variável", "Required" → "Obrigatório") e aplique a mesma substituição nas outras tabelas/trechos mencionados que usam esses mesmos rótulos; revise todas as ocorrências das strings "Source", "Generates", "Command", "Description", "Variable" e "Required" no conteúdo para manter consistência de tradução.docs/pt-BR/CONTRIBUTING.md (1)
230-265: Esclareça quematcheraceitastringouobject.Os exemplos estão bons, mas hoje parecem restringir matcher a string. O schema aceita ambos (
schemas/hooks.schema.json:119-145), então vale explicitar isso para evitar ambiguidade.📌 Proposta de ajuste
### Formato de Hook + +`matcher` pode ser **string** (expressão) ou **objeto** (configuração estruturada), conforme o schema. ```json {🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/pt-BR/CONTRIBUTING.md` around lines 230 - 265, Atualize a seção que descreve "Formato de Hook" e "Sintaxe de Matcher" para deixar explícito que a propriedade matcher aceita tanto string quanto object (conforme o schema de hooks), inclua um exemplo adicional mostrando um matcher como objeto (por exemplo: { "tool": "Bash", "tool_input": { "command": "rm -rf /" } } ou uma estrutura equivalente com operadores) e explique brevemente a diferença de uso entre matcher string e matcher object; mantenha os exemplos atuais (como PreToolUse e tool_input.command matches) e acrescente o exemplo de objeto para evitar ambiguidade sobre o tipo aceito por matcher.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/pt-BR/agents/code-reviewer.md`:
- Line 18: Summary: The docs currently apply a >80% confidence filter to
reported issues which can suppress CRITICAL findings, conflicting with the
command that says CRITICAL/HIGH issues should block commits. Fix: Update the
"Reportar descobertas" section in the agents/code-reviewer documentation and its
translated counterpart to explicitly state the resolution (choose one): either
(A) document that confidence filtering is subordinate to severity rules (i.e.,
CRITICAL/HIGH always reported/blocked regardless of confidence) or (B) exempt
CRITICAL security issues from the confidence threshold so they always surface
and block merges; ensure the change is mirrored in the corresponding code-review
command documentation (the rule that "CRITICAL or HIGH issues block commits") so
both docs are consistent about precedence and behavior.
In `@docs/pt-BR/agents/security-reviewer.md`:
- Line 79: The "## Resposta a Emergências" section is empty; add a short
actionable runbook under that heading that lists the minimal incident steps:
STOP (halt deployment/merge), invoke the security-reviewer agent, prioritize and
fix CRITICAL findings, rotate any exposed secrets, and perform a codebase sweep
for similar issues; update the docs/pt-BR/agents/security-reviewer.md file by
inserting this concise runbook paragraph or bullet list immediately below the
"## Resposta a Emergências" header so users can follow it during a security
incident.
In `@docs/pt-BR/commands/code-review.md`:
- Line 33: The "Severidade: CRITICAL, HIGH, MEDIUM, LOW" line introduces an
unmatched severity level; update the taxonomy in the
docs/pt-BR/commands/code-review.md by either removing "LOW" from the Severidade
list or adding a clear criteria subsection for "LOW" (mirroring the style used
for CRITICAL/HIGH/MEDIUM), and ensure any references to "Severidade" and "LOW"
in the document and examples are consistent with the chosen change.
In `@docs/pt-BR/commands/go-review.md`:
- Around line 62-64: Replace the incorrect race-detection command "go build
-race ./..." in the document with "go test -race ./..." because the race
detector requires running the instrumented code (use the "go test -race ./..."
invocation instead of "go build -race ./..."); update the section header or
example so the command shown reads go test -race ./... wherever "go build -race
./..." appears (search for the literal "go build -race ./..." to locate the
change).
In `@docs/pt-BR/commands/setup-pm.md`:
- Line 35: O texto em docs/pt-BR/commands/setup-pm.md afirma que o fallback
escolhe o “primeiro disponível (pnpm > bun > yarn > npm)”, mas o comportamento
em scripts/lib/package-manager.js usa fallback direto para npm (marca como
source: 'default'); atualize a documentação para refletir o comportamento real
(indicar que o fallback padrão é npm/source: 'default') ou, se preferir alterar
o comportamento ao invés do docs, modificar scripts/lib/package-manager.js para
implementar a ordem de preferência (verificando disponibilidade de pnpm, bun,
yarn em sequência antes de usar npm) e garantir que o campo source seja definido
corretamente para cada descoberta.
In `@docs/pt-BR/commands/update-codemaps.md`:
- Line 13: Documentation states output may be written to ".reports/codemaps/",
but the generator implementation always writes to "docs/CODEMAPS/"; update the
documentation entry in update-codemaps.md to match the generator behavior
(docs/CODEMAPS/) or make the generator (scripts/codemaps/generate.ts)
configurable to accept an alternate output directory and document that option;
reference the filenames update-codemaps.md and generate.ts to locate the doc and
the function writing the output and ensure both agree.
In `@docs/pt-BR/commands/verify.md`:
- Around line 45-46: O template atual sempre exibe o campo "Secrets", mas esse
campo só deve aparecer quando a varredura de segurança foi executada (por
exemplo no modo pre-pr); atualize o template/gerador do relatório (função
renderVerifyReport ou reportTemplate usado pelo comando verify) para
condicionalmente renderizar "Secrets: [OK/X found]" apenas quando a flag
securityScanPerformed ou scanMode estiver em ['pre-pr'] (ou quando estiver
presente um resultado de security scan), e ajuste o texto descritivo do
relatório para explicar claramente quando cada campo (Secrets, Logs, etc.)
aparece; aplique a mesma correção na outra ocorrência do template onde "Secrets"
é mostrado.
In `@docs/pt-BR/CONTRIBUTING.md`:
- Around line 267-272: Update the CONTRIBUTING docs to correct the exit-code
semantics: change the checklist and any mentions that say "exit 1" blocks to
instead state that PreToolUse uses exit 2 to block, and that non-blocking
warnings are emitted to stderr (as described in hooks/README.md). Locate and
update references in the "Checklist de Hook" and surrounding explanatory text so
they reflect blocking with exit 2 and non-blocking warnings via stderr.
- Around line 221-229: Update the "Tipos de Hooks" table in
docs/pt-BR/CONTRIBUTING.md to list all 18 hook types defined in
schemas/hooks.schema.json (ensure each hook name exactly matches the schema) and
correct the Stop row so its Gatilho/Case of Use reflects that Stop runs after
each response (see hooks/README.md for exact behavior), not "sessão termina";
keep the PreToolUse, PostToolUse and SessionStart rows as-is but expand the
table to include the remaining hook names and concise, accurate use/descriptions
from the schema.
In `@docs/pt-BR/examples/django-api-CLAUDE.md`:
- Around line 224-230: The test uses integer literals with underscores (29_99
and 59_98) which are parsed as 2999 and 5998; update the test to use proper
monetary values (e.g., Decimal('29.99') and Decimal('59.98')) so the
ProductFactory(price=...) and the assertion response.data["total"] use Decimal
monetary values; ensure you import Decimal from the decimal module (or otherwise
use the project’s canonical money type) and update both the
ProductFactory(price=...) and the assert response.data["total"] comparisons
accordingly.
In `@docs/pt-BR/rules/hooks.md`:
- Around line 3-8: The docs list of hook types is incomplete — update the "Tipos
de Hook" section to include all hook kinds defined in the project schema such as
SessionStart, PreToolUse, PostToolUse, PreCompact, PostToolUseFailure, Stop (and
any other types present in the hooks registry) so the documentation matches the
canonical hooks list; edit the hooks.md content to enumerate every hook type
(using the exact type names) and, if helpful, add a short one-line description
for each to match the semantics in the schema/registry.
---
Nitpick comments:
In `@docs/pt-BR/agents/architect.md`:
- Line 29: Replace the term "performance" with the Portuguese-equivalent
"desempenho" in the string "Requisitos não-funcionais (performance, segurança,
escalabilidade)" and any other occurrences of that exact token (e.g., the
instance at line mentioning "performance" later in the document) so the phrase
reads "Requisitos não-funcionais (desempenho, segurança, escalabilidade)";
ensure both occurrences are updated for consistent formal Portuguese usage.
In `@docs/pt-BR/commands/update-docs.md`:
- Around line 7-13: Padronize os cabeçalhos no arquivo de documentação pt-BR
trocando os textos em inglês por equivalentes em português (por exemplo:
"Source" → "Fonte", "Generates" → "Gera" ou "Gerados", "Command" → "Comando",
"Description" → "Descrição", "Variable" → "Variável", "Required" →
"Obrigatório") e aplique a mesma substituição nas outras tabelas/trechos
mencionados que usam esses mesmos rótulos; revise todas as ocorrências das
strings "Source", "Generates", "Command", "Description", "Variable" e "Required"
no conteúdo para manter consistência de tradução.
In `@docs/pt-BR/CONTRIBUTING.md`:
- Around line 230-265: Atualize a seção que descreve "Formato de Hook" e
"Sintaxe de Matcher" para deixar explícito que a propriedade matcher aceita
tanto string quanto object (conforme o schema de hooks), inclua um exemplo
adicional mostrando um matcher como objeto (por exemplo: { "tool": "Bash",
"tool_input": { "command": "rm -rf /" } } ou uma estrutura equivalente com
operadores) e explique brevemente a diferença de uso entre matcher string e
matcher object; mantenha os exemplos atuais (como PreToolUse e
tool_input.command matches) e acrescente o exemplo de objeto para evitar
ambiguidade sobre o tipo aceito por matcher.
In `@docs/pt-BR/rules/git-workflow.md`:
- Line 20: Replace the phrase "plano de teste com TODOs" with a requirement for
an executable test plan: require concrete steps/commands to run, expected
results and how to record actual results (no placeholders or TODOs); update the
rule text (the line containing "plano de teste com TODOs") to state "plano de
teste executável (comandos, resultado esperado e resultado obtido) — sem
placeholders/TODOs".
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: f035056a-6ea0-437b-ab64-5c7db7596253
📒 Files selected for processing (48)
README.mddocs/pt-BR/CONTRIBUTING.mddocs/pt-BR/README.mddocs/pt-BR/TERMINOLOGY.mddocs/pt-BR/agents/architect.mddocs/pt-BR/agents/build-error-resolver.mddocs/pt-BR/agents/code-reviewer.mddocs/pt-BR/agents/database-reviewer.mddocs/pt-BR/agents/doc-updater.mddocs/pt-BR/agents/e2e-runner.mddocs/pt-BR/agents/go-build-resolver.mddocs/pt-BR/agents/go-reviewer.mddocs/pt-BR/agents/planner.mddocs/pt-BR/agents/refactor-cleaner.mddocs/pt-BR/agents/security-reviewer.mddocs/pt-BR/agents/tdd-guide.mddocs/pt-BR/commands/build-fix.mddocs/pt-BR/commands/checkpoint.mddocs/pt-BR/commands/code-review.mddocs/pt-BR/commands/e2e.mddocs/pt-BR/commands/eval.mddocs/pt-BR/commands/go-build.mddocs/pt-BR/commands/go-review.mddocs/pt-BR/commands/go-test.mddocs/pt-BR/commands/learn.mddocs/pt-BR/commands/orchestrate.mddocs/pt-BR/commands/plan.mddocs/pt-BR/commands/refactor-clean.mddocs/pt-BR/commands/setup-pm.mddocs/pt-BR/commands/tdd.mddocs/pt-BR/commands/test-coverage.mddocs/pt-BR/commands/update-codemaps.mddocs/pt-BR/commands/update-docs.mddocs/pt-BR/commands/verify.mddocs/pt-BR/examples/CLAUDE.mddocs/pt-BR/examples/django-api-CLAUDE.mddocs/pt-BR/examples/go-microservice-CLAUDE.mddocs/pt-BR/examples/rust-api-CLAUDE.mddocs/pt-BR/examples/saas-nextjs-CLAUDE.mddocs/pt-BR/examples/user-CLAUDE.mddocs/pt-BR/rules/agents.mddocs/pt-BR/rules/coding-style.mddocs/pt-BR/rules/git-workflow.mddocs/pt-BR/rules/hooks.mddocs/pt-BR/rules/patterns.mddocs/pt-BR/rules/performance.mddocs/pt-BR/rules/security.mddocs/pt-BR/rules/testing.md
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
Contributor
|
Contributor
Analysis Failed
Troubleshooting
Retry: |
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
Contributor
|
Contributor
Analysis Failed
Troubleshooting
Retry: |
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
Contributor
|
Contributor
Analysis Failed
Troubleshooting
Retry: |
Contributor
There was a problem hiding this comment.
1 issue found across 3 files (changes from recent commits).
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="docs/pt-BR/commands/plan.md">
<violation number="1" location="docs/pt-BR/commands/plan.md:99">
P2: Duplicate line "Se quiser mudanças, responda com:" appears twice consecutively. This is an accidental duplication that should be removed to maintain documentation clarity.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
Contributor
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (1)
docs/pt-BR/commands/plan.md (1)
113-113: Padronizar para “arquivo-fonte” em PT-BR.Sugestão de ajuste textual para ortografia/padronização: “arquivo-fonte”.
📝 Suggested wording tweak
-Para instalações manuais, o arquivo fonte fica em: +Para instalações manuais, o arquivo-fonte fica em:🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/pt-BR/commands/plan.md` at line 113, Replace the phrase "arquivo fonte" in the sentence "Para instalações manuais, o arquivo fonte fica em:" with the hyphenated PT-BR standard "arquivo-fonte" so the line reads "Para instalações manuais, o arquivo-fonte fica em:". Ensure the change is applied to the text node containing that exact sentence.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/pt-BR/commands/eval.md`:
- Around line 17-18: Remove the duplicate markdown fence opener so the code
block starts with a single "```markdown" only; locate the consecutive
"```markdown" lines in the doc (the nested fence in the code block) and delete
the extra opener so the block reads a single fence followed by the content
(e.g., "## EVAL: feature-name...") and then a closing "```".
In `@docs/pt-BR/commands/plan.md`:
- Around line 98-99: Remove the duplicated sentence "Se quiser mudanças,
responda com:" so it appears only once in the document; locate the consecutive
duplicate lines containing that exact phrase in docs/pt-BR/commands/plan.md and
delete one occurrence to avoid redundant content.
---
Nitpick comments:
In `@docs/pt-BR/commands/plan.md`:
- Line 113: Replace the phrase "arquivo fonte" in the sentence "Para instalações
manuais, o arquivo fonte fica em:" with the hyphenated PT-BR standard
"arquivo-fonte" so the line reads "Para instalações manuais, o arquivo-fonte
fica em:". Ensure the change is applied to the text node containing that exact
sentence.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: ef5bc9e8-956e-4f40-955e-d148270011b0
📒 Files selected for processing (3)
docs/pt-BR/commands/eval.mddocs/pt-BR/commands/go-review.mddocs/pt-BR/commands/plan.md
Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com>
Contributor
|
Contributor
Analysis Failed
Troubleshooting
Retry: |
Contributor
|
Contributor
Analysis Failed
Troubleshooting
Retry: |
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
Contributor
|
Contributor
Analysis Failed
Troubleshooting
Retry: |
Contributor
There was a problem hiding this comment.
1 issue found across 3 files (changes from recent commits).
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="docs/pt-BR/commands/tdd.md">
<violation number="1" location="docs/pt-BR/commands/tdd.md:52">
P1: Nested Markdown code fences use the same delimiter (```) which will break rendering. The outer example block should use ```` (4 backticks) to properly contain inner ``` code blocks.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
Contributor
|
Contributor
Analysis Failed
Troubleshooting
Retry: |
Contributor
There was a problem hiding this comment.
♻️ Duplicate comments (1)
docs/pt-BR/agents/security-reviewer.md (1)
79-87:⚠️ Potential issue | 🟠 MajorAdicionar contenção imediata e varredura pós-incidente no runbook
Na Line 81, o fluxo de emergência ainda não inclui explicitamente: STOP (pausar merge/deploy), corrigir CRÍTICOS antes de continuar, e varrer o código por issues similares. Isso deixa o protocolo incompleto para resposta a incidentes.
📌 Ajuste sugerido
## Resposta a Emergências Se você encontrar uma vulnerabilidade CRÍTICA: -1. Documente em um relatório detalhado -2. Alerte imediatamente o responsável pelo projeto -3. Forneça um exemplo de um código seguro -4. Verifique se a correção funciona -5. Troque as informações confidenciais se as credenciais forem expostas +1. **PARE imediatamente** (pause merge/deploy e mudanças não essenciais) +2. Acione o agente `security-reviewer` para triagem e plano de correção +3. Priorize e corrija todos os achados **CRÍTICOS** antes de continuar +4. Documente em relatório detalhado e alerte imediatamente o responsável pelo projeto +5. Valide a correção (testes/revisão) e confirme que o risco foi mitigado +6. Rotacione segredos/credenciais expostos +7. Revise o códigobase por vulnerabilidades semelhantesBased on learnings: If security issue found: STOP → use security-reviewer agent → fix CRITICAL issues → rotate exposed secrets → review codebase for similar issues.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/pt-BR/agents/security-reviewer.md` around lines 79 - 87, Update the "## Resposta a Emergências" runbook to include immediate containment and post-incident scanning: insert a clear STOP action to pause merges/deploys, call the security-reviewer agent to triage, mandate fixing CRITICAL issues before continuing, rotate any exposed secrets, and run a code-wide scan for similar vulnerabilities (add these as steps following the existing numbered list under "Resposta a Emergências" so the flow becomes: STOP → invoke security-reviewer → fix CRITICALs → rotate secrets → scan for similar issues → verify fix).
🧹 Nitpick comments (1)
docs/pt-BR/agents/refactor-cleaner.md (1)
65-65: Optional Portuguese style refinements.The static analysis tool flagged two minor Portuguese grammar/style suggestions:
- Line 65: Consider using a compound plural + singular form for "Princípios Chave" in academic/scientific writing
- Line 71: The phrase "ou antes de deploys" might benefit from comma separation for improved style
These are optional refinements that don't affect technical clarity or functionality.
Also applies to: 71-71
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/pt-BR/agents/refactor-cleaner.md` at line 65, Change the Portuguese header "Princípios Chave" to the compound form "Princípios‑chave" (use a hyphen) and add a comma in the sentence fragment containing "ou antes de deploys" to improve flow (e.g., "ou, antes de deploys," or "ou, antes de deploys,") so the two flagged strings ("Princípios Chave" header and the phrase "ou antes de deploys") reflect the suggested style refinements.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Duplicate comments:
In `@docs/pt-BR/agents/security-reviewer.md`:
- Around line 79-87: Update the "## Resposta a Emergências" runbook to include
immediate containment and post-incident scanning: insert a clear STOP action to
pause merges/deploys, call the security-reviewer agent to triage, mandate fixing
CRITICAL issues before continuing, rotate any exposed secrets, and run a
code-wide scan for similar vulnerabilities (add these as steps following the
existing numbered list under "Resposta a Emergências" so the flow becomes: STOP
→ invoke security-reviewer → fix CRITICALs → rotate secrets → scan for similar
issues → verify fix).
---
Nitpick comments:
In `@docs/pt-BR/agents/refactor-cleaner.md`:
- Line 65: Change the Portuguese header "Princípios Chave" to the compound form
"Princípios‑chave" (use a hyphen) and add a comma in the sentence fragment
containing "ou antes de deploys" to improve flow (e.g., "ou, antes de deploys,"
or "ou, antes de deploys,") so the two flagged strings ("Princípios Chave"
header and the phrase "ou antes de deploys") reflect the suggested style
refinements.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 147208f0-49ff-4867-b12c-2371beba8555
📒 Files selected for processing (3)
docs/pt-BR/agents/refactor-cleaner.mddocs/pt-BR/agents/security-reviewer.mddocs/pt-BR/commands/tdd.md
✅ Files skipped from review due to trivial changes (1)
- docs/pt-BR/commands/tdd.md
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
docs/pt-BR/commands/orchestrate.md (1)
154-157: Considere padronizar termos em inglês e acrônimos para PT-BR.Há trechos de prosa técnica não localizados (
cross-harness,CONTROL PLANE,ECC) sem explicação imediata. Isso pode reduzir legibilidade para o público-alvo da tradução. Sugiro manter os termos técnicos necessários, mas com glossário/expansão na primeira ocorrência.✍️ Exemplo de ajuste de estilo
-Para workers externos em tmux panes com git worktrees separados, use `node scripts/orchestrate-worktrees.js plan.json --execute`. O padrão embutido de orquestração permanece no processo atual; o helper é para sessões longas ou cross-harness. +Para workers externos em panes do tmux com git worktrees separados, use `node scripts/orchestrate-worktrees.js plan.json --execute`. O padrão embutido de orquestração permanece no processo atual; o helper é para sessões longas ou execução entre harnesses (cross-harness). -Quando os workers precisarem enxergar arquivos locais sujos ou não rastreados do checkout principal, adicione `seedPaths` ao arquivo de plano. O ECC faz overlay apenas desses caminhos selecionados em cada worktree do worker após `git worktree add`, mantendo o branch isolado e ainda expondo scripts, planos ou docs em andamento. +Quando os workers precisarem enxergar arquivos locais sujos ou não rastreados do checkout principal, adicione `seedPaths` ao arquivo de plano. O ECC (Execution Control Center) faz overlay apenas desses caminhos selecionados em cada worktree do worker após `git worktree add`, mantendo o branch isolado e ainda expondo scripts, planos ou docs em andamento.Also applies to: 185-205
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/pt-BR/commands/orchestrate.md` around lines 154 - 157, The translation contains untranslated technical terms and unexplained acronyms (e.g., "cross-harness", "CONTROL PLANE", "ECC") which reduce readability; update the PT-BR doc around the orchestrate section and the later block (also lines ~185-205) to either translate these terms consistently or keep the English term but add a parenthetical Portuguese expansion/glossary entry on first occurrence, and ensure tool/script names like orchestrate-worktrees.js and the config key seedPaths remain literal code tokens; maintain consistent capitalization and create a short glossary entry or inline expansion for ECC and CONTROL PLANE the first time they appear.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/pt-BR/commands/plan.md`:
- Line 112: Replace the phrase "Para instalações manuais, o arquivo fonte fica
em:" with the corrected hyphenation "Para instalações manuais, o arquivo-fonte
fica em:"—update the occurrence of the noun compound "arquivo fonte" in the
string in the docs (the exact sentence shown) to use "arquivo-fonte".
---
Nitpick comments:
In `@docs/pt-BR/commands/orchestrate.md`:
- Around line 154-157: The translation contains untranslated technical terms and
unexplained acronyms (e.g., "cross-harness", "CONTROL PLANE", "ECC") which
reduce readability; update the PT-BR doc around the orchestrate section and the
later block (also lines ~185-205) to either translate these terms consistently
or keep the English term but add a parenthetical Portuguese expansion/glossary
entry on first occurrence, and ensure tool/script names like
orchestrate-worktrees.js and the config key seedPaths remain literal code
tokens; maintain consistent capitalization and create a short glossary entry or
inline expansion for ECC and CONTROL PLANE the first time they appear.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 2fabc687-96cf-4dc1-b43a-5a5ed5ca8c6a
📒 Files selected for processing (2)
docs/pt-BR/commands/orchestrate.mddocs/pt-BR/commands/plan.md
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
Contributor
|
Contributor
Analysis Failed
Troubleshooting
Retry: |
This was referenced Mar 23, 2026
FrancescoRosciano
pushed a commit
to FRosciano-Mambo/everything-claude-code
that referenced
this pull request
Jun 1, 2026
…guese-translation Docs/add brazilian portuguese translation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What Changed
Added and completed the new pt-BR documentation set, including missing command and example translations, and updated language navigation in the main README.
Scope delivered:
Breakdown:
Why This Change
Portuguese is a high-impact language for documentation accessibility, not a niche addition.
Testing Done
node tests/run-all.js)Type of Change
fix:Bug fixfeat:New featurerefactor:Code refactoringdocs:Documentationtest:Testschore:Maintenance/toolingci:CI/CD changesSecurity & Quality Checklist
Documentation
Summary by cubic
Added full Brazilian Portuguese (pt-BR) docs and updated the README language switcher to include it. The site now supports 6 languages.
docs/pt-BRwith core docs and all agents, commands, examples, and rules (47 files)./eval(criteria/reporting), plus/go-review,go-build-resolver,security-reviewer,refactor-cleaner, and improved/orchestrateand/planworkflows.README.mdto add Português (Brasil) and bump language count from 5 to 6.Written for commit c3769b5. Summary will update on new commits.
Summary by CodeRabbit
New Features
Documentation