Repository navigation
refactor(DCT-587): rename aitaskbuilder command to taskbuilder - #554
Open
script-this wants to merge 2 commits into
Open
script-this wants to merge 2 commits into
script-this wants to merge 2 commits into
Conversation
Drop "AI" from the Task Builder name in the CLI. - Rename `prolific aitaskbuilder` to `prolific taskbuilder` and move the package to cmd/taskbuilder. - Keep `prolific aitaskbuilder` as a hidden alias. It runs the same subcommands and prints a "has moved" notice to stderr (on help, flag errors and normal runs), with usage showing the new command. Stdout is unchanged. - Update help text, output headings and examples from "AI Task Builder" to "Task Builder", including the collection commands. - Rename the example files and orchestration script, and update the README, DEVELOPMENT.md, changelog script and CHANGELOG. Wire identifiers (AI_TASK_BUILDER_* values, operationIds, client method names) are unchanged. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The published spec's operationIds change from aiTaskBuilder_<Op> to taskBuilder_<Op> when the Task Builder rename is published to the docs site. Use the new prefix in the contract test's coverage table and README, and map the legacy prefix to it when reading the spec, so the contract test and README generator pass against the spec both before and after that publish. The mapping can be removed once only the new prefix is published. Merge order: independent of the monolith docs publish (DCT-586); this branch can merge before or after it. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
benmatselby
approved these changes
Nov 5, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What's been changed?
Drops "AI" from Task Builder in the CLI (DCT-587).
prolific aitaskbuilderis nowprolific taskbuilder(package moved tocmd/taskbuilder). Help text, examples, output headings and thecollectionhelp now say "Task Builder".prolific aitaskbuilderstill works as a hidden alias: same subcommands, a "prolific aitaskbuilderhas moved, did you meanprolific taskbuilder?" notice on stderr (on help, flag errors and normal runs), usage shown with the new command, stdout unchanged so scripts that parse output keep working.taskbuilder-model-evaluation.csv,standard-sample-taskbuilder.json,study-with-task-builder-collection.json) and the orchestration script updated. README, DEVELOPMENT.md, the changelog script and CHANGELOG (## next) updated.taskBuilder_operationId prefix, and the legacyaiTaskBuilder_prefix in the live spec is mapped to it. Passes against the spec before and after the docs rename is published.Unchanged on purpose: the
AI_TASK_BUILDER_*wire values, client method names (tied to operationIds) and mocks.Why?
Marketing is renaming AI Task Builder to Task Builder; no human should see the old name in the CLI, UI, API or docs.
How I tested
make test,make lint(Go 1.26),make build.taskbuilder batch listvsaitaskbuilder batch listgave identical stdout (exit 0), notice only on the old command's stderr; read commands (batch view/check/tasks/responses,dataset check,batch export list) matched; wrote a dataset, uploaded the renamed example CSV, created a batch, and created a dataset through the alias.TestAPICoveragepasses against the live spec and against the regenerated new spec (served locally).TestClientMatchesAPISpecfails against the monolith's main spec in the same way with or without this change (studies_DuplicateStudy).Breaking changes
None for users:
aitaskbuilderkeeps working with a notice. The README and contract table use the new operationId prefix.Merge order
Merge after the monolith PR (prolific #17238) is deployed to production, which publishes the Fern docs. It would also pass before, because it accepts both prefixes. Remove the legacy-prefix mapping once only
taskBuilder_is published.Screen recording
n/a
Checklist
🤖 Generated with Claude Code