diff options
| author | Claude <noreply@anthropic.com> | 2026-11-19 01:38:59 +0000 |
|---|---|---|
| committer | Claude <noreply@anthropic.com> | 2026-11-19 01:38:59 +0000 |
| commit | fc515815fa14ab96bebc363a5f42e79a7f571158 (patch) | |
| tree | 796871d943efb9f92635f2cb62a34498d82d300e /plugins/code-modernization/agents | |
| parent | 4d9854e0873b9d068fb444c8b14d00278ce2402a (diff) | |
code-modernization: look up whether a target version is supported before proposing itcode-modernization/supported-target-versions
Commands proposed language and framework versions from the model's memory, which is older than today, so a plan could name a release that is already out of support. A shared rule (references/target-versions.md) now has each command look versions up, record them in a Target versions table with the support end date and source, keep a version the person chose with a warning, and mark a version that could not be checked as unverified instead of guessing. Version 1.1.0.
Diffstat (limited to 'plugins/code-modernization/agents')
4 files changed, 12 insertions, 3 deletions
diff --git a/plugins/code-modernization/agents/architecture-critic.md b/plugins/code-modernization/agents/architecture-critic.md index a170dac1..0017b083 100644 --- a/plugins/code-modernization/agents/architecture-critic.md +++ b/plugins/code-modernization/agents/architecture-critic.md @@ -19,6 +19,11 @@ For **architecture proposals**: unstated, and does the design accidentally violate them? - What's the data migration story? "We'll figure it out" is a finding. - What happens when service X is down? Trace one failure mode end-to-end. +- Does every language, runtime, framework, database and platform have a + version, a support end date and the source it was checked against? One that + is missing, unsourced or out of support is a **High** finding, unless it is + marked `unverified` for a person to confirm or the person chose it knowingly. + You cannot look versions up: judge the record, not your memory. For **transformed code**: - Is this idiomatic for the target stack, or is legacy structure leaking diff --git a/plugins/code-modernization/agents/scaffolder.md b/plugins/code-modernization/agents/scaffolder.md index 2626a579..2f130b6d 100644 --- a/plugins/code-modernization/agents/scaffolder.md +++ b/plugins/code-modernization/agents/scaffolder.md @@ -11,7 +11,11 @@ service boundaries, interface contracts, behavior-contract rules — exactly. ## What you produce -- Project skeleton for the stack named in the architecture +- Project skeleton for the stack named in the architecture, on exactly the + versions in its Target versions table. For a dependency not in the table, + use the newest stable release the package registry reports that is + compatible, never a version from memory. A version that cannot be resolved + is a blocker: report it, do not substitute another - Domain model - API stubs matching the interface contracts in the spec - **Executable acceptance tests** for every behavior-contract rule assigned diff --git a/plugins/code-modernization/agents/test-engineer.md b/plugins/code-modernization/agents/test-engineer.md index 247d2a55..5f281358 100644 --- a/plugins/code-modernization/agents/test-engineer.md +++ b/plugins/code-modernization/agents/test-engineer.md @@ -64,7 +64,7 @@ to do it unless the plan the person approved names that target. ## Output -Idiomatic tests for the requested target stack (JUnit 5 / pytest / Vitest / +Idiomatic tests for the requested target stack (JUnit / pytest / Vitest / xUnit), one test class/file per legacy module, test method names that read as specifications. Include a `README.md` in the test directory explaining how to run them and how to add a new case. diff --git a/plugins/code-modernization/agents/version-delta-analyst.md b/plugins/code-modernization/agents/version-delta-analyst.md index e8624e18..02faedcb 100644 --- a/plugins/code-modernization/agents/version-delta-analyst.md +++ b/plugins/code-modernization/agents/version-delta-analyst.md @@ -1,6 +1,6 @@ --- name: version-delta-analyst -description: Identifies the breaking changes between two versions of the SAME stack (e.g. .NET Framework 4.8 → .NET 8, Java 8 → 17/21, Spring Boot 2 → 3) that actually bite a given codebase, and drives the ecosystem's migration tooling. Use for same-stack uplifts, where code is preserved and tweaked — not rewritten from intent. (Note — some "same-stack" bumps are really rewrites — Python 2 → 3 with pervasive str/bytes, AngularJS → Angular — where minimal-diff fails; flag those for /code-modernization:modernize-transform.) +description: Identifies the breaking changes between two versions of the SAME stack (e.g. .NET Framework → modern .NET, Java 8 → a current LTS, Spring Boot 2 → the current release) that actually bite a given codebase, and drives the ecosystem's migration tooling. Use for same-stack uplifts, where code is preserved and tweaked — not rewritten from intent. (Note — some "same-stack" bumps are really rewrites — Python 2 → 3 with pervasive str/bytes, AngularJS → Angular — where minimal-diff fails; flag those for /code-modernization:modernize-transform.) tools: Read, Glob, Grep, Bash --- |
