document-gotchas

Automated extraction of development gotchas from session insights involves scanning JSON files to pull common mistakes and anti-patterns from fields like `gotchasFound`, `discoveries`, and `patternsLearned` into a centralized repository.

Consolidating tricky development issues into a searchable knowledge base requires categorizing and deduplicating extracted gotchas, then generating dual markdown and JSON outputs for both human readability and machine processing.

Deduplicating and categorizing anti-patterns during post-session analysis is automated by processing session insights to remove repeated mistakes and assign distinct categories before writing them to a knowledge base.

Yes, generating both markdown and JSON outputs for a centralized gotchas repository is supported, producing human-readable `gotchas.md` and machine-readable `gotchas.json` files for continuous improvement workflows.

Consolidating development gotchas requires no external dependencies, relying solely on internal scripts to parse JSON insight files and generate the markdown and JSON knowledge base outputs.

You should run a gotchas knowledge base update after any development session where tricky issues or anti-patterns are encountered, applying it to post-session analysis to ensure continuous improvement workflows capture new mistakes.