convert-code
Skill7 starsChanged 6 months agoMITView on GitHub
Converts code between programming languages while preserving logic, error handling, and idiomatic patterns. Use when migrating modules between languages or frameworks.
In this repository45 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- a11y-auditSkill
- api-designSkill
- architecture-reviewSkill
- business-blueprintSkill
- business-logic-auditSkill
- changelogSkill
- ci-pipelineSkill
- code-coverageSkill
- competitive-analysisSkill
- create-componentSkill
- db-migrationSkill
- debugSkill
- dependency-auditSkill
- deploy-checklistSkill
- design-flowSkill
- docker-setupSkill
- env-setupSkill
- error-monitorSkill
- estimateSkill
- explain-codeSkill
- fix-issueSkill
- generate-docsSkill
- git-cleanupSkill
- grill-meSkill
- handoffSkill
- legal-pagesSkill
- memory-importSkill
- memorySkill
- microcopySkill
- migrate-frameworkSkill
- onboardSkill
- optimizeSkill
- pr-summarySkill
- refactorSkill
- reference-appSkill
- review-prSkill
- security-scanSkill
- seo-scaffoldSkill
- tddSkill
- web-launch-checkSkill
- wireframeSkill
- write-skillSkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Read the source file completely
- Distinctive: line 15
All functions, classes, and types
- Distinctive: line 24
Don't transliterate — convert to idiomatic target code:
- Distinctive: line 39
If no direct equivalent exists, note it and implement the functionality
- Distinctive: line 65
Write the converted file with proper formatting
- Distinctive: line 66
Add a header comment noting the source and conversion
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Code Conversion
Instructions
Step 1: Analyze Source Code
- Read the source file completely
- Identify:
- All functions, classes, and types
- External dependencies and their equivalents in the target language
- Error handling patterns
- Async/concurrent patterns
- Data structures and their representations
- Tests (if present)
Step 2: Map Language Idioms
Don't transliterate — convert to idiomatic target code:
| Source Pattern | Target Equivalent |
| Python list comprehension | Java streams / Go slices / Rust iterators |
| JS Promise.all | Python asyncio.gather / Go goroutines+WaitGroup / Rust tokio::join |
| Python dict | Go map / Rust HashMap / Java Map |
| JS destructuring | Go multiple returns / Python tuple unpacking |
| Python decorator | Java annotation / Go middleware / Rust macro |
| C# LINQ | Python generators / JS array methods / Rust iterators |
| Ruby blocks | Python context managers / Go defer / Rust closures |
Step 3: Handle Dependencies
For each import/dependency in the source:
- Find the equivalent package/library in the target ecosystem
- If no direct equivalent exists, note it and implement the functionality
- Map API calls to the target library's conventions
Step 4: Convert Error Handling
Different languages handle errors differently:
| Language | Pattern |
| Python | try/except, raise |
| JavaScript/TypeScript | try/catch, throw, Promise rejection |
| Go | Multiple return values (value, error) |
| Rust | Result<T, E>, Option<T>, ? operator |
| Java/C# | try/catch, checked/unchecked exceptions |
| Ruby | begin/rescue/ensure |
| Elixir | {:ok, value} / {:error, reason} tuples |
Convert error handling to the idiomatic pattern of the target language.
Step 5: Convert Types
Map type systems:
- Dynamic → Static: Infer and add explicit types
- Static → Dynamic: Simplify but add runtime checks where safety-critical
- Generics: Map to target language's generic system
- Null safety: Map Optional/Maybe/Option patterns appropriately
Step 6: Generate Output
- Write the converted file with proper formatting
- Add a header comment noting the source and conversion
- Include all necessary imports
- Preserve comments (translate them to the target language's convention)
- Generate a companion test file if tests existed in the source
Step 7: Conversion Notes
Document:
- Patterns that couldn't be directly converted and the approach taken
- Dependencies that have no direct equivalent
- Behavioral differences to be aware of
- Performance characteristics that differ between implementations
Rules
- Idiomatic over literal — code should look like it was written by a native developer
- Preserve behavior — the converted code must do the same thing
- Preserve tests — convert tests too, not just implementation
- Flag risks — note where behavior might differ (floating point, string encoding, concurrency)
- Don't assume — if unsure about a language feature, ask rather than guess
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

