// Use when working on Codemod's Rust workspace, including workflow engine crates, models, state, runners, scheduler, CLI-adjacent Rust crates, schema generation, Cargo features, Rust tests, clippy, rustfmt, or CI parity.
| name | codemod-rust-workspace |
| description | Use when working on Codemod's Rust workspace, including workflow engine crates, models, state, runners, scheduler, CLI-adjacent Rust crates, schema generation, Cargo features, Rust tests, clippy, rustfmt, or CI parity. |
AGENTS.md for the crate you are changing.butterflow-models: workflow schema/data contracts.butterflow-core: execution engine, step execution, reports, git/file operations.butterflow-state: state adapters.butterflow-runners: Docker/Podman/direct runner abstractions.butterflow-scheduler: task scheduling and WASM package logic.codemod: CLI command surface and TUI.codemod-sandbox: JSSG runtime and sandbox.testing-utils: shared test helpers.Cargo.toml.crates/models; avoid duplicate public structs in higher-level crates.crates/cli choose text, TUI, JSONL, or task-log routing.docker, podman, wasm, native, and real-fs.cargo xtask schema and review generated diffs.cargo test -p <crate>cargo testcargo fmt --checkcargo clippy --tests --no-deps -- -D warningsbash ./scripts/check-single-crossterm.shUse when editing Codemod documentation, Mintlify MDX, docs navigation, CLI/JSSG/workflow/platform docs, docs snippets, examples, troubleshooting, or technical writing under docs/.
Use Codemod CLI whenever the user wants to migrate, upgrade, update, or refactor a codebase in a repeatable way. This includes framework migrations, library upgrades, version bump migrations, API surface changes, deprecations, large-scale mechanical edits, codemod package authoring, AST inspection, tree-sitter node type lookup, and Codemod documentation lookup through `codemod ai` commands. First search the Codemod Registry for an existing package, prefer deterministic codemods before open-ended AI rewrites, run dry-runs before apply, and create a codemod package only when no suitable package exists.
Use Codemod CLI whenever the user wants to migrate, upgrade, update, or refactor a codebase in a repeatable way. This includes framework migrations, library upgrades, version bump migrations, API surface changes, deprecations, large-scale mechanical edits, codemod package authoring, AST inspection, tree-sitter node type lookup, and Codemod documentation lookup through `codemod ai` commands. First search the Codemod Registry for an existing package, prefer deterministic codemods before open-ended AI rewrites, run dry-runs before apply, and create a codemod package only when no suitable package exists.
Use when changing Codemod CLI commands, terminal UI, workflow command behavior, auth/login, publish/search/unpublish, init templates, report server, npm CLI wrapper, quiet-mode output, terminal dependencies, or command tests.
Use when working on JSSG, Codemod's JavaScript/TypeScript sandbox, ast-grep bindings, QuickJS runtime, WASM/native sandbox behavior, runtime module shims, sandbox capabilities, packages/jssg-types, packages/jssg-utils, or codemod author APIs.
Use when changing Codemod semantic analysis providers, language-core traits, JavaScript/TypeScript provider behavior, Python provider behavior, semantic-factory routing, tree-sitter loader behavior, goto-definition, find-references, or semantic integration tests.