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/tr/agents/go-build-resolver.md">

<violation number="1" location="docs/tr/agents/go-build-resolver.md:57">
P2: `invalid type assertion` fix guidance is technically incorrect by restricting assertions to `interface{}` only; assertions are valid from any interface-typed expression.</violation>
</file>

<file name="docs/tr/agents/chief-of-staff.md">

<violation number="1" location="docs/tr/agents/chief-of-staff.md:85">
P2: Inconsistent relationship memory path (`private/relationships.md` vs `relationships.md`) in one workflow can cause read/write divergence.</violation>
</file>

<file name="docs/tr/agents/rust-reviewer.md">

<violation number="1" location="docs/tr/agents/rust-reviewer.md:14">
P2: CI/merge readiness is framed as an assumption instead of a mandatory precondition, conflicting with required "green checks + no conflicts before review" workflow.</violation>
</file>

<file name="docs/tr/commands/multi-plan.md">

<violation number="1" location="docs/tr/commands/multi-plan.md:127">
P2: Phase 1’de enhanced requirement zorunlu kılınırken Phase 2.1’de original requirement isteniyor; bu aynı komut akışında çelişkili input talimatı oluşturuyor.</violation>
</file>

<file name="docs/tr/agents/go-reviewer.md">

<violation number="1" location="docs/tr/agents/go-reviewer.md:14">
P2: Reviewer workflow omits required pre-review gates (green checks and conflict-free branch) and instructs immediate review.</violation>
</file>

<file name="docs/tr/agents/code-reviewer.md">

<violation number="1" location="docs/tr/agents/code-reviewer.md:14">
P2: Review process doc omits mandatory pre-review gates (green CI and no merge conflicts), leading to blocked/invalid review cycles.</violation>
</file>

<file name="docs/tr/commands/instinct-import.md">

<violation number="1" location="docs/tr/commands/instinct-import.md:29">
P2: HTTP import example uses a non-raw GitHub URL, which will not provide parseable instinct YAML and can make the documented command fail.</violation>
</file>

<file name="docs/tr/commands/go-review.md">

<violation number="1" location="docs/tr/commands/go-review.md:90">
P2: Nested fenced code blocks reuse triple backticks, which breaks Markdown rendering of the example block.</violation>
</file>

<file name="docs/tr/commands/tdd.md">

<violation number="1" location="docs/tr/commands/tdd.md:40">
P2: Nested triple-backtick fences in the example session break Markdown rendering; use a longer outer fence (e.g., four backticks) or restructure the block.</violation>
</file>

<file name="docs/tr/commands/e2e.md">

