菜单
Use this skill when editing any docs/reference/* or other bilingual documentation pairs in ForgeLM. Keeps the .md and -tr.md mirrors structurally aligned per docs/standards/localization.md. Triggered by requests like "update the configuration docs", "add a section about X to the usage guide", "translate the new feature docs".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use this skill when adding a new YAML configuration field to ForgeLM. Handles Pydantic model update, cross-field validation, config_template.yaml sync, bilingual docs, and tests. Triggered by requests like "add a new config option for X", "expose Y as a YAML field", "make Z configurable".
Use this skill when reviewing a pull request to ForgeLM, whether your own (self-review before requesting review) or someone else's. Applies the code-review standard, catches anti-patterns, and produces actionable feedback. Triggered by requests like "review this PR", "check if PR
Use this skill when reviewing a pull request to ForgeLM, whether your own (self-review before requesting review) or someone else's. Applies the code-review standard, catches anti-patterns, and produces actionable feedback. Triggered by requests like "review this PR", "check if PR
Use this skill when preparing a ForgeLM release. Walks through version bump, changelog finalization, tag, publish, and post-release sync per docs/standards/release.md. Triggered by requests like "cut v0.4.0", "release ForgeLM", "prepare the next version".
Use this skill when writing new tests for ForgeLM. Applies conventions from docs/standards/testing.md — fixture factory patterns, mock boundaries, no-GPU-no-network discipline, coverage floor. Triggered by requests like "add a test for X", "cover function Y", "write a test that triggers error Z".
Use this skill when adding a substantial end-to-end feature to ForgeLM's training pipeline — a new alignment method, a new evaluation gate, a new quantization backend, a new distributed scheme. Differs from add-config-field by touching multiple modules and requiring integration tests. Triggered by requests like "add support for algorithm X", "integrate library Y for training", "implement feature from roadmap Phase N".
| name | sync-bilingual-docs |
| description | Use this skill when editing any docs/reference/* or other bilingual documentation pairs in ForgeLM. Keeps the .md and -tr.md mirrors structurally aligned per docs/standards/localization.md. Triggered by requests like "update the configuration docs", "add a section about X to the usage guide", "translate the new feature docs". |
ForgeLM ships user-facing docs in English + Turkish. The mirrors must stay in structural sync or readers switching languages get confused and CI (future) will complain.
Any change to these paths or their siblings:
docs/README.md (if bilingual)docs/product_strategy.md / product_strategy-tr.mddocs/roadmap.md / roadmap-tr.mddocs/reference/*.md (has matching -tr.md)docs/usermanuals/{en,tr}/**/*.md (the static-site SPA viewer source)Do not use for:
docs/standards/* (English only)docs/marketing/* (gitignored working-memory; mixed languages)docs/qms/* (English only)docs/design/* (English only)docs/guides/* (English only for now — Turkish is future work)Do not reference any file under gitignored working-memory directories
(docs/marketing/, docs/analysis/) from the bilingual docs you edit —
those paths are local-only and won't resolve in fresh clones.
docs/usermanuals/ is link-isolated. Pages there feed the static-site
SPA viewer (site/usermanual.html), which only renders SPA hash-router
routes (#/<section>/<page>) and external HTTPS URLs. Repo-relative
links like ../../../guides/foo.md or even intra-manual paths like
../concepts/choosing-trainer.md 404 in the SPA. When you edit a
usermanual page, every link MUST be one of:
#/<section>/<page> where the target file exists under
docs/usermanuals/<lang>/<section>/<page>.md.https://github.com/HodeTech/ForgeLM/blob/main/<path>
for project files that live outside the manual — guides, references,
QMS templates, source files, the roadmap).#heading-slug).The guard tools/check_usermanual_self_contained.py --strict enforces
this; see docs/standards/documentation.md "User-manual link discipline"
for the full ruleset.
1. Edit file.md (English)
2. Same PR: edit file-tr.md — add matching section in same position
3. Verify H2 count matches: grep -c "^## " docs/reference/X.md equals grep -c "^## " docs/reference/X-tr.md
4. Verify links in TR point to TR mirrors (-tr.md) where those exist
5. Commit together
Same workflow, mirrored. But: the EN version is canonical — if you're writing new content, write the EN first, then mirror.
Acceptable fallback (for non-native-speaker contributors):
file.md (English)<!-- TR translation pending, tracked in #ISSUE --> at the top of file-tr.md for the new sectiontranslation-debtDo not paste untranslated English into the TR file. Either translate properly or mark pending explicitly.
If the EN file (say docs/reference/foo.md) says:
See [Architecture](architecture.md) for the module layout.
The TR file (docs/reference/foo-tr.md) should say:
Modül yapısı için [Mimari](architecture-tr.md) belgesine bakın.
Both link text and target translate. A TR reader clicking an EN link mid-document is a UX bug.
# H2 count must match
EN_COUNT=$(grep -c "^## " docs/reference/configuration.md)
TR_COUNT=$(grep -c "^## " docs/reference/configuration-tr.md)
[ "$EN_COUNT" = "$TR_COUNT" ] && echo "OK" || echo "MISMATCH"
# Links to other bilingual files should use -tr.md from TR files
grep -E "\]\([^)]+\.md\)" docs/reference/configuration-tr.md | \
grep -v "\-tr\.md" | \
grep -v "^.*standards/" # standards are EN only, allowed
# Should produce no output
(These aren't enforced by CI yet, but the rules are the same.)
Consistent glossary from localization.md:
| English | Turkish |
|---|---|
| fine-tuning | ince ayar |
| training | eğitim |
| config / configuration | yapılandırma / config |
| pipeline | pipeline (tercih) / boru hattı |
| safety evaluation | güvenlik değerlendirmesi |
| audit trail | denetim izi |
| compliance | uyumluluk |
| quantization | quantization (çevirmeyi zorlama) |
| layer | katman |
| tokenizer | tokenizer |
| EU AI Act | EU AI Act (ilk kullanımda: AB Yapay Zekâ Yasası) |
Acronyms (LoRA, PEFT, DPO, GRPO) stay unchanged in both languages.
The file list in localization.md marks which paths have TR mirrors. If you're working on one that doesn't:
add-config-field — always touches configuration.md + configuration-tr.mdadd-trainer-feature — typically touches multiple docs/reference/ filescut-release — CHANGELOG updates don't need a TR mirror (English only)