turkce-kod
Write Turkish Code Documentation
Turkish software teams need consistent documentation, comments, commit messages, and terminology. This skill helps Claude, Codex, and Claude Code produce clear Turkish developer text.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "turkce-kod" from https://skillstore.io/skills/cesareth-turkce-kod.md and its manifest at https://skillstore.io/api/skills/cesareth-turkce-kod/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "turkce-kod". A developer asks for Turkish comments on session validation logic.
Expected outcome:
- The response explains the reason for validation and permission checks.
- It avoids comments that only restate each operation.
- It keeps framework terms understandable for the team.
Using "turkce-kod". A maintainer needs a Turkish commit message for moving invoice logic into a service layer.
Expected outcome:
The response provides a short Turkish subject and an optional body explaining the architectural reason.
Using "turkce-kod". A team wants Turkish technical terms for API and security documentation.
Expected outcome:
The response suggests consistent Turkish equivalents and notes terms that are commonly kept in English.
Security Audit
SafeAll 54 static findings are false positives caused by Markdown backticks in SKILL.md. The skill provides documentation guidance and examples; no executable script, command execution path, prompt injection, or data exfiltration intent was found.
Risk Factors
⚙️ External commands (54)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/cesareth-turkce-kod/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/cesareth-turkce-kod?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/cesareth-turkce-kod?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cesareth-turkce-kod/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/cesareth-turkce-kod.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
cesareth. (2026). turkce-kod security audit report (audit version 4) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/cesareth-turkce-kod/audits/4BibTeX citation
@techreport{cesareth-cesareth-turkce-kod-2026,
author = {cesareth},
title = {turkce-kod security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/cesareth-turkce-kod/audits/4},
note = {Author version 1.0.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "turkce-kod security audit report (audit version 4)"
version: "1.0.0"
type: report
authors:
- name: "cesareth"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/cesareth-turkce-kod/audits/4"
identifiers:
- type: other
value: "skillstore:cesareth-turkce-kod:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Document Backend Logic
Write Turkish comments and error messages that explain business rules without repeating obvious code.
Prepare Project README Text
Create Turkish README sections for setup, quick start, features, configuration, contribution, and license notes.
Standardize Team Language
Align commit labels, domain terms, log messages, and naming choices across a Turkish software team.
Try These Prompts
Add Turkish comments to this function. Explain why important decisions exist, and avoid comments that repeat obvious code.
Write a Turkish commit message for this change. Use the project type labels and keep the subject under 72 characters.
Draft Turkish README sections for installation, quick start, configuration, contribution, and license. Keep the text direct and practical.
Review these names, messages, and docs for Turkish terminology consistency. Recommend which terms should remain English and explain why.
Best Practices
- Use Turkish for domain concepts and keep established framework terms in English when teams expect them.
- Explain why code exists, not only what each line does.
- Keep commit subject lines short and add context in the body when needed.
Avoid
- Mixing Turkish and English names without a project rule.
- Translating framework keywords in ways that confuse developers.
- Writing comments that repeat obvious code behavior.
Frequently Asked Questions
Does this skill write production code?
Can it help with README files?
Should every technical term be translated?
Can it enforce a team naming standard?
Does it run shell commands?
Which tools can use it?
Developer Details
Author
cesarethLicense
MIT
Author version
v1.0.0
Skillstore revision
r1
Ref
dd4a3ef9f20ddf38830950b4bb713df96b431fd6
Maintenance freshness
7/20/2026
Usage
4 downloads · 128 views
File structure