Go Surgeon — AI skill for Claude Code

---

The problem nobody admits

Ask your agent to update a single function in a 200-line Go file. Watch what happens:

1. It Reads the file, finds the function, plans the edit
2. It calls Edit with a string replacement — misses a trailing tab
3. The patch fails. It re-reads the file. Tries again with the whole function body
4. This time it forgets the context.Context import
5. go build fails. It edits the import block — badly. Curly brace drift.
6. Three turns later you have a working file and no idea what changed.

Every Go dev using an LLM agent has lived this. The problem isn't the model's reasoning — **text-level patching is fundamentally wrong for a structured language**. Indentation, imports, braces: these aren't content, they're grammar. And grammar breaks loudly.

The fix

update(object="func", file="internal/catalog/domain/book.go", identifier="NewBook", content="""
func NewBook(title, author string) (*Book, error) {
    return &Book{Title: title, Author: author}, nil
}
""")

✅ SUCCESS (update func): Updated NewBook in internal/catalog/domain/book.go

Locat