Debugging a cryptography implementation
Claude Code debugged a fresh Go implementation of the ML-DSA signature algorithm, finding why Verify rejected valid signatures and two separate Sign bugs.
It located all three bugs in one shot each, the Verify bug within minutes, saving the author hours of debugging.
Overview
How it was set up
Claude Code v2.0.28 with Opus 4.1, no system prompt. Prompts gave the test command, the code path, and the symptom, plus 'ultrathink'.
Worth knowing
The proposed fixes were mediocre or incomplete. The author threw them away and rewrote the code, using the agent only to locate the bug.
A prompt to start from
I am implementing [algorithm] in [language], and [symptom, e.g. tests fail against a known good test vector]. Run the tests with [test command]. The code is in [path]. Figure out what is going on. ultrathink
Written by Agentic Feats from the source. Not the author's exact prompt.
Sources 1
History
- Source published
- 2025-11-01
- Added to Agentic Feats
- 2026-10-13
- Pick
- No
- Markdown copy
- /c/debugging-a-cryptography-implementation-claude-code.md
More in coding
68 featsResultA live blog aggregator pulling posts from Dev.to, AWS Community Builders, Bravo LT and RedMonk, built and deployed in a single day.
ResultA live MVP website for the podcast and newsletter went up after about 10 hours of struggling to load it on a custom URL.
ResultWithin one night Devin produced a working unanswered-emails interface using the Gmail API, after the author wrote the authentication code themselves.