Kata Forge: The Language Sprint is now in its final stretch. If you missed the Discord announcement, this is a community authoring challenge built around the recent nine Codewars language runtime updates.
The idea is simple: create a new kata, or translate an existing kata into a language it does not support yet, using one of the updated runtimes. The community votes for the best submission in each language, and each language winner receives a $50 gift card.
Submission window extended: Wednesday, July 1, 2026, at 12 p.m. ET / 4 p.m. GMT.
Voting opens: Wednesday, July 1, 2026, at 2 p.m. ET / 6 p.m. GMT.
Voting closes: Friday, July 3, 2026, at 2 p.m. ET / 6 p.m. GMT.
This follow-up is here to make sure more of the wider Codewars community sees the challenge while there is still time to take part.
How Kata Forge works
Kata Forge is open to everyone. You can enter by writing a new kata or by translating an existing kata into one of the eligible languages it does not already support.
Translations count because they expand the kata library and make more challenges available to more developers. New kata count when they make meaningful use of one of the updated runtimes.
Eligible languages
| Language | Updated runtime |
|---|---|
| JavaScript | Node 22 |
| TypeScript | 5.7 |
| Rust | ~1.86 |
| Go | 1.24 |
| Kotlin | 2.1 |
| Swift | 6 |
| Java | 21 |
| PHP | 8.4 |
| C# | 13 on .NET 9 |
All nine languages are equal-standing, with one winner per language.
What counts as a submission?
Your kata should make meaningful use of the updated runtime. That could be a new language feature, a modern idiom, a standard library capability, a testing approach, or a language-specific improvement.
The runtime usage can show up in your solution, your tests, or both. If you are translating an existing kata, make sure the language you choose is not already supported by that kata.
How to submit
- Create a new kata or translation on Codewars as a draft or beta.
- Add this structured first comment on your kata:
#kata-forge
Track: Build
Language: [language]
What it is: [one sentence]
Runtime usage: [how you used the updated version]
AI-assisted: [optional - one sentence on how you used it]No external form. No separate submission platform. Just your kata and the #kata-forge comment.
Need an idea?
Start small. Pick a runtime you are curious about, look at what changed, and build a kata that highlights one clear feature or improvement. The runtime update post is a good place to look for inspiration.
You might create a kata around a new language feature, modernize an existing kata through translation, or write tests that take advantage of newer runtime behavior.
Final call: build something with them.
If you have been meaning to author, translate, or polish something for Kata Forge, this is the window to finish it.
Submissions close Wednesday, July 1, 2026, at 12 p.m. ET / 4 p.m. GMT. Voting starts two hours later.
Read the contest terms and conditions for full details.
See you in the kata editor.
