Keeping up with major Drupal Core releases takes real effort. Each release deprecates APIs and introduces new coding patterns, forcing module developers to update their code. That is how most software evolves: old patterns are gradually replaced by better ones. Tools like Drupal Rector help automate parts of that work, but still rely on hand-written rules. Historically, that hasn't scaled well. Writing Rector rules is often more tedious than difficult: reading change records, understanding edge cases, finding real-world usage patterns, and testing rules. So I asked a different question: what if we didn't have to write Rector rules at all? If AI can generate Rector rules automatically, Drupal Core can keep evolving without every API change turning into manual migration work. That idea led me to extend Drupal Digests , the tool I built to follow key Drupal developments . In addition to generating summaries, it now also analyzes Drupal Core commits and generates Rector rules automatically.…