<violation number="1" location="docs/tr/commands/e2e.md:39">
P2: Nested fenced code in the example uses a triple-backtick outer fence; use a longer outer fence (e.g., ````) so inner ``` blocks do not break markdown rendering.</violation>
</file>

<file name="docs/tr/commands/checkpoint.md">

<violation number="1" location="docs/tr/commands/checkpoint.md:7">
P2: Usage syntax is inconsistent with documented arguments: `clear` is supported below but missing from the main command signature.</violation>
</file>

<file name="docs/tr/agents/java-build-resolver.md">

<violation number="1" location="docs/tr/agents/java-build-resolver.md:24">
P2: Diagnostic instructions conflict: agents are told to run Maven and Gradle commands sequentially, despite later requiring build-tool detection first.</violation>
</file>

<file name="docs/tr/SECURITY.md">

<violation number="1" location="docs/tr/SECURITY.md:46">
P2: Security policy adds a direct link to an external GitHub repo, conflicting with project guidance to avoid unvetted external code links in user-facing security docs.</violation>
</file>

<file name="docs/tr/commands/eval.md">

<violation number="1" location="docs/tr/commands/eval.md:7">
P2: Usage synopsis is inconsistent with documented subcommands/arguments (`clean` missing; optional feature arg appears to apply to subcommands that take none).</violation>
</file>

<file name="docs/tr/agents/cpp-reviewer.md">

<violation number="1" location="docs/tr/agents/cpp-reviewer.md:14">
P2: Reviewer workflow contradicts team policy by starting review immediately instead of gating on passing CI checks.</violation>

<violation number="2" location="docs/tr/agents/cpp-reviewer.md:44">
P2: Turkish translation corrupts the C++ style rule by reversing `typedef`/`using` semantics, changing reviewer guidance.</violation>
</file>

<file name="docs/tr/agents/java-reviewer.md">

<violation number="1" location="docs/tr/agents/java-reviewer.md:12">
P2: Java reviewer workflow starts detailed review without required pre-review gates for green checks and conflict-free merge state.</violation>
</file>

<file name="docs/tr/agents/kotlin-reviewer.md">

<violation number="1" location="docs/tr/agents/kotlin-reviewer.md:20">
P2: Workflow guidance omits required pre-review gates (green CI and resolved merge conflicts), causing process non-compliance and wasted reviewer effort.</violation>
</file>

<file name="docs/tr/AGENTS.md">

<violation number="1" location="docs/tr/AGENTS.md:3">
P2: Documentation inventory is internally inconsistent (agent/skill totals conflict with listed content), indicating stale translated guidance.</violation>
</file>

<file name="docs/tr/README.md">

<violation number="1" location="docs/tr/README.md:9">
P2: License badge link is relative to the nested docs folder and points to a non-existent `docs/tr/LICENSE` instead of the repository root license file.</violation>

<violation number="2" location="docs/tr/README.md:18">
P3: Language support count is outdated (`5`) and contradicts the six-language selector in the same README.</violation>

<violation number="3" location="docs/tr/README.md:394">
P2: FAQ contains broken in-page anchor links to non-existent sections, causing dead internal navigation.</violation>
</file>

<file name="docs/tr/agents/python-reviewer.md">

<violation number="1" location="docs/tr/agents/python-reviewer.md:14">
P2: Python reviewer workflow starts review immediately but omits required pre-review gates (passing checks and no merge conflicts), conflicting with established review policy.</violation>

<violation number="2" location="docs/tr/agents/python-reviewer.md:74">
P2: Localized severity token in structured review output breaks consistency with canonical markers used in other agent docs, risking parser/tooling incompatibility.</violation>
</file>

<file name="docs/tr/commands/verify.md">

<violation number="1" location="docs/tr/commands/verify.md:45">
P2: Verification workflow claims secrets/security checks in output and `pre-pr`, but the actual step-by-step instructions never execute any security scan.</violation>
</file>

<file name="docs/tr/commands/skill-create.md">

<violation number="1" location="docs/tr/commands/skill-create.md:58">
P2: Nested triple-backtick fences in the example output can prematurely close the outer code block and break Markdown rendering.</violation>
</file>

<file name="docs/tr/commands/go-build.md">

<violation number="1" location="docs/tr/commands/go-build.md:46">
P2: Nested fenced code blocks use the same triple-backtick delimiter, which can prematurely close the outer example block and break Markdown rendering.</violation>
</file>

<file name="docs/tr/TERMINOLOGY.md">

<violation number="1" location="docs/tr/TERMINOLOGY.md:42">
P2: The glossary’s status column uses undocumented value `-` even though the status legend defines only `Onaylandı` and `Beklemede`.</violation>
</file>

<file name="docs/tr/CONTRIBUTING.md">

<violation number="1" location="docs/tr/CONTRIBUTING.md:273">
P2: Hook command example is shell-invalid due to an unescaped apostrophe inside a single-quoted string.</violation>
</file>

<file name="docs/tr/commands/sessions.md">

<violation number="1" location="docs/tr/commands/sessions.md:11">
P2: Usage synopsis is incomplete: it excludes documented `aliases` and `unalias` commands.</violation>
</file>

<file name="docs/tr/examples/README.md">

<violation number="1" location="docs/tr/examples/README.md:68">
P2: Documentation instructs appending a full JSON object to `settings.json`, which can corrupt the file into invalid JSON.</violation>

<violation number="2" location="docs/tr/examples/README.md:81">
P2: Two newly added related-resource links target non-existent files in `docs/tr`, resulting in broken documentation navigation.</violation>
</file>

<file name="docs/tr/agents/e2e-runner.md">

<violation number="1" location="docs/tr/agents/e2e-runner.md:74">
P2: Dokümantasyon `page.click()` otomatik bekleme davranışını yanlış belirtiyor; bu Playwright kullanımını yanıltabilir.</violation>
</file>

<file name="docs/tr/CODE_OF_CONDUCT.md">

<violation number="1" location="docs/tr/CODE_OF_CONDUCT.md:98">
P2: New user-facing doc adds an external GitHub repository link that conflicts with the team’s unvetted-repo-link policy.</violation>
</file>

<file name="docs/tr/examples/statusline.json">

<violation number="1" location="docs/tr/examples/statusline.json:4">
P2: `todo_count` can become `0\n0` due to `grep -c` + `|| echo 0`, causing integer comparison errors in the statusline command.</violation>
</file>

<file name="docs/tr/TROUBLESHOOTING.md">

<violation number="1" location="docs/tr/TROUBLESHOOTING.md:373">
P2: Hardcoded marketplace cache path is inconsistent with actual nested cache layout, so the MODULE_NOT_FOUND recovery `cd` can fail on real installs.</violation>

<violation number="2" location="docs/tr/TROUBLESHOOTING.md:421">
P3: Relative link `./docs/` in `docs/tr/TROUBLESHOOTING.md` likely points to a non-existent `docs/tr/docs/` path, causing broken documentation navigation.</violation>
</file>

<file name="docs/tr/commands/multi-execute.md">

<violation number="1" location="docs/tr/commands/multi-execute.md:101">
P2: Timeout/proses yönetimi yönergeleri kendi içinde çelişiyor; bir yandan process'i asla öldürmeyi yasaklayıp diğer yandan öldürme seçeneğini kullanıcıya sormayı zorunlu kılıyor.</violation>
</file>

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/tr/agents/e2e-runner.md`:
- Line 74: The current Turkish sentence wrongly claims page.click() does not
auto-wait; change it to state that both page.click() and page.locator().click()
perform Playwright's auto-wait/actionability checks, and clarify the real
difference: locator.click() (or page.locator().click()) is strict (will error on
multiple matches) and is the recommended modern approach for resilience—not
because it waits differently; update the wording to reflect this distinction
using the symbols page.click(), page.locator().click(), and locator.click().

