# 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

```bash
npx skillstore add cesareth/turkce-kod
```

## Metadata

- Status: approved
- Slug: cesareth-turkce-kod
- Version: 1.0.0
- Author version: 1.0.0
- Skillstore revision: r1
- Version status: valid
- Tree hash: 6a31dc35d32a795d96607f1c625fe7782c1847e481c930457e86f32d99f39fd0
- Author: cesareth
- GitHub username: cesareth
- License: MIT
- Repository: https://github.com/cesareth/hermes-turkce-skills/tree/main/turkce-kod
- Ref: dd4a3ef9f20ddf38830950b4bb713df96b431fd6
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 76
- Public page: https://skillstore.pages.dev/skills/cesareth-turkce-kod
- Manifest: https://skillstore.pages.dev/api/skills/cesareth-turkce-kod/manifest

## Capabilities

- Creates Turkish comment guidance for Python, TypeScript, and Go examples.
- Suggests Turkish variable, function, and domain naming conventions.
- Formats commit messages with Turkish type labels and concise summaries.
- Drafts README sections for setup, quick start, configuration, contribution, and license details.
- Provides Turkish equivalents for common software, API, DevOps, security, and data terms.

## Use Cases

- 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.

## Prompt Templates

### Add Turkish Comments

```
Add Turkish comments to this function. Explain why important decisions exist, and avoid comments that repeat obvious code.
```

### Create a Turkish Commit Message

```
Write a Turkish commit message for this change. Use the project type labels and keep the subject under 72 characters.
```

### Draft a Turkish README Section

```
Draft Turkish README sections for installation, quick start, configuration, contribution, and license. Keep the text direct and practical.
```

### Standardize Project Terminology

```
Review these names, messages, and docs for Turkish terminology consistency. Recommend which terms should remain English and explain why.
```

## Limitations

- Does not validate code correctness or run tests.
- Does not translate every framework term when English is the common standard.
- Requires project context to choose consistent naming and tone.
- Contains documentation examples, not executable automation.

## 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.

## Anti Patterns

- Mixing Turkish and English names without a project rule.
- Translating framework keywords in ways that confuse developers.
- Writing comments that repeat obvious code behavior.

## Security Audit

- Audited at: 2026-07-06T05:03:30.356\+00:00
- Summary: All 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.

## Stats

- Views: 128
- Downloads: 8
- Favorites: 0
- Popularity score: 0