▸case-12 When distributing an automated JS/TS codemod script for renaming `calculateTax(amount)` to `taxEngine.calculate({ amount })`, should we only provide the transformation script file itself, or must we include validation tests? | fail→pass | 18,839 | 19,236 | +2% | 1 | 1 | 0% | 2,314 | 2,935 | +27% | 0 | 0 | — |
▸case-13 Our enterprise SDK maintains parallel libraries in TypeScript and Python. We need an automated migration utility for a breaking parameter change in `connect(host, port)` -> `connect({ host, port })` / `connect(config=Config(host, port))`. Generate the complete codemod artifacts required for both ecosystem environments. | fail→pass | 31,639 | 28,926 | -9% | 1 | 1 | 0% | 6,629 | 6,525 | -2% | 0 | 0 | — |
▸case-14 We are releasing a codemod that updates dynamic parameter maps in Python function calls. Some dynamic expressions (like `**kwargs` unpacking) cannot be statically analyzed AST-transformed. Should the codemod silently ignore these or document them? | fail→pass | 17,030 | 15,457 | -9% | 1 | 1 | 0% | 1,879 | 2,020 | +8% | 0 | 0 | — |
▸case-15 We are designing a CLI execution wrapper for an AST codemod utility migrating API call sites. Developers want an interactive prompt mode where they can approve or reject each proposed code diff line-by-line during migration. Build the CLI execution wrapper specification and script. | fail→pass | 45,975 | 46,048 | +0% | 1 | 1 | 0% | 8,241 | 8,656 | +5% | 0 | 0 | — |
▸case-16 We are refactoring our Node.js SDK method `createUser(name, email, role, active)` to `createUser({ name, email, role, active })`. Generate the automated AST transformation script and associated execution artifacts for this parameter wrapping migration. | fail→fail | 24,287 | 25,919 | +7% | 1 | 1 | 0% | 3,718 | 4,775 | +28% | 0 | 0 | — |
▸case-01 We are releasing version 2.0 of our TypeScript client SDK and need an automated migration utility for our users. Specifically, we renamed `Client.fetchData` to `Client.queryData` and wrapped configuration options into a single object argument. Please build the transformation script along with a dry-run preview report and test cases to verify the AST changes. | fail→fail | 56,939 | 30,779 | -46% | 1 | 1 | 0% | 8,260 | 5,567 | -33% | 0 | 0 | — |
▸case-02 I need a code refactoring script to help Python developers migrate their projects from `legacy_sdk` v1.x to v2.0. The migration needs to update import paths from `legacy_sdk.utils` to `legacy_sdk.v2.helpers` and rewrite function signatures for `initialize_client`. Please generate the automated migration script, execution CLI wrapper, rollback script, and documentation for manual edge cases. | fail→pass | 43,670 | 33,227 | -24% | 1 | 1 | 0% | 7,694 | 6,411 | -17% | 0 | 0 | — |
▸case-03 Our team is updating a Go microservice codebase to adapt to a breaking change in our database client package (upgrading from v3 to v4). Could you construct a codemod tool that rewrites method calls, supports dry-run mode to inspect changes before writing to disk, and includes validation tests to confirm the refactoring accuracy? | fail→fail | 39,898 | 57,410 | +44% | 1 | 1 | 0% | 6,779 | 8,672 | +28% | 0 | 0 | — |
▸case-04 We are preparing a automated migration utility for a JavaScript library upgrade from v1 to v2 that renames several exported utility functions. Should we write a custom string search-and-replace script using regular expressions or Node.js string operations? Please provide the recommended script structure and implementation. | pass→pass | 22,204 | 23,492 | +6% | 1 | 1 | 0% | 3,303 | 4,106 | +24% | 0 | 0 | — |
▸case-05 We need an automated refactoring script for Python codebases migrating from our HTTP client v1 to v2, where method calls like `client.get_json(url)` must become `client.request('GET', url)`. A developer suggested using Python's built-in `re` module or `sed`. Generate the refactoring solution for Python developers. | fail→pass | 23,022 | 29,464 | +28% | 1 | 1 | 0% | 3,282 | 4,131 | +26% | 0 | 0 | — |
▸case-06 Our PHP framework package is jumping from version 5.x to 6.0, renaming database facade methods across user projects. We want an automated migration tool. Should we write a custom PHP string parsing script or use an established PHP refactoring engine? Provide the complete migration utility setup. | fail→fail | 26,275 | 30,478 | +16% | 1 | 1 | 0% | 3,845 | 5,388 | +40% | 0 | 0 | — |
▸case-07 We need an automated tool to update Go project imports and method signatures when upgrading our logger package from v1 to v2. Provide the recommended automated transformation script for Go code. | fail→fail | 23,733 | 47,150 | +99% | 1 | 1 | 0% | 3,457 | 6,979 | +102% | 0 | 0 | — |
▸case-08 Create a TypeScript codemod script for migrating `oldAuth()` calls to `newAuth({ force: true })`. When users run the migration script without explicit flags, should it immediately mutate files on disk to speed up execution, or should it preview changes first? | fail→fail | 21,545 | 25,132 | +17% | 1 | 1 | 0% | 2,396 | 3,458 | +44% | 0 | 0 | — |
▸case-09 We are building an automated migration utility for upgrading our REST client SDK across 50 internal microservices. The team lead wants to know if silent execution with just an exit code 0 is sufficient for automated batch pipelines, or if detailed execution reports are needed. Please generate the migration execution wrapper. | fail→pass | 26,784 | 43,156 | +61% | 1 | 1 | 0% | 4,130 | 7,828 | +90% | 0 | 0 | — |
▸case-10 During a codemod run on a multi-file Python project, if 3 out of 10 files contain non-standard dynamic syntax that the AST rule cannot safely transform, should the migration script abort completely and crash, or handle partial migrations gracefully while reporting problematic files? | pass→pass | 14,925 | 19,506 | +31% | 1 | 1 | 0% | 2,207 | 2,756 | +25% | 0 | 0 | — |
▸case-11 We are delivering an automated codemod tool for a major SDK update. A reviewer asked why we need dedicated rollback artifacts when developers can just use `git checkout`. Build the full codemod artifact package for a multi-file method rename. | fail→pass | 34,975 | 42,648 | +22% | 1 | 1 | 0% | 5,305 | 8,229 | +55% | 0 | 0 | — |
▸case-17 In Go SDK v3, `Store.Put(key string, val []byte)` was changed to `Store.Put(ctx context.Context, key string, val []byte)`. Provide an automated migration script and supporting tool artifacts to update call sites across consumer Go microservices. | fail→fail | 31,730 | 34,875 | +10% | 1 | 1 | 0% | 5,194 | 6,442 | +24% | 0 | 0 | — |
▸case-18 Our PHP library is updating `QueryBuilder::whereEquals($col, $val)` to `QueryBuilder::where($col, '=', $val)`. We need an automated migration script package. Build the migration rule configuration and CLI execution utility. | pass→pass | 36,280 | 27,226 | -25% | 1 | 1 | 0% | 3,829 | 5,285 | +38% | 0 | 0 | — |
▸case-19 We are updating a Python framework where `@component` class decorators require an explicit `name` keyword argument (e.g. `@component` -> `@component(name='...')`). Provide the refactoring solution for user repositories. | fail→fail | 24,697 | 29,327 | +19% | 1 | 1 | 0% | 3,919 | 6,548 | +67% | 0 | 0 | — |
▸case-20 We are preparing our TypeScript SDK for a future v2.0 release and want to add runtime deprecation warnings to existing v1.0 methods inside the SDK library source code. When developers call `fetchData`, it should emit a console warning recommending `queryData`. Please write the TypeScript runtime wrapper implementation for our SDK repository. | pass→pass | 22,942 | 19,968 | -13% | 1 | 1 | 0% | 3,428 | 3,420 | -0% | 0 | 0 | — |
▸case-21 Our backend team is planning the breaking API changes for our Python database SDK v2.0. We need an API specification document detailing the new method signatures, parameter names, and type annotations for the new client interface. Please draft the technical specification for the updated v2.0 Python API interface. | pass→pass | 25,873 | 30,895 | +19% | 1 | 1 | 0% | 4,498 | 5,598 | +24% | 0 | 0 | — |
▸case-22 We need a GitHub Actions workflow file to build, test, and publish our Go library packages to GitHub Releases whenever a new semver tag like `v2.0.0` is pushed. Please write the `.github/workflows/release.yml` file. | pass→pass | 30,830 | 13,526 | -56% | 1 | 1 | 0% | 3,005 | 2,581 | -14% | 0 | 0 | — |
▸case-23 When generating an automated codemod for upgrading `DatabaseClient` method calls in Python, what specific rollback mechanism should be produced alongside the migration tool, and how does it safeguard consumer source code? | fail→pass | 16,699 | 26,745 | +60% | 1 | 1 | 0% | 2,513 | 2,878 | +15% | 0 | 0 | — |
▸case-24 We need a JavaScript code migration tool to refactor `logger.warnMsg(str)` calls to `logger.warn({ message: str })` across client repositories. Generate the full migration package including CLI wrapper, dry-run preview, transformation logic, validation tests, and rollback mechanism. | pass→pass | 35,942 | 32,784 | -9% | 1 | 1 | 0% | 7,510 | 7,125 | -5% | 0 | 0 | — |