In `@docs/tr/commands/build-fix.md`:
- Line 17: Replace the project-level validation command in the table cell that
currently shows `python -m py_compile` with `python -m compileall .` so the docs
recommend a recursive, project-wide bytecode compile (locate the table entry
containing the literal `python -m py_compile` and update it to `python -m
compileall .`). Ensure the surrounding formatting of the table row remains
intact.

In `@docs/tr/commands/code-review.md`:
- Around line 1-3: Bu dosyada eksik olan YAML frontmatter bloğunu ekleyin:
dosyanın en üstüne üç kısa çizgiyle başlanan/bitirilen frontmatter içine en
azından description alanını (ör. description: "kısa açıklama") ekleyin ve
gerekiyorsa title/metadatayı tamamlayarak commands/ komut dokümantasyon
şablonuyla uyumlu hale getirin; hedeflenen semboller: frontmatter bloğu ve
description alanı (description) — bu alanı docs/tr/commands/code-review.md
içeriğinin üstüne yerleştirin.

In `@docs/tr/commands/e2e.md`:
- Line 278: The workflow step currently uses the deprecated action reference
"uses: actions/upload-artifact@v3"; update that to a supported major version
(preferably "uses: actions/upload-artifact@v7", or at minimum "uses:
actions/upload-artifact@v4") in the workflow file, then validate the workflow
(run GitHub Actions workflow lint/syntax check or a dry run) and adjust any
inputs/fields if the newer action version changed parameter names or behavior.

In `@docs/tr/commands/verify.md`:
- Around line 1-3: Bu Markdown dokümanında eksik olan YAML frontmatter
(özellikle description alanı) eklenecek: dosyanın en başına üç çizgiyle ayrılmış
bir YAML bloğu ekleyin ve içine en azından description: "Kısa komut açıklaması"
olacak şekilde yerel dilde açıklama; gerekiyorsa title, tags veya locale gibi
CONTRIBUTING.md’de tanımlı diğer metadata alanlarını de dahil edin; frontmatter
bloğunu (--- ... ---) ekleyip kaydederek komut keşfi/işlenmesi için gereken
metadata’yı sağlamış olacaksınız.

In `@docs/tr/examples/README.md`:
- Around line 65-69: Update the “Status Line Konfigürasyonu” instructions to
remove the raw append command and instead tell the user to merge JSON safely:
explain that they should not use cat ... >> to append, and instruct them to
either manually merge the contents of statusline.json into their settings.json
maintaining valid JSON, or use a JSON-aware merge/cli tool (reference the
statusline.json file and the settings.json target in the README section header)
and replace the current two-line bash snippet with this safer guidance.

In `@docs/tr/examples/statusline.json`:
- Line 4: The todo_count assignment is producing "0\n0" when grep -c finds no
matches because grep exits non-zero and the subsequent || echo 0 appends another
zero; update the command that sets todo_count (the expression using todo_count,
transcript and grep -c '"type":"todo"') so that the grep's non-zero exit is
swallowed (e.g. wrap the grep invocation in a grouped command and append "||
true") before falling back to echo 0 when the transcript file is missing,
ensuring only a single numeric "0" is produced and [ "$todo_count" -gt 0 ] works
correctly.

In `@docs/tr/skills/coding-standards/SKILL.md`:
- Around line 399-401: sortedMarkets hesaplanırken useMemo içindeki
markets.sort(...) diziyi yerinde mutasyona uğratarak değişmezlik ilkesini ihlal
ediyor; bunu düzeltmek için useMemo içerisindeki markets.sort çağrısını kopya
bir dizi üzerinde çalıştıracak şekilde değiştir (örneğin markets.slice() veya
[...markets] ile yeni bir dizi oluşturup o diziyi sort et) ve sortedMarkets ile
useMemo kullanımını buna göre güncelle; ilgili yerleri bulmak için
sortedMarkets, useMemo ve markets.sort sembollerine bak.

In `@docs/tr/skills/golang-testing/SKILL.md`:
- Line 675: The fuzz command's target name doesn't match the actual test
function: update the example command to reference the real fuzz function name
FuzzParseJSON (or use a pattern that matches it, e.g. FuzzParse*) so the command
will run the intended test; locate the example command and replace
`-fuzz=FuzzParse` with `-fuzz=FuzzParseJSON` (or a matching pattern) where the
CLI example is shown.

In `@docs/tr/skills/kotlin-patterns/SKILL.md`:
- Around line 382-423: The dependency versions in the plugins block
(kotlin("jvm")/kotlin("plugin.serialization") "2.3.10", id("io.ktor.plugin")
"3.4.0", kotest/test deps, etc.) and the dependencies section are outdated;
either update these to current stable releases (e.g., Kotlin 2.3.20, Ktor 3.4.1,
Kotest 6.1.6 and matching library versions) by changing the version strings in
the plugins and dependencies entries, or add a clear “example versions (last
updated YYYY-MM-DD)” label above the block so readers know these are
illustrative and may be out of date; ensure you modify the plugins { ... } and
dependencies { ... } blocks referenced by kotlin("jvm"), id("io.ktor.plugin"),
and the Kotest/testImplementation lines accordingly.

---

Minor comments:
In `@docs/tr/AGENTS.md`:
- Line 3: Dosyadaki tutarsızlık: metinde "116 skill" ve "115 iş akışı skillleri"
ifadeleri çelişiyor; tek doğru değeri kullanmak için AGENTS.md içindeki her iki
ifadeyi bulun (örneğin arama ile "116 skill" ve "115 iş akışı skillleri") ve
geçerli envanter sayısına göre her iki ifadeyi aynı sayıyla eşitleyin;
güncelleme sırasında ilgili başlık/bağlam (agent/skill listesi veya açıklama
satırı) korunmalı ve yazım tutarlılığı (örn. "skill" vs "iş akışı skillleri")
sağlanmalıdır.

In `@docs/tr/agents/chief-of-staff.md`:
- Line 108: Başlık satırındaki yazım hatasını düzeltin: değiştirin "# Bugünün
Brifingı — [Tarih]" ifadesini doğru yazımı olan "# Bugünün Brifingi — [Tarih]"
ile güncelleyin (arama anahtarı: başlık satırı içeriği "Bugünün Brifingı").

In `@docs/tr/agents/docs-lookup.md`:
- Line 8: Replace the Turkish word "specialistisiniz" in the sentence on line 8
with a correct, natural alternative such as "uzmanısınız" or "dokümantasyon
uzmanısınız" to improve spelling and language consistency in the phrase that
currently reads "Bir dokümantasyon specialistisiniz."

In `@docs/tr/agents/kotlin-reviewer.md`:
- Line 39: Dosyadaki güvenlik eskalasyon cümlesindeki küçük dil hatasını
düzeltin: "security-reviewer'а devreden" ifadesini bulun (satırdaki eskalasyon
cümlesi/ifadesi) ve bunu "security-reviewer'a devredin" olarak değiştirin;
ilgili metin tekil çekimde ve emir kipinde doğru okunacak şekilde
güncellendiğinden başka değişiklik yapmanıza gerek yoktur.

In `@docs/tr/agents/loop-operator.md`:
- Around line 1-7: The YAML frontmatter's description for the loop-operator
document is in English while the rest of the Turkish docs use Turkish; update
the description field (the "description" key in the frontmatter for name:
loop-operator) to a Turkish translation matching the tone of other files (e.g.,
similar to planner.md) so the frontmatter is fully Turkish and consistent across
the docs.

In `@docs/tr/CLAUDE.md`:
- Line 60: Güncelleme: mevcut tek satırlık kural "Dosya isimlendirme: tire ile
küçük harfler (örn., `python-reviewer.md`, `tdd-workflow.md`)" yanıltıcı;
değiştirirken açıkça belirtin ki genel içerik dosyaları için kebab-case ve küçük
harf kullanılırken, skills dizini için hüküm farklıdır — klasör adı kebab-case
(örn. `python-reviewer`) olmalı ve içindeki dosya standart olarak büyük harfli
`SKILL.md` formatında olmalıdır; yani dokümanda mevcut cümleyi değiştirip hem
genel kuralı (kebab-case, küçük harf) hem de skills/ dizini özel kuralını
(`SKILL.md` inside kebab-case folder) ikili olarak netleştirin.

In `@docs/tr/commands/checkpoint.md`:
- Line 7: Update the usage line for the checkpoint command to include the
missing "clear" subcommand so the syntax matches the documented arguments;
specifically modify the `/checkpoint [create|verify|list] [isim]` line to
`/checkpoint [create|verify|list|clear] [isim]` (and make the same change in the
repeated usage block around lines 70-74) so the displayed usage matches the
available `clear` argument.

In `@docs/tr/commands/eval.md`:
- Line 7: Update the usage line string that currently reads "`/eval
[define|check|report|list] [feature-name]`" to include the missing "clean"
subcommand so it matches the detailed documentation (e.g., change the usage
pattern to include "clean" among the subcommands); locate the usage line in the
eval.md content (the string on Line 7) and add "clean" to the bracketed list of
subcommands.

In `@docs/tr/commands/go-review.md`:
- Line 2: Replace inconsistent English-derived terms with the preferred Turkish
terms: change occurrences of "İdiomatic" to "İdiyomatik" and "Static" to "Statik
analiz" (or "Statik" if used in short form) throughout the document, including
the sentence that currently reads "İdiomatic desenler, ..." and the other
occurrence referenced (line 12); ensure casing and diacritics match the Turkish
forms and update the phrase "go-reviewer agent'ını" if necessary for consistent
Turkish phrasing.

In `@docs/tr/commands/update-docs.md`:
- Around line 45-55: Update the incorrect documentation path references: replace
the generic CONTRIBUTING.md reference with the repository's Turkish localized
CONTRIBUTING.md file (use the localized CONTRIBUTING.md entry present in the
repo) and fix the RUNBOOK.md reference by either pointing to the correct
existing runbook file in the Turkish docs set or add/create a RUNBOOK.md in the
docs so the "Runbook" section points to a valid file; update the two mentions in
the update-docs text accordingly.

In `@docs/tr/examples/user-CLAUDE.md`:
- Line 35: Fix the spelling mistake in the table row string "agents.md | Agent
orkestrayonu, hangi agent'ın ne zaman kullanılacağı" by replacing "orkestrayonu"
with "orkestrasyonu" so the entry reads "agents.md | Agent orkestrasyonu, hangi
agent'ın ne zaman kullanılacağı".

In `@docs/tr/README.md`:
- Line 9: Update the README: change the license badge link target from the local
"LICENSE" to the repository root LICENSE (so the badge points to the top-level
LICENSE file instead of a non-existent local file) and increment the language
support count from 5 to 6 where the language count is mentioned; use the badge
markdown
"[![License](https://img.shields.io/badge/lisans-MIT-blue.svg)](LICENSE)" as the
locator for the license link change and search for the language-count sentence
("5" language supports) to update it to "6".

In `@docs/tr/skills/django-patterns/SKILL.md`:
- Line 483: Dokümantasyondaki Türkçe ifade hatası: sınıf/dosya içinde yer alan
docstring veya açıklama satırı """Sipariş ilgili iş mantığı için service
layer.""" ifadesini bulun (aranacak benzersiz sembol: "Sipariş ilgili iş mantığı
için service layer.") ve metni "Siparişle ilgili iş mantığı için service layer."
olarak düzeltin; yalnızca bu kelime birleşimini güncelleyin ve diğer metin
yapısını değiştirmeyin.
- Line 61: The docs snippets are missing required imports: add the environ setup
before using env() (e.g., import environ and initialize env = environ.Env() so
SECRET_KEY = env('DJANGO_SECRET_KEY') works) and add the slugify import before
using slugify() (e.g., from django.utils.text import slugify) — update the code
blocks that contain SECRET_KEY/env() and the code that calls slugify() to
include these imports and any minimal initialization.

In `@docs/tr/skills/eval-harness/SKILL.md`:
- Line 263: Metindeki yazım hatasını düzeltin: satırdaki "Geçme oranlarını
kovalamken maliyet ve gecikme kaymasını görmezden gelmek" ifadesinde
"kovalamken" kelimesini "kovalarken" olarak değiştirin (örnekteki cümleyi
güncelleyin).

In `@docs/tr/skills/frontend-patterns/SKILL.md`:
- Around line 298-300: The useMemo block computing sortedMarkets currently calls
markets.sort(...) which mutates the original markets array; change it to sort a
shallow copy to avoid side effects (e.g., create a copy with [...markets] or
Array.from(markets] and then call .sort) inside the useMemo, keeping the
dependency on markets; update the expression around sortedMarkets/useMemo to use
the copied array before sorting so the original markets prop/state is not
mutated.

In `@docs/tr/SPONSORS.md`:
- Line 59: Satırdaki sabit metin "*Otomatik güncellenir. Son senkronizasyon:
Şubat 2026*" çabuk güncelliğini yitirdiği için ya statik tarihi kaldırın ya da
otomatik üretilen bir tarihle değiştirin; örneğin SPONSORS.md içindeki bu metni
bir şablon değişkeni (ör. {{lastSync}} veya LAST_SYNC) ile değiştirin ve doküman
üretim/builder sürecine (CI/build script) güncel tarih atayan adım ekleyin veya
doğrudan metni tamamen kaldırarak yalnızca "Otomatik güncellenir" bırakın.

In `@docs/tr/TERMINOLOGY.md`:
- Around line 42-127: The Durum column currently uses '-' for many rows (e.g.,
entries like "Supabase", "Redis", "Playwright", "Go/Golang", "Docker", etc.),
which is ambiguous; replace all '-' values in the Durum column with the explicit
status "Beklemede" so the table uses only the defined statuses
(Onaylandı/Beklemede), and verify the status legend/description near the top of
the document still matches these two values.

---

Nitpick comments:
In `@docs/tr/agents/build-error-resolver.md`:
- Around line 89-91: Dokümandaki "rm -rf node_modules package-lock.json && npm
install" adımı lockfile'ı gereksiz yere siliyor; bunun yerine lockfile'ı
koruyarak deterministik kurulum yapın: değiştirilecek komut/metin "rm -rf
node_modules package-lock.json && npm install" olarak bulun ve bunu ya sadece
node_modules'i kaldıracak şekilde "rm -rf node_modules && npm ci" ile ya da
lockfile'ı koruyarak tekrar üretmeyecek bir alternatifle (ör. "rm -rf
node_modules && npm install --prefer-offline" veya sadece "npm ci") güncelleyin;
belgenin açıklamasında da lockfile'ı korumanın amacını kısa bir not olarak
ekleyin.

In `@docs/tr/commands/multi-plan.md`:
- Line 40: The phrase for {{GEMINI_MODEL_FLAG}} is ambiguous; replace the
current line with a clearer instruction stating that when using --backend gemini
you should substitute {{GEMINI_MODEL_FLAG}} with --gemini-model
gemini-3-pro-preview (do not include a trailing space) and that for the codex
backend the flag should be an empty string; update the wording to a concise
Turkish sentence like: "`{{GEMINI_MODEL_FLAG}}`: --backend gemini
kullanıyorsanız `--gemini-model gemini-3-pro-preview` ile değiştir (sonunda
boşluk bırakmayın); codex için boş string kullanın."

In `@docs/tr/commands/plan.md`:
- Around line 1-3: Add complete frontmatter fields to the top of the document:
include a "name" key with the Turkish command title, keep the existing
"description" value, and add "command: true" so the file matches other command
docs (e.g., instinct-status.md). Preserve existing content and YAML delimiters
(---) and ensure the new frontmatter keys are ordered and localized consistently
with other Turkish command files.

In `@docs/tr/skills/backend-patterns/SKILL.md`:
- Around line 296-303: Replace the demonstration console.error usage in the
error handler (the block that logs Unexpected error: and returns
NextResponse.json(...)) with a brief comment directing readers to the document's
structured logging example and advising to use a proper logging library in
production; reference the existing structured logging example in this document
and mention the console.error call and the error-handling return
(NextResponse.json) so reviewers can locate and update the error handler to
point to the structured logging pattern.

In `@docs/tr/skills/continuous-learning/SKILL.md`:
- Around line 80-119: Add an explicit "Örnekler" section to the SKILL.md to
match other skill docs and include short example usages and expected outcomes;
ensure the doc also contains the "Ne zaman kullanılır" (When to use) and "Nasıl
çalışır" (How it works) headings if missing. Update the markdown under the
existing "Neden Stop Hook?" and "İlgili" blocks by inserting a new "Örnekler"
heading with 2–3 concise examples (input, brief action, expected result) and
confirm the local headings match the project convention ("When to use" => "Ne
zaman kullanılır", "How it works" => "Nasıl çalışır") so tooling and readers
find them consistently.

In `@docs/tr/skills/docker-patterns/SKILL.md`:
- Around line 1-364: The doc is missing a short "Nasıl Çalışır" (How it works)
overview to match the recommended skill structure; add a brief paragraph-level
section titled "## Nasıl Çalışır" summarizing core concepts (what Docker Compose
does, multi-stage Dockerfile build flow, service discovery via Compose network
names, and volume vs bind mount tradeoffs) and place it between the YAML
frontmatter (containing name: docker-patterns) and the existing "## Ne Zaman
Aktifleştirmeli" heading so readers get a quick conceptual primer before the
usage patterns and examples.

In `@docs/tr/skills/e2e-testing/SKILL.md`:
- Around line 1-326: The skill (name: e2e-testing) is missing the required "Ne
Zaman Kullanmalı" and "Nasıl Çalışır" sections; add two new Markdown sections
titled "## Ne Zaman Kullanmalı" and "## Nasıl Çalışır" near the top (after the
short description/frontmatter) that briefly state when to use the patterns
(e.g., critical user flows, regression prevention, cross-browser testing) and a
short overview of Playwright architecture and the Page Object Model approach
(mention ItemsPage as an example POM) so the document conforms to the standard
skill format.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/tr/README.md`:
- Line 404: In docs/tr/README.md replace the root-English CONTRIBUTING link
target ../../CONTRIBUTING.md with the local Turkish copy (e.g. CONTRIBUTING.md
or ./CONTRIBUTING.md) so the "[CONTRIBUTING.md]" link in the line containing
"'ye bakın." points to the localized docs/tr/CONTRIBUTING.md; apply the same
change for the other occurrence around the previously noted line (the one at the
other occurrence near line 439).
- Line 9: Update the license badge link in the README so it points to the
repository root LICENSE rather than a broken local path; replace the current
badge link target "(LICENSE)" in the line starting with "[![License]" with a
path to the repo root (for example "../../LICENSE" from docs/tr/README.md) so
the badge links correctly to the root LICENSE file.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/tr/README.md`:
- Around line 394-395: The in-page anchors `#cursor-ide-desteği` and
`#-opencode-desteği` referenced in the lines mentioning "Cursor IDE Desteği" and
"OpenCode Desteği" are broken; fix by either adding matching headings (e.g., a
"## Cursor IDE Desteği" and a "## OpenCode Desteği" with content) so the anchors
resolve, or update the two links to point to the actual existing section IDs in
the document if those sections already exist under different slugs; ensure the
anchor text and heading text match exactly so `#cursor-ide-desteği` and
`#-opencode-desteği` become valid targets.

---

Duplicate comments:
In `@docs/tr/README.md`:
- Line 404: Change the localized Turkish link target so it points to the local
contributing file instead of the English root: update the markdown link labeled
"[CONTRIBUTING.md]" in docs/tr/README.md (both occurrences cited) to target
"./CONTRIBUTING.md" rather than "../../CONTRIBUTING.md" so the Turkish docs
navigate to the localized CONTRIBUTING file.

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/tr/commands/instinct-import.md">

<violation number="1" location="docs/tr/commands/instinct-import.md:29">
P2: Usage example recommends importing from a mutable external `main` branch URL, creating avoidable supply-chain risk in behavioral config ingestion.</violation>
</file>