mirror of
https://github.com/davila7/claude-code-templates.git
synced 2026-09-19 01:30:23 +08:00
Daniel Avila
c754650ab9
* improve: enhance legacy-modernizer based on automated review
- Add missing model: sonnet frontmatter field (was required but absent)
- Add explicit ownership/hand-off statement clarifying scope vs
architecture-modernizer, refactoring-specialist, cloud-migration-specialist,
and database-optimizer
- Add concrete "Common legacy stacks & upgrade paths" section (COBOL,
Java EE/WebLogic, .NET Framework, AngularJS, Python 2, PHP 5/7)
- Add "AI-assisted analysis" guidance (dependency mapping, codemods,
auto-generated characterization tests)
- Replace vague filler bullets ("Team trained effectively", "Celebrate wins",
"Business value delivered continuously") with concrete, actionable deliverables
- Diversify description examples: replaced a redundant strangler-fig example
with a distinct mainframe/COBOL + version-upgrade-only scenario
Automated review cycle | Co-Authored-By: Claude Code <noreply@anthropic.com>
* fix: address greptile review feedback on legacy-modernizer
Align the third description example's context with what it actually
demonstrates (.NET Framework version-upgrade only), and de-duplicate
the implementation-approach bullets that repeated the checklist items
verbatim.
* fix: address cubic review feedback on legacy-modernizer accuracy
Scope the .NET Framework upgrade path (Web Forms/WCF have no direct
Upgrade Assistant port and need separate plans), note 2to3 was removed
in Python 3.13+, and clarify that Grep/Glob only inventories
dependencies rather than producing a validated call graph.
* fix: soften zero-risk claim in legacy-modernizer example commentary
Version-only upgrades can still change runtime/dependency/batch
behavior; describe risk minimization via validation and rollback
instead of guaranteeing zero production risk.
---------
Co-authored-by: Claude <noreply@anthropic.com>