[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74EJS72VSR4S5ZSPB0M197M":3,"skill-same:01M74EJS72VSR4S5ZSPB0M197M":57},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M74EJS72VSR4S5ZSPB0M197M","gears",null,"cli reference to help with the development of constructor fabric gears framework. It helps with the development of the framework from its initialization, adding\u002Fremoving gears, modifying configuration files, build and\u002For run project, lint the project and managing applications through its manifest.\nAlways load this skill whenever you detect Gears.toml or you locate a reference to gears, cargo-gears, gears-toolkit, gears, plugins or packages that include the prefix cf- in its name.","constructorfabric\u002Fcargo-gears","constructorfabric","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F286363322?v=4","01M74EHWDT73DH7WYE949KK2Y7","Constructor Fabric","01M74EHWEBE9GNT74CJC9DVJ3A",5,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fconstructorfabric\u002Fcargo-gears\u002Fblob\u002Fmain\u002Fcrates\u002Fcargo-gears-core\u002Fshared\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: gears\ndescription: cli reference to help with the development of constructor fabric gears framework. It helps with the development of\n  the framework from its initialization, adding\u002Fremoving gears, modifying configuration files,\n  build and\u002For run project, lint the project and managing applications through its manifest.\n\n  Always load this skill whenever you detect Gears.toml or you locate a reference to gears, cargo-gears, gears-toolkit,\n  gears, plugins or packages that include the prefix cf- in its name.\n---\n\n# General Guidelines to follow\n\n- When adding new dependencies use `cargo add`, do not edit Cargo.toml manually\n- When linting, use lint command of the cli to check if there are any lint errors.\n  Do not try to run cargo check, clippy or fmt by your own.\n- Always verify that the application runs successfully after modifying the code.\n- Unless the user specifically mentions to use a custom module, prefer to use system gears\n  instead of implementing your own ones. Pay attention to the \"deps\" section of the gears, as the module will be\n  required to be added in order to be used.\n- Do not try to create a module from scratch, always use the generate module command to create a new module.\n\n## Invocation Forms\n\nThe crate exposes a single entrypoint:\n\n- **[`cargo gears`]** Cargo subcommand form via the `cargo-gears` binary\n\nExample:\n\n```bash\ncargo gears generate workspace \u002Ftmp\u002Fmy-app\n```\n\n## Objective\n\nThis CLI is a tool for automating gears development, a Rust framework. You can get more information about it in:\n\n- Gears repository main: https:\u002F\u002Fgithub.com\u002Fconstructorfabric\u002Fcyberware-rust\n- Gears libraries(the ones that leverage this CLI tool) are located\n  in https:\u002F\u002Fgithub.com\u002Fconstructorfabric\u002Fcyberware-rust\u002Ftree\u002Fmain\u002Flibs\n- More documentation of the project will be located in https:\u002F\u002Fgithub.com\u002Fconstructorfabric\u002Fcyberware-rust\u002Ftree\u002Fmain\u002Fdocs\n\nClone(shallow) the repo to .gears folder (create it if it doesn't exist), and use it as a reference.\nIf so, prefer to use the ssh version instead of https to avoid authentication issues.\n\n## Command Tree\n\n```text\ncargo gears\n├── generate\n│   ├── workspace\n│   ├── gear\n│   └── config\n├── new\n├── config\n│   ├── mod\n│   │   ├── add\n│   │   ├── db\n│   │   │   ├── add\n│   │   │   ├── edit\n│   │   │   └── rm\n│   │   └── rm\n│   └── db\n│       ├── add\n│       ├── edit\n│       └── rm\n├── src\n├── help\n│   ├── schema\n│   ├── src\n│   └── topic\n├── lint\n├── ls\n│   ├── gears\n│   ├── templates\n│   ├── features\n│   ├── deps\n│   ├── packages\n│   └── targets\n├── manifest\n│   ├── validate\n│   └── ls\n├── test\n├── tools\n│   └── check-version\n├── run\n├── build\n├── clean\n└── deploy\n```\n\n## Shared Argument Patterns\n\n- **[`-p, --path \u003CPATH>`]** Optional workspace path. When provided to `config ...`, `build`, `run`, `deploy`, `lint`,\n  and `test`, relative config paths, manifest paths, generated project locations, and workspace-scoped lint\u002Ftest resolution use\n  that directory as the workspace root. When omitted, the current working directory is used as the workspace root.\n- **[`-c, --config \u003CPATH>`]** Config file path. This is required for `config ...` and `deploy` commands because there is\n  no default. `build` and `run` no longer accept `--config`; they compose their generation inputs from `Gears.toml`\n  and forward the manifest-declared runtime config path through the `GEARS_CONFIG` environment variable.\n- **[`--manifest \u003CPATH>`]** Gears manifest path, defaulting to `Gears.toml`, for `manifest`, `build`, `run`,\n  `lint`, and `test`.\n  For `manifest`, you can combine this with `-p\u002F--path` to resolve relative manifest paths from a selected workspace.\n- **[`--app \u003CAPP> --env \u003CENV>`]** Selects a manifest app\u002Fenvironment for manifest-driven `build`, `run`, `lint`, and `test`.\n  When omitted, inferred from the manifest: a single app is used automatically; with multiple apps the command\n  fails listing available names. For environments, `dev` is selected by default if it exists; otherwise the\n  command fails listing available names.\n- **[`--name \u003CNAME>`]** For `build` and `run`, overrides the generated server project and binary name that would\n  otherwise default to the config filename stem.\n- **[`-v, --verbose`]** Usually enables more logging or richer output.\n- **[name validation]** Config-managed names for modules, DB servers, and generated server names only allow letters,\n  numbers, `-`, and `_`.\n\n## What the Tool Manages\n\nFrom the current implementation, the CLI is mainly for:\n\n- **[workspace scaffolding]** Initialize a Gears workspace and add module templates\n- **[config management]** Enable modules and patch YAML config sections\n- **[server generation]** Generate a runnable Cargo project under the manifest `workspace.generated-dir` directory\n  (default `.gears\u002F\u003Cname>\u002F`)\n- **[manifest orchestration]** Read `Gears.toml` to separate generation metadata from runtime YAML config\n- **[build\u002Frun\u002Fclean\u002Fdeploy]** Build, run, clean, or package that generated server as a Docker image\n- **[source inspection]** Resolve Rust source for crates\u002Fitems through workspace metadata or crates.io\n- **[module inspection]** List workspace-discovered and system-registry modules\n- **[tool bootstrap]** Install or upgrade `rustup`, `cargofmt`, and `clippy`\n\n## Top-Level Commands\n\n### `generate`\n\nGenerate workspace, module, and config scaffolding from built-in templates or explicit local\u002FGit template sources.\n\n#### `generate workspace`\n\nSynopsis:\n\n```bash\ncargo gears generate workspace [\u003Cpath>] [--template \u003CTEMPLATE>] [--list] [--verbose] [--name \u003CNAME>] [--local-path \u003CPATH>] [--git \u003CURL>] [--subfolder \u003CNAME>] [--branch \u003CNAME>] [--override]\n```\n\nArguments:\n\n- **[`\u003Cpath>`]** Target directory to initialize; not required with `--list`\n- **[`-t, --template \u003CTEMPLATE>`]** Workspace template name, defaults to `basic-init`; `default` is accepted as a compatibility alias\n- **[`-l, --list`]** List built-in workspace templates plus manifest `templates.workspace` entries when a `Gears.toml` exists at the selected path\n- **[`-v, --verbose`]** Verbose output from `cargo-generate`\n- **[`-n, --name \u003CNAME>`]** Override the generated project name; inferred from the final path segment by default\n- **[`--local-path \u003CPATH>`]** Use a local template directory instead of the default Git template\n- **[`--git \u003CURL>`]** Override the Git URL for the template\n- **[`--subfolder \u003CNAME>`]** Override the template subfolder\n- **[`--branch \u003CNAME>`]** Override the template branch\n- **[`--override`]** Allow generated files to overwrite existing files\n\nBehavior:\n\n- **[creates target directory]** If it does not exist\n- **[fails on file path]** Errors if `\u003Cpath>` already exists and is not a directory\n- **[uses directory name as project name]** The final path segment becomes the generated project name unless `--name` is\n  provided\n- **[uses template registry]** Template names resolve through the built-in registry and then manifest-defined templates\n- **[forces git init]** Template generation runs with Git initialization enabled\n- **[pins dylint lints]** Pins `cargo-gears-lints` to the CLI's release tag in the generated workspace's Dylint\n  metadata, as `lint --pin-dylint` does. If that fails (for example, the template has no workspace `Cargo.toml`), it\n  only warns\n\nExamples:\n\n```bash\ncargo gears generate workspace \u002Ftmp\u002Fcf-demo\n```\n\n```bash\ncargo gears generate workspace \u002Ftmp\u002Fcf-demo --git https:\u002F\u002Fgithub.com\u002Fconstructorfabric\u002Fcf-template-rust --branch main --subfolder Init\n```\n\n```bash\ncargo gears generate workspace \u002Ftmp\u002Fcf-demo --local-path ~\u002Fdev\u002Fcf-template-rust\n```\n\n```bash\ncargo gears generate workspace --list\n```\n\n#### `generate gear`\n\nGenerate a gear template inside an existing workspace's `gears\u002F` directory and wire Cargo workspace dependencies.\n\nSynopsis:\n\n```bash\ncargo gears generate gear [--template \u003CTEMPLATE>] [--list] [--name \u003CNAME>] [--path \u003CPATH>] [--verbose] [--local-path \u003CPATH>] [--git \u003CURL>] [--subfolder \u003CNAME>] [--branch \u003CNAME>]\n```\n\nAvailable built-in templates:\n\n- **[`background-worker`]** Background worker module template\n- **[`api-db-handler`]** API\u002Fdatabase handler module template\n- **[`api-gateway`]** API gateway module template. Unless the user instruct to implement its own api-gateway, prefer the system module cf-api-gateway\n\nArguments:\n\n- **[`-t, --template \u003CTEMPLATE>`]** Gear template name; not required with `--list`\n- **[`-l, --list`]** List built-in gear templates plus manifest `templates.gear` entries when a `Gears.toml` exists at the selected path\n- **[`-n, --name \u003CNAME>`]** Generated gear folder\u002Fcrate name; defaults to the template name. Prefer passing this when\n  the generated gear should use the user's chosen name.\n- **[`-p, --path \u003CPATH>`]** Workspace root, defaults to `.`\n- **[`-v, --verbose`]** Verbose template generation output\n- **[`--local-path \u003CPATH>`]** Use a local template directory instead of the default Git template\n- **[`--git \u003CURL>`]** Override the Git URL for the template\n- **[`--subfolder \u003CNAME>`]** Override the template subfolder\n- **[`--branch \u003CNAME>`]** Override the template branch\n\nBehavior:\n\n- **[requires `gears\u002F`]** Fails unless `\u003Cworkspace>\u002Fgears` already exists\n- **[creates `gears\u002F\u003Cname>`]** Uses `--name` when provided, otherwise the template name\n- **[prevents duplicate]** Fails if that gear directory already exists\n- **[updates workspace members]** Adds generated modules to `workspace.members`\n- **[promotes dependencies]** Moves new gear dependency source\u002Fversion metadata into `workspace.dependencies`\n- **[rewrites gear Cargo files]** Rewrites gear dependencies to `workspace = true`\n- **[inherits workspace lints]** Adds `lints.workspace = true` to generated modules if needed\n- **[includes SDK crate when present]** If the generated gear contains `sdk\u002F`, it is also added as a workspace member\n\nExamples:\n\n```bash\ncargo gears generate gear --template background-worker -p \u002Ftmp\u002Fcf-demo\n```\n\n```bash\ncargo gears generate gear --template background-worker --name jobs -p \u002Ftmp\u002Fcf-demo\n```\n\n```bash\ncargo gears generate gear --template rest-api -p \u002Ftmp\u002Fcf-demo\n```\n\n```bash\ncargo gears generate gear --list -p \u002Ftmp\u002Fcf-demo\n```\n\n#### `generate config`\n\nGenerate a runtime YAML config file from a built-in template.\n\nSynopsis:\n\n```bash\ncargo gears generate config --template \u003Cdev|prod|db> [--app \u003CAPP>] [--env \u003CENV>] [--name \u003CNAME>] [--path \u003CPATH>]\n```\n\nBuilt-in templates:\n\n- **[`dev`]** Development-friendly runtime config\n- **[`prod`]** Production-oriented runtime config\n- **[`db`]** Development config with a `database.servers.main` section\n\nArguments:\n\n- **[`-t, --template \u003CTEMPLATE>`]** Config template name\n- **[`--app \u003CAPP>`]** Application name used for output filename\n- **[`--env \u003CENV>`]** Environment name used for output filename\n- **[`--name \u003CNAME>`]** Custom output filename; `.yml` is appended when no YAML extension is provided\n- **[`-p, --path \u003CPATH>`]** Workspace root, defaults to `.`\n\nBehavior:\n\n- **[writes under `config\u002F`]** Output path is `\u003Cworkspace>\u002Fconfig\u002F\u003Cfilename>`\n- **[filename resolution]** `--name` wins; otherwise `\u003Capp>-\u003Cenv>.yml`, `\u003Capp>.yml`, `\u003Cenv>.yml`, or `\u003Ctemplate>.yml`\n- **[prevents overwrites]** Fails if the target config file already exists\n- **[runtime values only]** Generated config contains runtime settings, not dependency metadata\n\nExamples:\n\n```bash\ncargo gears generate config --template dev --app app1 --env dev -p \u002Ftmp\u002Fcf-demo\n```\n\n```bash\ncargo gears generate config --template db --name local-db -p \u002Ftmp\u002Fcf-demo\n```\n\n### `new`\n\nAlias for `generate workspace`.\n\nSynopsis:\n\n```bash\ncargo gears new \u003Cpath> [--template \u003CTEMPLATE>] [--verbose] [--name \u003CNAME>] [--local-path \u003CPATH>] [--git \u003CURL>] [--subfolder \u003CNAME>] [--branch \u003CNAME>] [--override]\n```\n\n### `config`\n\nManages the YAML application config file used by `build` and `run`.\n\nThere are two branches:\n\n- **[`config mod ...`]** Module configuration\n- **[`config db ...`]** Global database server configuration\n\n### `config mod`\n\nManage the `modules` section in the app config.\n\n#### `config mod add`\n\nAdd or update a module entry in the config file's `modules` section.\n\nSynopsis:\n\n```bash\ncargo gears config mod add -c \u003CCONFIG> [-p \u003CPATH>] [--package \u003CNAME>] [--module-version \u003CVER>] [--default-features \u003CBOOL>] [-F, --feature \u003CFEATURES>]... [--dep \u003CNAME>]... \u003Cmodule>\n```\n\nArguments:\n\n- **[`\u003Cmodule>`]** Module name in the config\n- **[`-c, --config \u003CCONFIG>`]** Required config file path\n- **[`-p, --path \u003CPATH>`]** Optional workspace directory\n- **[`--package \u003CNAME>`]** Override metadata package name\n- **[`--module-version \u003CVER>`]** Override metadata version\n- **[`--default-features \u003CBOOL>`]** Persist Cargo `default_features`\n- **[`-F, --feature \u003CFEATURES>`]** Feature list; accepts comma-separated values and can be repeated\n- **[`--dep \u003CNAME>`]** Metadata dependency name; repeat to add more\n\nBehavior:\n\n- **[upsert]** Creates or updates `modules.\u003Cmodule>`\n- **[path activation]** If `-p\u002F--path` is provided, Clap changes the current working directory while parsing that value,\n  before `-c\u002F--config` is resolved\n- **[local-first discovery]** Tries to discover module metadata from the workspace\n- **[remote module support]** If the module is not local, you must provide both `--package` and `--module-version`\n- **[portable metadata]** Local filesystem paths are intentionally not persisted into config metadata\n- **[merge semantics]** Existing metadata fields are preserved unless you explicitly override them\n- **[metadata requirements]** Package and version are required in the resulting metadata, whether sourced locally or\n  passed explicitly\n\nExamples:\n\n```bash\ncargo gears config mod add background-worker -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fquickstart.yml\n```\n\n```bash\ncargo gears config mod add api-gateway -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fquickstart.yml -F json,metrics -F tracing --dep authn-resolver --dep tenant-resolver\n```\n\n```bash\ncargo gears config mod add credstore -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fquickstart.yml --package cf-credstore --module-version 0.4.2\n```\n\n```bash\ncargo gears config mod add api-db-handler -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fquickstart.yml --default-features false\n```\n\n#### `config mod rm`\n\nRemove a module from the config file's `modules` section.\n\nSynopsis:\n\n```bash\ncargo gears config mod rm -c \u003CCONFIG> [-p \u003CPATH>] \u003Cmodule>\n```\n\nBehavior:\n\n- **[path activation]** If `-p\u002F--path` is provided, Clap changes the current working directory while parsing that value,\n  before `-c\u002F--config` is resolved\n- **[strict removal]** Fails if the module is not present in config\n\nExample:\n\n```bash\ncargo gears config mod rm background-worker -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fquickstart.yml\n```\n\n#### `config mod db`\n\nManage module-level database config under `modules.\u003Cmodule>.database`.\n\nSubcommands:\n\n- **[`add`]** Add or patch a module DB config\n- **[`edit`]** Edit an existing module DB config\n- **[`rm`]** Remove a module DB config\n\nShared DB flags:\n\n- **[`--engine \u003Cpostgres|mysql|sqlite>`]**\n- **[`--dsn \u003CDSN>`]**\n- **[`--host \u003CHOST>`]**\n- **[`--port \u003CPORT>`]**\n- **[`--user \u003CUSER>`]**\n- **[`--password \u003CPASSWORD>`]**\n- **[`--dbname \u003CNAME>`]**\n- **[`--params \u003CK=V,...>`]**\n- **[`--sqlite-file \u003CFILE>`]**\n- **[`--sqlite-path \u003CPATH>`]**\n- **[`--pool-max-conns \u003CN>`]**\n- **[`--pool-min-conns \u003CN>`]**\n- **[`--pool-acquire-timeout-secs \u003CSECS>`]**\n- **[`--pool-idle-timeout-secs \u003CSECS>`]**\n- **[`--pool-max-lifetime-secs \u003CSECS>`]**\n- **[`--pool-test-before-acquire \u003CBOOL>`]**\n- **[`--server \u003CNAME>`]** Reference a named global DB server\n\nRules:\n\n- **[path activation]** If `-p\u002F--path` is provided, each subcommand changes the current working directory while Clap is\n  parsing that value, before `-c\u002F--config` is resolved\n- **[payload required]** `add` and `edit` require at least one DB-related field\n- **[module must exist]** `add` requires the module already exist in config and recommends `config mod add` first\n- **[edit requires existing DB config]** `edit` fails if no module DB config exists yet\n- **[patch semantics]** `add` and `edit` patch only the fields you provide\n\nExamples:\n\n```bash\ncargo gears config mod db add background-worker -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fquickstart.yml --server primary\n```\n\n```bash\ncargo gears config mod db add api-db-handler -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fquickstart.yml --engine postgres --host localhost --port 5432 --user app --password '${DB_PASSWORD}' --dbname appdb --pool-max-conns 20\n```\n\n```bash\ncargo gears config mod db edit api-db-handler -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fquickstart.yml --pool-acquire-timeout-secs 30 --pool-test-before-acquire true\n```\n\n```bash\ncargo gears config mod db rm api-db-handler -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fquickstart.yml\n```\n\n### `config db`\n\nManage global database server config under `database.servers`.\n\nSubcommands:\n\n- **[`add`]** Add or upsert a named global DB server\n- **[`edit`]** Edit an existing global DB server\n- **[`rm`]** Remove an existing global DB server\n\nSynopsis:\n\n```bash\ncargo gears config db add  -c \u003CCONFIG> [-p \u003CPATH>] \u003Cname> \u003Cdb-flags...>\ncargo gears config db edit -c \u003CCONFIG> [-p \u003CPATH>] \u003Cname> \u003Cdb-flags...>\ncargo gears config db rm   -c \u003CCONFIG> [-p \u003CPATH>] \u003Cname>\n```\n\nBehavior:\n\n- **[path activation]** If `-p\u002F--path` is provided, each subcommand changes the current working directory while Clap is\n  parsing that value, before `-c\u002F--config` is resolved\n- **[server name]** Stored under `database.servers.\u003Cname>`\n- **[add is upsert]** `add` creates or patches an existing server entry\n- **[edit is strict]** `edit` requires the server to already exist\n- **[payload required]** `add` and `edit` require at least one DB-related field\n- **[cleanup]** `rm` removes the top-level `database` section if it becomes empty and `auto_provision` is unset\n\nExamples:\n\n```bash\ncargo gears config db add primary -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fquickstart.yml --engine postgres --host localhost --port 5432 --user app --password '${DB_PASSWORD}' --dbname appdb\n```\n\n```bash\ncargo gears config db edit primary -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fquickstart.yml --pool-max-conns 30 --pool-idle-timeout-secs 120\n```\n\n```bash\ncargo gears config db add local-sqlite -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fquickstart.yml --engine sqlite --sqlite-path \u002Ftmp\u002Fcf-demo\u002Fdev.db\n```\n\n```bash\ncargo gears config db rm primary -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fquickstart.yml\n```\n\n### `src`\n\nResolve Rust source for a crate\u002Fmodule\u002Fitem query from local workspace metadata, the local source cache, or crates.io.\n\nSynopsis:\n\n```bash\ncargo gears src [--path \u003CPATH>] [--registry \u003CREGISTRY>] [--verbose] [--libs] [--version \u003CVERSION>] [--clean] [\u003Cquery>]\n```\n\nArguments:\n\n- **[`-p, --path \u003CPATH>`]** Workspace or crate to inspect, defaults to `.`\n- **[`--registry \u003CREGISTRY>`]** Registry fallback, defaults to `crates.io`\n- **[`-v, --verbose`]** Print resolution metadata before the source\n- **[`-l, --libs`]** Print `library_name -> package_name` mappings for a package query instead of source\n- **[`--version \u003CVERSION>`]** Resolve a specific crate version after metadata\u002Fcache lookup misses\n- **[`--clean`]** Remove the source cache for the selected registry before resolving\n- **[`[\u003Cquery>]`]** Rust path to resolve, starting with the package name; omitted only when `--clean` is used by itself\n\nSupported query examples:\n\n- **[`cf-gears-toolkit`]**\n- **[`tokio::sync`]**\n- **[`cf-gears-toolkit::gts::plugin::BaseGearsPluginV1`]**\n- **[`cf-gears-toolkit::gts::schemas::get_core_gts_schemas`]**\n\nBehavior:\n\n- **[query requirement]** A query is required unless `--clean` is passed by itself\n- **[package-only libs mode]** `--libs` requires a package-only query such as `cf-gears-toolkit`\n- **[local resolution first]** Tries workspace metadata before hitting the network\n- **[cache-first registry fallback]** Reuses cached crate sources before downloading from the registry\n- **[crates.io fallback]** Downloads and extracts crate source if local resolution and cache lookup both fail\n- **[exact version fallback]** `--version` pins the registry\u002Fcache fallback to that exact crate version\n- **[recursive re-export resolution]** Follows re-exports across `crate`, `self`, `super`, and dependency boundaries\n  until it reaches the final source\n- **[library mapping output]** `--libs` prints the Rust source-code library name on the left and the Cargo package\n  name on the right, including renamed dependencies like `gears_toolkit_macros -> cf-gears-toolkit-macros`\n- **[cache location]** Registry sources are cached under the OS temp directory in `gears-docs-cache\u002F\u003Cregistry>\u002F` (legacy name)\n- **[cache cleaning]** `--clean` removes the selected registry cache before resolution\n- **[source output]** Prints the resolved Rust source to stdout\n- **[verbose metadata]** Also prints query, package, library, version, manifest path, and source path\n- **[registry support]** Only `crates.io` is supported today\n\nExamples:\n\n```bash\ncargo gears src -p \u002Ftmp\u002Fcf-demo cf-gears-toolkit\n```\n\n```bash\ncargo gears src cf-gears-toolkit::module\n```\n\n```bash\ncargo gears src --verbose tokio::sync\n```\n\n```bash\ncargo gears src --libs cf-gears-toolkit\n```\n\n```bash\ncargo gears src --version 1.0.217 serde::de::Deserialize\n```\n\n```bash\ncargo gears src --clean\n```\n\n```bash\ncargo gears src --clean -p \u002Ftmp\u002Fcf-demo tokio::sync\n```\n\n### `help`\n\nSchema, topic, and source-code help for developers and LLMs. Groups three subcommands under a\nsingle discoverable entry point.\n\n#### `help schema`\n\nPrint the schema for manifest, config, or module formats.\n\nSynopsis:\n\n```bash\ncargo gears help schema \u003Cmanifest|config|module> [--section \u003CSECTION>]\n```\n\nArguments:\n\n- **[`\u003Ctarget>`]** Schema target: `manifest`, `config`, or `module`\n- **[`--section \u003CSECTION>`]** Drill into a specific section of the schema\n\nBehavior:\n\n- **[overview mode]** Without `--section`, prints a top-level overview of the schema\n- **[section mode]** With `--section`, prints detailed field documentation for that section\n- **[manifest sections]** `workspace`, `apps`, `templates`\n- **[config sections]** `server`, `database`, `logging`, `opentelemetry`, `modules`\n- **[module sections]** None (only the overview is available)\n\nExamples:\n\n```bash\ncargo gears help schema manifest\n```\n\n```bash\ncargo gears help schema config --section database\n```\n\n```bash\ncargo gears help schema module\n```\n\n#### `help src`\n\nAlias for the top-level `src` command. Resolves Rust source code from a crate.\n\nSynopsis:\n\n```bash\ncargo gears help src [--path \u003CPATH>] [--registry \u003CREGISTRY>] [--verbose] [--libs] [--version \u003CVERSION>] [--clean] [\u003Cquery>]\n```\n\nBehavior identical to `src`; see the `src` section above.\n\n#### `help topic`\n\nPrint operational documentation for a named topic.\n\nSynopsis:\n\n```bash\ncargo gears help topic \u003CTOPIC>\n```\n\nAvailable topics:\n\n- **[`architecture`]** Framework architecture, three-tier hierarchy, and principles\n- **[`cli`]** CLI reference, guidelines, and command overview\n- **[`clienthub`]** Typed ClientHub, plugins, and GTS\n- **[`database`]** SecureConn, transactions, migrations, and repository pattern\n- **[`errors`]** RFC-9457 Problem error handling\n- **[`fips`]** FIPS mode activation and usage\n- **[`gear-layout`]** Gear directory structure and SDK pattern\n- **[`gear-refs`]** How local and remote gears are referenced\n- **[`gears-catalog`]** Gear categories and dependency rules\n- **[`generated-server`]** How the ephemeral generated server project works\n- **[`lifecycle`]** Gear lifecycle, cancellation, and background tasks\n- **[`manifest`]** Overview of `Gears.toml` and manifest-driven workflows\n- **[`otel`]** OpenTelemetry activation and runtime configuration\n- **[`rest-api`]** OperationBuilder, OpenAPI, SSE, and OData\n- **[`security`]** AuthN, AuthZ, SecureConn, and AccessScope\n\nExamples:\n\n```bash\ncargo gears help topic architecture\n```\n\n```bash\ncargo gears help topic gear-layout\n```\n\n```bash\ncargo gears help topic generated-server\n```\n\n```bash\ncargo gears help topic otel\n```\n\n### `tools`\n\nInstall or upgrade a small set of Rust tooling dependencies.\n\nKnown tool names:\n\n- **[`rustup`]**\n- **[`cargofmt`]** Installs the `rustfmt` rustup component\n- **[`clippy`]**\n\nSynopsis:\n\n```bash\ncargo gears tools (--all | --install \u003Ctool,...>) [--upgrade] [--yolo] [--verbose]\n```\n\nArguments:\n\n- **[`-a, --all`]** Select all known tools\n- **[`--install \u003Ctool,...>`]** Comma-separated tool names\n- **[`-u, --upgrade`]** Upgrade instead of initial install\n- **[`-y, --yolo`]** Skip confirmation prompts\n- **[`-v, --verbose`]** Show subprocess output\n\nBehavior:\n\n- **[selection required]** You must pass either `--all` or `--install`\n- **[interactive by default]** Without `--yolo`, the command prompts before installing\u002Fupgrading\n- **[rustup bootstrap]** If `rustup` is missing, the CLI can attempt to install it\n- **[component installs]** `cargofmt` and `clippy` are installed through `rustup component add`\n- **[upgrade mode]** Selected `rustup` upgrades via `rustup self update`; selected components upgrade via\n  `rustup update`\n\nExamples:\n\n```bash\ncargo gears tools --all\n```\n\n```bash\ncargo gears tools --install clippy,cargofmt --yolo\n```\n\n```bash\ncargo gears tools --install rustup,clippy --upgrade --verbose\n```\n\n#### `tools check-version`\n\nCheck that an external tool satisfies a semver version requirement by running `\u003Ctool> --version`,\nparsing the version from the output, and comparing it against the requirement. Exits 0 (printing\nthe version) if satisfied, or 1 if not.\n\nSynopsis:\n\n```bash\ncargo gears tools check-version \u003CTOOL> \u003CREQUIREMENT>\n```\n\nArguments:\n\n- **[`\u003CTOOL>`]** Tool binary name (e.g. `cargo-deny`, `cargo-nextest`)\n- **[`\u003CREQUIREMENT>`]** Semver requirement (e.g. `>=0.20.0`, `^0.9.130`)\n\nBehavior:\n\n- **[runs tool]** Invokes `\u003Ctool> --version` and parses the first semver token from stdout\n- **[exit code]** Exits 0 and prints the version if the requirement is satisfied; exits 1 with an error\n  message if not satisfied, if the tool is not installed, or if the version cannot be parsed\n\nExamples:\n\n```bash\ncargo gears tools check-version cargo-deny '>=0.20.0'\n```\n\n```bash\ncargo gears tools check-version cargo-nextest '^0.9.130'\n```\n\n### `run`\n\nGenerate a server project under the manifest `\u003Cworkspace.generated-dir>\u002F\u003Cname>` and run it.\n\nSynopsis:\n\n```bash\ncargo gears run [--app \u003CAPP>] [--env \u003CENV>] [--manifest \u003CGears.toml>] [-p \u003CPATH>] [--name \u003CNAME>] [--watch|--no-watch] [--otel|--no-otel] [--fips|--no-fips] [--release|--no-release] [--locked] [--clean|--no-clean] [--dry-run]\n```\n\nArguments:\n\n- **[`--manifest \u003CPATH>`]** Manifest file, defaults to `Gears.toml`\n- **[`--app \u003CAPP> --env \u003CENV>`]** Manifest app\u002Fenvironment selection (inferred from manifest if omitted)\n- **[`-p, --path \u003CPATH>`]** Optional workspace directory\n- **[`--name \u003CNAME>`]** Override the generated server project and binary name; defaults to the config filename stem\n- **[`-w, --watch` \u002F `--no-watch`]** Override manifest watch policy on or off\n- **[`--otel` \u002F `--no-otel`]** Override manifest OpenTelemetry policy on or off\n- **[`--fips` \u002F `--no-fips`]** Override manifest FIPS policy on or off\n- **[`-r, --release` \u002F `--no-release`]** Override manifest build profile to release or non-release\n- **[`--locked`]** Require `Cargo.lock` is up to date; passed as `--locked` to `cargo run`\n- **[`--clean` \u002F `--no-clean`]** Override manifest clean policy on or off\n- **[`--dry-run`]** Generate the project structure and print the generated files without building or running\n\nBehavior:\n\n- **[name resolution]** Uses the manifest build policy name when present, otherwise `\u003Capp>-\u003Cenv>`\n- **[path activation]** If `-p\u002F--path` is provided, Clap changes the current working directory while parsing that value,\n  before `Gears.toml` is resolved and the generated project directory is created\n- **[generates server structure]** Writes `\u003Cgenerated-dir>\u002F\u003Cname>\u002FCargo.toml`,\n  `\u003Cgenerated-dir>\u002F\u003Cname>\u002F.cargo\u002Fconfig.toml`, and `\u003Cgenerated-dir>\u002F\u003Cname>\u002Fsrc\u002Fmain.rs`; `generated-dir` comes from\n  manifest `workspace.generated-dir` and defaults to `.gears`\n- **[runtime config handoff]** The generated `src\u002Fmain.rs` reads the config path from `GEARS_CONFIG`, and\n  `cargo gears run` sets that environment variable automatically before invoking `cargo run`\n- **[dry run]** `--dry-run` writes the generated project structure under `\u003Cgenerated-dir>\u002F\u003Cname>\u002F` and prints JSON with the\n  generated project directory plus each generated file path and contents; it does not invoke Cargo build\u002Frun\n- **[manifest mode]** Reads generation dependencies, runtime config path, and policies from `Gears.toml`; runtime YAML\n  stays focused on server configuration\n- **[exclusive boolean overrides]** Boolean flag pairs are mutually exclusive. Use either the positive or negative form,\n  not both; for example, `--otel --no-otel` is rejected. When neither side is present, the manifest policy is used.\n- **[runs inside generated project]** Executes `cargo run` in `\u003Cgenerated-dir>\u002F\u003Cname>\u002F`\n- **[watch mode]** Restarts on runtime config changes and changes in watched local modules; regenerates and reruns when\n  workspace `Cargo.toml` or the selected `Gears.toml` changes\n- **[watch policy]** Manifest `run.watch.include` replaces the default watch set; `run.watch.exclude` removes matching\n  paths from either the default set or an explicit include set\n- **[manual generated-project execution]** If you invoke the generated project or compiled binary yourself instead of\n  using `cargo gears run`, you must set `GEARS_CONFIG` manually\n\nExamples:\n\n```bash\ncargo gears run -p \u002Ftmp\u002Fcf-demo --app app1 --env dev\n```\n\n```bash\ncargo gears run -p \u002Ftmp\u002Fcf-demo --app app1 --env dev --watch\n```\n\n```bash\ncargo gears run -p \u002Ftmp\u002Fcf-demo --app app1 --env dev --otel --fips --release --clean\n```\n\n```bash\ncargo gears run -p \u002Ftmp\u002Fcf-demo --app app1 --env dev --name demo-server\n```\n\n```bash\ncargo gears run -p \u002Ftmp\u002Fcf-demo --app app1 --env dev --dry-run\n```\n\n```bash\ncargo gears run -p \u002Ftmp\u002Fcf-demo --app app1 --env dev --manifest \u002Ftmp\u002Fcf-demo\u002FGears.toml\n```\n\n### `manifest`\n\nInspect and validate Gears manifest files.\n\nSynopsis:\n\n```bash\ncargo gears manifest [-p \u003CPATH>] [--manifest \u003CGears.toml>] validate [--format table|json]\ncargo gears manifest [-p \u003CPATH>] [--manifest \u003CGears.toml>] ls [--format table|json]\n```\n\nBehavior:\n\n- **[path activation]** If `-p\u002F--path` is provided, relative manifest paths are resolved from that workspace directory.\n- **[environment gears]** Manifest environments declare generation dependencies under the `gears` key.\n- **[validate]** Parses the manifest and resolves every app\u002Fenvironment entry.\n- **[ls]** Lists configured app\u002Fenvironment pairs with their resolved config paths and generated build names.\n- **[generated structure]** Use `build --dry-run` or `run --dry-run` to write and print the generated project structure.\n\n### `build`\n\nGenerate a server project under the manifest `\u003Cworkspace.generated-dir>\u002F\u003Cname>` and build it.\n\nSynopsis:\n\n```bash\ncargo gears build [--app \u003CAPP>] [--env \u003CENV>] [--manifest \u003CGears.toml>] [-p \u003CPATH>] [--name \u003CNAME>] [--otel|--no-otel] [--fips|--no-fips] [--release|--no-release] [--locked] [--clean|--no-clean] [--dry-run]\n```\n\nArguments:\n\n- **[`--manifest \u003CPATH>`]** Manifest file, defaults to `Gears.toml`\n- **[`--app \u003CAPP> --env \u003CENV>`]** Manifest app\u002Fenvironment selection (inferred from manifest if omitted)\n- **[`-p, --path \u003CPATH>`]** Optional workspace directory\n- **[`--name \u003CNAME>`]** Override the generated server project and binary name; defaults to the config filename stem\n- **[`--otel` \u002F `--no-otel`]** Override manifest OpenTelemetry policy on or off\n- **[`--fips` \u002F `--no-fips`]** Override manifest FIPS policy on or off\n- **[`-r, --release` \u002F `--no-release`]** Override manifest build profile to release or non-release\n- **[`--locked`]** Require `Cargo.lock` is up to date; passed as `--locked` to `cargo build`\n- **[`--clean` \u002F `--no-clean`]** Override manifest clean policy on or off\n- **[`--dry-run`]** Generate the project structure and print the generated files without building\n\nBehavior:\n\n- **[generates before build]** Recreates the generated server project before invoking Cargo\n- **[name resolution]** Uses the manifest build policy name when present, otherwise `\u003Capp>-\u003Cenv>`\n- **[path activation]** If `-p\u002F--path` is provided, Clap changes the current working directory while parsing that value,\n  before `Gears.toml` is resolved and the generated project directory is created\n- **[exclusive boolean overrides]** Boolean flag pairs are mutually exclusive. Use either the positive or negative form,\n  not both; for example, `--clean --no-clean` is rejected. When neither side is present, the manifest policy is used.\n- **[manifest mode]** Reads module dependency metadata, runtime config path, and build\u002Frun policy from `Gears.toml`\n  instead of runtime YAML module metadata\n- **[builds inside generated project]** Executes `cargo build` in `\u003Cgenerated-dir>\u002F\u003Cname>\u002F`\n- **[runtime config source]** The generated server no longer embeds the config path; the resulting binary reads it from\n  `GEARS_CONFIG` when you execute it\n- **[dry run]** `--dry-run` writes the generated project structure under `\u003Cgenerated-dir>\u002F\u003Cname>\u002F` and prints JSON with the\n  generated project directory plus each generated file path and contents; it does not invoke Cargo build\n- **[manual generated-project execution]** If you later run the generated project or binary outside the CLI, you must\n  set `GEARS_CONFIG` yourself\n\nExamples:\n\n```bash\ncargo gears build -p \u002Ftmp\u002Fcf-demo --app app1 --env dev\n```\n\n```bash\ncargo gears build -p \u002Ftmp\u002Fcf-demo --app app1 --env dev --release\n```\n\n```bash\ncargo gears build -p \u002Ftmp\u002Fcf-demo --app app1 --env dev --otel --fips --clean\n```\n\n```bash\ncargo gears build -p \u002Ftmp\u002Fcf-demo --app app1 --env dev --name demo-server\n```\n\n```bash\ncargo gears build -p \u002Ftmp\u002Fcf-demo --app app1 --env prod\n```\n\n```bash\ncargo gears build -p \u002Ftmp\u002Fcf-demo --app app1 --env prod --dry-run\n```\n\n### `clean`\n\nSuperset of `cargo clean`: removes build artifacts, the generated server project, and its workspace member entry\nfrom the root `Cargo.toml`.\n\nSynopsis:\n\n```bash\ncargo gears clean [--app \u003CAPP>] [--env \u003CENV>] [--manifest \u003CGears.toml>] [-p \u003CPATH>]\n```\n\nArguments:\n\n- **[`--manifest \u003CPATH>`]** Manifest file, defaults to `Gears.toml`\n- **[`--app \u003CAPP> --env \u003CENV>`]** Manifest app\u002Fenvironment selection (inferred from manifest if omitted)\n- **[`-p, --path \u003CPATH>`]** Optional workspace directory\n\nBehavior:\n\n- **[runs `cargo clean` first]** Removes build artifacts from the workspace `target\u002F` directory. If this fails due to\n  a broken workspace (e.g. missing generated member), the error is ignored and cleanup continues -- fixing such\n  broken state is the purpose of this command. Other `cargo clean` failures (permissions, disk errors, etc.) are\n  propagated as errors.\n- **[resolves target without dependencies]** Reads `Gears.toml` to determine the generated project directory and name\n  without resolving module dependencies or running `cargo metadata`\n- **[deletes generated project]** Removes `\u003Cgenerated-dir>\u002F\u003Cname>\u002F` (e.g. `.gears\u002Fproducts-dev\u002F`)\n- **[removes workspace member]** Removes the generated project entry from the `workspace.members` array in the root\n  `Cargo.toml`\n- **[cleans up empty generated dir]** If the generated directory (e.g. `.gears\u002F`) is empty after removal, it is also\n  deleted\n- **[runs `cargo clean` last]** After fixing the workspace, runs `cargo clean` to remove build artifacts from the\n  `target\u002F` directory. By running last, the workspace is guaranteed to be consistent so `cargo clean` succeeds\n  even when the generated member was previously missing or broken.\n- **[idempotent]** Running `clean` when the generated project does not exist is a no-op\n\nExamples:\n\n```bash\ncargo gears clean\n```\n\n```bash\ncargo gears clean --app app1 --env dev\n```\n\n```bash\ncargo gears clean -p \u002Ftmp\u002Fcf-demo\n```\n\n### `deploy`\n\nBuild a Docker image for the generated or provided server manifest.\n\nSynopsis:\n\n```bash\ncargo gears deploy [--app \u003CAPP>] [--env \u003CENV>] [--manifest \u003CGears.toml>] [-p \u003CPATH>] [-t \u003CTAG>] [-m \u003CCargo.toml>] [-c \u003CCONFIG>] [--debug] [--dockerfile \u003CPATH>] [--args \u003CKEY=VALUE>]...\n```\n\nArguments:\n\n- **[`-p, --path \u003CPATH>`]** Optional workspace directory used to resolve relative manifest paths\n- **[`--manifest \u003CPATH>`]** Gears manifest file, defaults to `Gears.toml`\n- **[`--app \u003CAPP> --env \u003CENV>`]** Manifest app\u002Fenvironment selection (inferred from manifest if omitted)\n- **[`-t, --tag \u003CTAG>`]** Tag for the Docker image; defaults to `gears:\u003Cversion>`\n- **[`-m, --manifest \u003CCargo.toml>`]** Optional Cargo manifest override; when omitted, uses the auto-resolved\n  generated project's `Cargo.toml` from the selected app\u002Fenv\n- **[`-c, --config \u003CCONFIG>`]** Optional config file override; when omitted, uses the config resolved from\n  the Gears.toml manifest\n- **[`--debug`]** Docker build mode; defaults to release mode. Use this flag to build in debug mode.\n- **[`--dockerfile \u003CPATH>`]** Dockerfile path to use instead of the default (Dockerfile from workspace root)\n- **[`--args \u003CKEY=VALUE>`]** Dockerfile `ARG` override passed as `docker build --build-arg`; repeat for multiple\n  overrides\n\nBehavior:\n\n- **[manifest selection]** Resolves the selected app\u002Fenvironment from `Gears.toml`, auto-selecting when there is\n  only one app\u002Fenv. The generated project's `Cargo.toml` and config path are derived automatically.\n- **[manifest override]** With `-m\u002F--manifest`, uses the provided Cargo.toml instead of the auto-resolved one;\n  its `package.name` is used as the artifact name\n- **[config override]** With `-c\u002F--config`, uses the provided config path instead of the manifest-resolved one\n- **[Dockerfile bootstrap]** If `Dockerfile` is missing from the selected workspace root, writes the shared CLI\n  Dockerfile there before running Docker\n- **[build context requirement]** The config file and selected manifest must be inside the workspace root because Docker\n  can only copy files from the build context\n- **[Docker args]** The CLI provides `BUILDER_MANIFEST`, `BUILD_MODE`, `ARTIFACT_NAME`, `LOCAL_CONFIG_PATH`, and\n  `CONFIG_EXT`; repeated `--args` values are appended afterward so they can override Dockerfile arguments\n\nExamples:\n\n```bash\n# Deploy using Gears.toml auto-selection (single app\u002Fenv)\ncargo gears deploy -p \u002Ftmp\u002Fcf-demo\n```\n\n```bash\n# Deploy a specific app\u002Fenv\ncargo gears deploy --app myapp --env dev -t my-app:latest\n```\n\n```bash\n# Deploy in debug mode\ncargo gears deploy --app myapp --env dev --debug\n```\n\n```bash\n# Deploy with an explicit Cargo manifest override\ncargo gears deploy --app myapp --env dev -m .gears\u002Fcustom-server\u002FCargo.toml\n```\n\n```bash\n# Deploy with extra Docker build args\ncargo gears deploy --app myapp --env dev --args BUILDER_FLAGS=\"--features metrics\"\n```\n\n### `lint`\n\nRun workspace linting helpers from the selected workspace directory.\n\nSynopsis:\n\n```bash\ncargo gears lint [--app \u003CAPP>] [--env \u003CENV>] [--manifest \u003CGears.toml>] [-p \u003CPATH>] [--all] [--fmt] [--clippy] [--strict] [--dylint] [-P \u003CSPEC>]... [--gear \u003CNAME>]... [--include-dependents] [-F \u003CFEATURES>]... [--all-features | --no-default-features] [--locked] [--list] [--pin-dylint]\n```\n\nArguments:\n\n- **[`-p, --path \u003CPATH>`]** Optional workspace directory used to resolve relative manifest paths\n- **[`--manifest \u003CPATH>`]** Manifest file, defaults to `Gears.toml`\n- **[`--app \u003CAPP> --env \u003CENV>`]** Manifest app\u002Fenvironment selection (inferred from manifest if omitted)\n- **[`--all`]** Runs all available lint suites instead of the selected manifest lint policy\n- **[`--fmt`]** Runs `cargo fmt --check` for the selected package scope; with no `-P\u002F--package` or `--gear`, it uses\n  `--all`. If passed by itself, it runs only formatting checks.\n- **[`--clippy`]** Runs workspace Clippy checks; if passed by itself, it runs only Clippy\n- **[`--strict`]** Turns Clippy warnings into errors; valid only when Clippy is selected explicitly or through `--all`\n- **[`--dylint`]** Runs `cargo dylint --all` against the workspace rooted at the current or selected directory, which\n  loads every library declared in `workspace.metadata.dylint.libraries`. Fails unless `cargo-gears-lints` is declared\n  there and pinned to the CLI's own release tag (see `--pin-dylint`)\n- **[`-P, --package \u003CSPEC>`]** Restricts formatting, Clippy, and Dylint to the given workspace package(s); repeatable.\n  Supports Cargo package ID specifications and package-name globs such as `cf-gears-*`. When omitted together with\n  `--gear`, the whole workspace is linted.\n- **[`--gear \u003CNAME>`]** Restricts formatting, Clippy, and Dylint to the local workspace package(s) belonging to a\n  discovered gear; repeatable. Includes the conventional nested gear SDK package. Use `cargo gears ls gears --local` to\n  list valid names. Can be combined with `-P\u002F--package`.\n- **[`--include-dependents`]** Expands the `-P\u002F--package` and `--gear` selection to also include every workspace crate\n  that (transitively) depends on the selected package(s) — the reverse-dependency closure. Requires at least one package\n  or gear selection; otherwise the command fails.\n- **[`-F, --features \u003CFEATURES>`]** Enables Cargo features for Clippy and Dylint. Accepts comma-separated values and is\n  repeatable. Default features remain enabled unless `--no-default-features` is also passed.\n- **[`--all-features`]** Enables every Cargo feature. Conflicts with `--features` and `--no-default-features`.\n- **[`--no-default-features`]** Disables Cargo default features. May be combined with `--features`.\n- **[`--locked`]** Requires `Cargo.lock` to be up to date; passed to Clippy and Dylint's `cargo check`.\n- **[`--list`]** Lists available lint rules instead of running them. When combined with `--dylint`, lists only the\n  dylint rules. Does not require a manifest or workspace path.\n- **[`--pin-dylint`]** Writes or updates the `cargo-gears-lints` entry in `workspace.metadata.dylint.libraries` so it is\n  pinned to the CLI's own release tag, then exits without running lints. Edits `dylint.toml` when it declares at least\n  one library, otherwise the workspace `Cargo.toml`; an empty `libraries = []` does not count. Fails without editing\n  when both files declare libraries, which Dylint rejects. Other libraries and keys are kept. Conflicts with `--all`, `--fmt`,\n  `--clippy`, `--strict`, `--dylint`, and `--list`.\n\nBehavior:\n\n- **[path activation]** If `-p\u002F--path` is provided, relative manifest paths are resolved from that workspace directory\n- **[manifest mode]** Reads lint policy from the selected `Gears.toml` app\u002Fenvironment and runs from the resolved\n  manifest workspace root\n- **[default lint selection]** With no explicit lint-selection flags, `lint` runs the selected manifest lint policy\n- **[explicit selection disables default all]** Passing `--fmt`, `--clippy`, and\u002For `--dylint` opts into just those\n  requested lint suites unless `--all` is also provided\n- **[package-scoped formatting]** `--fmt` runs `cargo fmt --check --all` when no package or gear is selected. With an\n  explicit package\u002Fgear scope, it passes each effective package as `--package \u003CSPEC>`. `--include-dependents` expands\n  this scope before formatting, matching Clippy and Dylint.\n- **[workspace Clippy]** Clippy runs as `cargo clippy --workspace --all-targets`, or as\n  `cargo clippy --package \u003CSPEC> ... --all-targets` when one or more `-P\u002F--package` flags are supplied. Cargo feature\n  flags are appended when selected. Without feature flags, each package's default features are used. Manifest\n  `feature-set-test` remains reserved for future feature-matrix linting and is not currently applied.\n- **[strict scope]** `--strict` is rejected unless Clippy is active through `--clippy` or `--all`\n- **[workspace-scoped dylint]** `cargo dylint` runs from the resolved workspace root with\n  `--manifest-path \u003Croot>\u002FCargo.toml`, so `-p\u002F--path` is the way to lint another workspace without manually changing\n  directories, and a workspace whose metadata cannot be loaded fails the run instead of linting nothing. It runs with\n  `--workspace`, or with `--package \u003CSPEC>` for\n  each effective package when a package\u002Fgear scope is selected; features, skips, and `--locked` are forwarded to its\n  `cargo check`.\n- **[pinned dylint lints]** Before running Dylint, the CLI checks the workspace's Dylint libraries (in `dylint.toml`\n  when it declares at least one, otherwise in the workspace `Cargo.toml`; declaring libraries in both is an error) for exactly one `cargo-gears-lints` entry. A git entry\n  must point at `https:\u002F\u002Fgithub.com\u002Fconstructorfabric\u002Fcargo-gears` with `tag = \"cargo-gears-v\u003CCLI version>\"`,\n  `pattern = \"crates\u002Fcargo-gears-lints\"`, and no `branch` or `rev`. A `path` entry to a local `cargo-gears-lints`\n  checkout is accepted with a warning, for developing the lints. A missing, duplicated, or differently pinned entry\n  fails the run and points at `--pin-dylint`.\n- **[external dylint lints]** Any other library in `workspace.metadata.dylint.libraries` runs together with\n  `cargo-gears-lints`, so third-party or in-house Dylint lints need only a standard Dylint entry\n- **[package-scoped linting]** Passing one or more `-P\u002F--package \u003CSPEC>` flags restricts formatting, Clippy, and Dylint\n  to those packages instead of the whole workspace; the flag is repeatable and supports Cargo package ID specifications\n  plus package-name globs. A bare `*` intentionally selects every workspace package while remaining an explicit scope.\n- **[gear-scoped linting]** Each `--gear \u003CNAME>` is resolved through local workspace gear discovery to its annotated\n  package and conventional nested SDK workspace package, when present. Gear-derived packages are merged and\n  de-duplicated with explicit `-P\u002F--package` selections. System registry gears that are not local workspace members\n  cannot be selected.\n- **[dependent expansion]** With `--include-dependents`, the selected packages are expanded to their reverse-dependency\n  closure (the seed packages plus every workspace crate that depends on them) before formatting, Clippy, and Dylint run,\n  so a change to a crate can be linted together with everything it may break. Unknown package names are rejected.\n- **[feature-scoped linting]** `--features`, `--all-features`, and `--no-default-features` use Cargo's standard feature\n  semantics and apply to both Clippy and Dylint. Package-qualified features such as `crate-name\u002Ffeature-name` can be used\n  when linting multiple workspace packages.\n- **[manifest dylint skips]** Manifest `lint.dylint.skip` entries are passed to Dylint as allowed rustc lints, so\n  listed rules are ignored for that lint run. They apply to external libraries' lints as well. They are passed both\n  as `build.rustflags` and appended to `DYLINT_RUSTFLAGS`, so they still hold when `RUSTFLAGS` is set, even to\n  `-D warnings`.\n- **[tool bootstrap]** Before running Dylint, the CLI installs `cargo-dylint` and `dylint-link` with\n  `cargo install --locked` if either is missing. Dylint itself fetches and builds the declared libraries on the first\n  run, with each library's pinned toolchain, so it needs access to GitHub.\n- **[list mode]** `--list` prints available lints grouped by category and exits without running any checks.\n  `--list --dylint` prints only the `cargo-gears-lints` rules. `--list` alone prints all lint suites plus those rules.\n  Lints from other Dylint libraries are not listed.\n\nExamples:\n\n```bash\ncargo gears lint --app app1 --env dev\n```\n\n```bash\ncargo gears lint --app app1 --env dev --clippy --strict\n```\n\n```bash\ncargo gears lint --app app1 --env dev --fmt\n```\n\n```bash\ncargo gears lint --app app1 --env dev --fmt --gear file-parser\n```\n\n```bash\ncargo gears lint --app app1 --env dev --dylint\n```\n\n```bash\ncargo gears lint -p \u002Ftmp\u002Fcf-demo --app app1 --env dev --dylint\n```\n\n```bash\ncargo gears lint --app app1 --env dev --clippy --package cf-gears-file-parser\n```\n\n```bash\ncargo gears lint --app app1 --env dev --dylint -P cf-gears-file-parser -P cf-gears-file-parser-sdk\n```\n\n```bash\ncargo gears lint --app app1 --env dev --dylint --gear file-parser\n```\n\n```bash\ncargo gears lint --app app1 --env dev --clippy --gear file-parser --include-dependents\n```\n\n```bash\ncargo gears lint --app app1 --env dev --clippy -P shared-utils --gear file-parser\n```\n\n```bash\ncargo gears lint --app app1 --env dev --clippy -P cf-gears-file-parser --include-dependents\n```\n\n```bash\ncargo gears lint --app app1 --env dev --clippy -P cf-gears-file-parser --features json,otel\n```\n\n```bash\ncargo gears lint --app app1 --env dev --dylint -P cf-gears-file-parser --no-default-features -F sqlite\n```\n\n```bash\ncargo gears lint --app app1 --env dev --clippy -P cf-gears-file-parser --all-features\n```\n\n```bash\ncargo gears lint --list --dylint\n```\n\n```bash\ncargo gears lint --app app1 --env dev --pin-dylint\n```\n\n```bash\ncargo gears lint --list\n```\n\nWorkspace `Cargo.toml` pin written by `--pin-dylint`, next to an external library:\n\n```toml\n[workspace.metadata.dylint]\nlibraries = [\n    { git = \"https:\u002F\u002Fgithub.com\u002Fconstructorfabric\u002Fcargo-gears\", tag = \"cargo-gears-v\u003CCLI version>\", pattern = \"crates\u002Fcargo-gears-lints\" },\n    { git = \"https:\u002F\u002Fgithub.com\u002Fexample\u002Fmy-lints\", tag = \"v1.0.0\" },\n]\n```\n\nManifest Dylint skip example:\n\n```toml\n[apps.app1.dev.lint]\ndylint = { enabled = true, skip = [\"de0301_no_infra_in_domain\"] }\n```\n\n### `ls`\n\nInspect workspace gears, system gears, templates, features, dependencies, and packages.\n\n#### `ls gears`\n\nList all gears — both system-registry and workspace-discovered — in a single unified view.\n\nSynopsis:\n\n```bash\ncargo gears ls gears [-p \u003CPATH>] [--system] [--local] [--verbose] [--registry crates.io] [--format table|json|list|cargo-flags] [--filter \u003CREGEX>] [--dirs \u003CDIR,...>] [--include-rdeps]\n```\n\nArguments:\n\n- **[`-p, --path \u003CPATH>`]** Optional workspace directory used for local gear discovery\n- **[`--system`]** Only print built-in system registry gears\n- **[`--local`]** Only print workspace-discovered gears\n- **[`-v, --verbose`]** Show full metadata for both system and local gears (fetches registry metadata for system\n  gears)\n- **[`--registry \u003CREGISTRY>`]** Registry to query for system-crate metadata; defaults to `crates.io`\n- **[`-f, --format \u003CFORMAT>`]** Output format; defaults to `json`. Supported values: `table`, `json`, `list`,\n  `cargo-flags`\n- **[`--filter \u003CREGEX>`]** Filter gear names by regex pattern. Applied before `--include-rdeps`\n- **[`--dirs \u003CDIR,...>`]** Comma-separated directory paths (relative to workspace root) to restrict results\n  to gears whose crate directory is under one of the given directories. Applied before `--include-rdeps`\n- **[`--include-rdeps`]** After filtering\u002Fscoping, expand the result set with every workspace crate that\n  transitively depends on the matched gears (reverse-dependency closure)\n\nBehavior:\n\n- **[combined output]** Prints system gears first, then workspace gears, separated by a blank line\n- **[filtered output]** `--system` prints only system gears; `--local` prints only workspace gears; passing both is\n  equivalent to the default combined output\n- **[json output]** `--format json` prints a `modules` array with each gear's `source` (`system` or `local`), static\n  metadata, and verbose metadata when `--verbose` is enabled\n- **[system usage marker]** System gears include `used: yes\u002Fno` in table output and `used: true\u002Ffalse` in JSON output,\n  based on whether `Gears.toml` references the system gear as a remote module or the workspace has a discovered gear\n  with the same name\n- **[config-independent]** Does not require a `-c\u002F--config` file\n- **[workspace scanning]** Local output runs `cargo metadata --no-deps` and discovers crates with a gears annotation\n  (`#[toolkit::gear(...)]`) in any `src\u002F**\u002F*.rs` file\n- **[system registry]** System output uses the compiled-in registry, and `--verbose` fetches crate metadata from the\n  selected registry\n- **[cargo-flags format]** `--format cargo-flags` prints `-p \u003Cpackage>` flags suitable for passing to Cargo commands\n- **[filter → scope → rdeps pipeline]** Filters and scope directories are applied first to narrow the initial gear\n  set; `--include-rdeps` then expands that set with reverse dependents\n\nExamples:\n\n```bash\ncargo gears ls gears\n```\n\n```bash\ncargo gears ls gears -p \u002Ftmp\u002Fcf-demo --verbose\n```\n\n```bash\ncargo gears ls gears --local\n```\n\n```bash\ncargo gears ls gears --system --verbose\n```\n\n```bash\ncargo gears ls gears --local --filter 'api-.*' --include-rdeps\n```\n\n```bash\ncargo gears ls gears --local --dirs gears\u002Fapi -f cargo-flags\n```\n\n#### `ls templates`\n\nList all available generation templates.\n\nSynopsis:\n\n```bash\ncargo gears ls templates [-p \u003CPATH>]\n```\n\nArguments:\n\n- **[`-p, --path \u003CPATH>`]** Optional workspace directory used to find `Gears.toml`; defaults to `.`\n\nBehavior:\n\n- **[built-in templates]** Always prints built-in workspace and gear templates with their names and descriptions\n- **[manifest templates]** Also prints manifest `templates.workspace` and `templates.gear` entries when `Gears.toml`\n  exists at the selected path\n- **[config-independent]** Does not require a `-c\u002F--config` file\n\nExamples:\n\n```bash\ncargo gears ls templates\n```\n\n```bash\ncargo gears ls templates -p \u002Ftmp\u002Fcf-demo\n```\n\n#### `ls features`\n\nList all feature names defined in a Cargo.toml's `[features]` section.\n\nSynopsis:\n\n```bash\ncargo gears ls features --manifest \u003CPATH> [-f \u003CFORMAT>]\n```\n\nArguments:\n\n- **[`--manifest \u003CPATH>`]** Path to the Cargo.toml to inspect\n- **[`-f, --format \u003CFORMAT>`]** Output format; defaults to `list`. Supported values: `list`, `table`, `json`,\n  `cargo-flags`\n\nBehavior:\n\n- **[sorted output]** Features are listed in lexicographic order\n- **[cargo-flags format]** `--format cargo-flags` prints features as a comma-separated list suitable for\n  `--features \u003CLIST>`\n\nExamples:\n\n```bash\ncargo gears ls features --manifest gears\u002Fapi-gateway\u002FCargo.toml\n```\n\n```bash\ncargo gears ls features --manifest Cargo.toml -f json\n```\n\n#### `ls deps`\n\nList dependency names from a Cargo.toml's `[dependencies]` section.\n\nSynopsis:\n\n```bash\ncargo gears ls deps --manifest \u003CPATH> [--non-optional] [-f \u003CFORMAT>]\n```\n\nArguments:\n\n- **[`--manifest \u003CPATH>`]** Path to the Cargo.toml to inspect\n- **[`--non-optional`]** Only list non-optional (always-linked) dependencies\n- **[`-f, --format \u003CFORMAT>`]** Output format; defaults to `list`. Supported values: `list`, `table`, `json`,\n  `cargo-flags`\n\nBehavior:\n\n- **[sorted output]** Dependencies are listed in lexicographic order\n- **[package field]** Uses the `package` field from the dependency table when present, otherwise uses the key name\n- **[cargo-flags format]** `--format cargo-flags` prints `-p \u003Cpackage>` flags\n\nExamples:\n\n```bash\ncargo gears ls deps --manifest gears\u002Fapi-gateway\u002FCargo.toml\n```\n\n```bash\ncargo gears ls deps --manifest Cargo.toml --non-optional -f json\n```\n\n#### `ls packages`\n\nList all Cargo packages (crates) in the workspace or under specific directories, with optional\nfiltering and reverse-dependency expansion.\n\nSynopsis:\n\n```bash\ncargo gears ls packages [-p \u003CPATH>] [--dirs \u003CDIR,...>] [--filter \u003CREGEX>] [--include-rdeps] [-f \u003CFORMAT>]\n```\n\nArguments:\n\n- **[`-p, --path \u003CPATH>`]** Optional workspace directory\n- **[`--dirs \u003CDIR,...>`]** Comma-separated directory paths to restrict discovery to crates under those directories\n  (relative to workspace root)\n- **[`--filter \u003CREGEX>`]** Filter package names by regex pattern. Applied before `--include-rdeps`\n- **[`--include-rdeps`]** After filtering\u002Fscoping, expand the result set with every workspace crate that transitively\n  depends on the matched packages (reverse-dependency closure)\n- **[`-f, --format \u003CFORMAT>`]** Output format; defaults to `list`. Supported values: `list`, `table`, `json`,\n  `cargo-flags`\n\nBehavior:\n\n- **[all packages by default]** Without `--dirs`, lists all workspace packages\n- **[dirs discovery]** With `--dirs`, only packages whose manifest path is inside one of the given directories\n  are included\n- **[scope → filter → rdeps pipeline]** Scoping is applied first, then filters, then `--include-rdeps` expands\n  the filtered set\n- **[cargo-flags format]** `--format cargo-flags` prints `-p \u003Cpackage>` flags\n\nExamples:\n\n```bash\ncargo gears ls packages -p \u002Ftmp\u002Fcf-demo\n```\n\n```bash\ncargo gears ls packages -p \u002Ftmp\u002Fcf-demo --dirs gears\u002Fapi\n```\n\n```bash\ncargo gears ls packages --filter 'cf-gears-.*' --include-rdeps\n```\n\n```bash\ncargo gears ls packages --filter 'api' --include-rdeps -f cargo-flags\n```\n\n### `test`\n\nOrchestrates manifest-driven Rust tests with either `cargo test` or the in-process nextest runner.\n\nSynopsis:\n\n```bash\ncargo gears test [-p \u003CPATH>] [--manifest \u003CPATH>] [--app \u003CAPP>] [--env \u003CENV>] [--runner \u003Ccargo|nextest>] [--module \u003CNAME>] [--include-dependents] [--coverage] [--locked]\n```\n\nArguments:\n\n- **[`--runner \u003Ccargo|nextest>`]** Overrides the manifest `test.runner`; defaults to `nextest` that it's integrated in the tool\n- **[`--module \u003CNAME>`]** Limits tests to a module\u002Fpackage. When manifest `test.feature-set` contains that module, its feature matrix is used.\n- **[`--include-dependents`]** Also tests every workspace crate that (transitively) depends on `--module` — the reverse-dependency closure. Requires `--module`; has no effect on its own.\n- **[`--coverage`]** Runs coverage with `cargo llvm-cov` using the selected or manifest test runner\n- **[`--locked`]** Require `Cargo.lock` is up to date; passed as `--locked` to `cargo test`, nextest build, and `cargo llvm-cov`\n\nBehavior:\n\n- **[manifest selection]** Resolves the selected app\u002Fenvironment and passes its config path to tests via `GEARS_CONFIG`\n- **[cargo runner]** Runs `cargo test` with `--workspace` by default, or `-p \u003Cpackage>` for module-specific runs\n- **[nextest runner]** Builds test binaries with Cargo JSON messages, then executes them through the embedded nextest runner from `cargo-nextest`\n- **[coverage runner]** Cleans llvm-cov artifacts once, executes every selected module\u002Ffeature-set run, then generates one aggregate report across all collected profiles\n- **[cargo coverage]** With `cargo`, runs each selected module\u002Ffeature-set through `cargo llvm-cov --no-report --no-clean`, then reports once with `cargo llvm-cov report`\n- **[nextest coverage]** With `nextest`, uses `cargo llvm-cov show-env`, runs the embedded nextest runner under the coverage environment for every selected module\u002Ffeature-set, then reports once with `cargo llvm-cov report`\n- **[feature-set policy]** Expands manifest `test.feature-set` module entries by `mode`: `all-features` uses `--all-features`, `no-default-features` uses `--no-default-features`, `default-features` uses Cargo defaults, and `features` uses `--no-default-features --features \u003CLIST>`\n- **[dependent expansion]** With `--module \u003CNAME> --include-dependents`, the resolved package is expanded to its reverse-dependency closure and each additional dependent crate is added as a default-feature test run (de-duplicated against runs already produced by the feature-set policy)\n\n## Practical End-to-End Flows\n\n### Create a workspace and run it\n\n```bash\ncargo gears {new|generate workspace} \u002Ftmp\u002Fcf-demo\ncargo gears generate module --template background-worker -p \u002Ftmp\u002Fcf-demo\ncargo gears generate config --template dev --app app1 --env dev -p \u002Ftmp\u002Fcf-demo\ncargo gears config mod add background-worker -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fapp1-dev.yml\ncargo gears run -p \u002Ftmp\u002Fcf-demo --app app1 --env dev\n```\n\n### Add a module and wire a shared DB server\n\n```bash\ncargo gears generate module --template api-db-handler -p \u002Ftmp\u002Fcf-demo\ncargo gears config db add primary -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fquickstart.yml --engine postgres --host localhost --port 5432 --user app --password '${DB_PASSWORD}' --dbname appdb\ncargo gears config mod add api-db-handler -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fquickstart.yml\ncargo gears config mod db add api-db-handler -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fquickstart.yml --server primary\ncargo gears run -p \u002Ftmp\u002Fcf-demo --app app1 --env dev --watch\n```\n\n### Inspect source for a dependency\n\n```bash\ncargo gears src --verbose tokio::sync\n```\n\n## Important Caveats\n\n- **[`-c\u002F--config` is mandatory]** For `config ...` and `deploy`; `build` and `run` use `Gears.toml` instead\n- **[generated servers expect `GEARS_CONFIG`]** `cargo gears run` sets it for you, but manual execution of\n  generated project directory or its compiled binary must provide it explicitly\n- **[`lint --dylint` needs the lints pinned]** Run `cargo gears lint --pin-dylint` after creating a workspace by\n  other means than `generate workspace`, and after every CLI upgrade\n- **[`lint --strict` depends on Clippy]** Use it together with `--clippy` or `--all`\n- **[`test` is not ready]** It is part of the CLI surface but currently panics at runtime\n- **[`tools` can mutate your system]** It may install `rustup` or rustup components\n- **[`src --registry`]** Only `crates.io` is supported\n- **[`src`]** Accepts a single query, and that query is only optional when `--clean` is used by itself\n- **[`config mod add`]** Remote modules require both `--package` and `--module-version`\n- **[`config mod db add`]** The module must already exist in config\n\n## Quick Reference\n\n```bash\ncargo gears {new|generate workspace} \u003Cpath> [--template \u003Ctemplate>] [--name \u003Cname>]\ncargo gears generate module --template \u003Cbackground-worker|api-db-handler|api-gateway> [--name \u003Cname>] [-p \u003Cworkspace>]\ncargo gears generate config --template \u003Cdev|prod|db> [--app \u003Capp>] [--env \u003Cenv>] [--name \u003Cname>] [-p \u003Cworkspace>]\n\ncargo gears config mod add \u003Cmodule> [-p \u003Cworkspace>] -c \u003Cconfig>\ncargo gears config mod rm \u003Cmodule> [-p \u003Cworkspace>] -c \u003Cconfig>\ncargo gears config mod db add \u003Cmodule> [-p \u003Cworkspace>] -c \u003Cconfig> ...\ncargo gears config mod db edit \u003Cmodule> [-p \u003Cworkspace>] -c \u003Cconfig> ...\ncargo gears config mod db rm \u003Cmodule> [-p \u003Cworkspace>] -c \u003Cconfig>\n\ncargo gears config db add \u003Cname> [-p \u003Cworkspace>] -c \u003Cconfig> ...\ncargo gears config db edit \u003Cname> [-p \u003Cworkspace>] -c \u003Cconfig> ...\ncargo gears config db rm \u003Cname> [-p \u003Cworkspace>] -c \u003Cconfig>\n\n\ncargo gears ls gears [-p \u003Cworkspace>] [--system] [--local] [--verbose] [--registry crates.io] [-f table|json|list|cargo-flags] [--filter \u003Cregex>] [--dirs \u003Cdirs>] [--include-rdeps]\ncargo gears ls templates [-p \u003Cworkspace>]\ncargo gears ls features --manifest \u003CCargo.toml> [-f list|json|cargo-flags]\ncargo gears ls deps --manifest \u003CCargo.toml> [--non-optional] [--dev] [--build] [-f list|json|cargo-flags]\ncargo gears ls packages [-p \u003Cworkspace>] [--dirs \u003Cdirs>] [--filter \u003Cregex>] [--include-rdeps] [-f list|json|cargo-flags]\ncargo gears ls targets --manifest \u003CCargo.toml> [-f list|json|cargo-flags]\n\ncargo gears src [-p \u003Cpath>] [--version \u003Cversion>] [--clean] [\u003Cquery>]\ncargo gears lint [-p \u003Cworkspace>] [--app \u003Capp>] [--env \u003Cenv>] [--manifest \u003CGears.toml>] [--all] [--fmt] [--clippy] [--strict] [--dylint] [-P \u003Cspec>]... [--gear \u003Cname>]... [--include-dependents] [-F \u003Cfeatures>]... [--all-features | --no-default-features] [--locked] [--list] [--pin-dylint]\ncargo gears tools --all\ncargo gears tools check-version \u003Ctool> '\u003Crequirement>'\ncargo gears run [-p \u003Cworkspace>] [--app \u003Capp>] [--env \u003Cenv>] [--manifest \u003CGears.toml>] [--name \u003Cname>] [--watch] [--locked]\ncargo gears build [-p \u003Cworkspace>] [--app \u003Capp>] [--env \u003Cenv>] [--manifest \u003CGears.toml>] [--name \u003Cname>] [--locked]\ncargo gears deploy [--app \u003Capp>] [--env \u003Cenv>] [-p \u003Cworkspace>] [-t \u003Ctag>] [-m \u003CCargo.toml>] [-c \u003Cconfig>] [--debug] [--args \u003CKEY=VALUE>]...\n```\n","# General Guidelines to follow\n\n- When adding new dependencies use `cargo add`, do not edit Cargo.toml manually\n- When linting, use lint command of the cli to check if there are any lint errors.\n  Do not try to run cargo check, clippy or fmt by your own.\n- Always verify that the application runs successfully after modifying the code.\n- Unless the user specifically mentions to use a custom module, prefer to use system gears\n  instead of implementing your own ones. Pay attention to the \"deps\" section of the gears, as the module will be\n  required to be added in order to be used.\n- Do not try to create a module from scratch, always use the generate module command to create a new module.\n\n## Invocation Forms\n\nThe crate exposes a single entrypoint:\n\n- **[`cargo gears`]** Cargo subcommand form via the `cargo-gears` binary\n\nExample:\n\n```bash\ncargo gears generate workspace \u002Ftmp\u002Fmy-app\n```\n\n## Objective\n\nThis CLI is a tool for automating gears development, a Rust framework. You can get more information about it in:\n\n- Gears repository main: https:\u002F\u002Fgithub.com\u002Fconstructorfabric\u002Fcyberware-rust\n- Gears libraries(the ones that leverage this CLI tool) are located\n  in https:\u002F\u002Fgithub.com\u002Fconstructorfabric\u002Fcyberware-rust\u002Ftree\u002Fmain\u002Flibs\n- More documentation of the project will be located in https:\u002F\u002Fgithub.com\u002Fconstructorfabric\u002Fcyberware-rust\u002Ftree\u002Fmain\u002Fdocs\n\nClone(shallow) the repo to .gears folder (create it if it doesn't exist), and use it as a reference.\nIf so, prefer to use the ssh version instead of https to avoid authentication issues.\n\n## Command Tree\n\n```text\ncargo gears\n├── generate\n│   ├── workspace\n│   ├── gear\n│   └── config\n├── new\n├── config\n│   ├── mod\n│   │   ├── add\n│   │   ├── db\n│   │   │   ├── add\n│   │   │   ├── edit\n│   │   │   └── rm\n│   │   └── rm\n│   └── db\n│       ├── add\n│       ├── edit\n│       └── rm\n├── src\n├── help\n│   ├── schema\n│   ├── src\n│   └── topic\n├── lint\n├── ls\n│   ├── gears\n│   ├── templates\n│   ├── features\n│   ├── deps\n│   ├── packages\n│   └── targets\n├── manifest\n│   ├── validate\n│   └── ls\n├── test\n├── tools\n│   └── check-version\n├── run\n├── build\n├── clean\n└── deploy\n```\n\n## Shared Argument Patterns\n\n- **[`-p, --path \u003CPATH>`]** Optional workspace path. When provided to `config ...`, `build`, `run`, `deploy`, `lint`,\n  and `test`, relative config paths, manifest paths, generated project locations, and workspace-scoped lint\u002Ftest resolution use\n  that directory as the workspace root. When omitted, the current working directory is used as the workspace root.\n- **[`-c, --config \u003CPATH>`]** Config file path. This is required for `config ...` and `deploy` commands because there is\n  no default. `build` and `run` no longer accept `--config`; they compose their generation inputs from `Gears.toml`\n  and forward the manifest-declared runtime config path through the `GEARS_CONFIG` environment variable.\n- **[`--manifest \u003CPATH>`]** Gears manifest path, defaulting to `Gears.toml`, for `manifest`, `build`, `run`,\n  `lint`, and `test`.\n  For `manifest`, you can combine this with `-p\u002F--path` to resolve relative manifest paths from a selected workspace.\n- **[`--app \u003CAPP> --env \u003CENV>`]** Selects a manifest app\u002Fenvironment for manifest-driven `build`, `run`, `lint`, and `test`.\n  When omitted, inferred from the manifest: a single app is used automatically; with multiple apps the command\n  fails listing available names. For environments, `dev` is selected by default if it exists; otherwise the\n  command fails listing available names.\n- **[`--name \u003CNAME>`]** For `build` and `run`, overrides the generated server project and binary name that would\n  otherwise default to the config filename stem.\n- **[`-v, --verbose`]** Usually enables more logging or richer output.\n- **[name validation]** Config-managed names for modules, DB servers, and generated server names only allow letters,\n  numbers, `-`, and `_`.\n\n## What the Tool Manages\n\nFrom the current implementation, the CLI is mainly for:\n\n- **[workspace scaffolding]** Initialize a Gears workspace and add module templates\n- **[config management]** Enable modules and patch YAML config sections\n- **[server generation]** Generate a runnable Cargo project under the manifest `workspace.generated-dir` directory\n  (default `.gears\u002F\u003Cname>\u002F`)\n- **[manifest orchestration]** Read `Gears.toml` to separate generation metadata from runtime YAML config\n- **[build\u002Frun\u002Fclean\u002Fdeploy]** Build, run, clean, or package that generated server as a Docker image\n- **[source inspection]** Resolve Rust source for crates\u002Fitems through workspace metadata or crates.io\n- **[module inspection]** List workspace-discovered and system-registry modules\n- **[tool bootstrap]** Install or upgrade `rustup`, `cargofmt`, and `clippy`\n\n## Top-Level Commands\n\n### `generate`\n\nGenerate workspace, module, and config scaffolding from built-in templates or explicit local\u002FGit template sources.\n\n#### `generate workspace`\n\nSynopsis:\n\n```bash\ncargo gears generate workspace [\u003Cpath>] [--template \u003CTEMPLATE>] [--list] [--verbose] [--name \u003CNAME>] [--local-path \u003CPATH>] [--git \u003CURL>] [--subfolder \u003CNAME>] [--branch \u003CNAME>] [--override]\n```\n\nArguments:\n\n- **[`\u003Cpath>`]** Target directory to initialize; not required with `--list`\n- **[`-t, --template \u003CTEMPLATE>`]** Workspace template name, defaults to `basic-init`; `default` is accepted as a compatibility alias\n- **[`-l, --list`]** List built-in workspace templates plus manifest `templates.workspace` entries when a `Gears.toml` exists at the selected path\n- **[`-v, --verbose`]** Verbose output from `cargo-generate`\n- **[`-n, --name \u003CNAME>`]** Override the generated project name; inferred from the final path segment by default\n- **[`--local-path \u003CPATH>`]** Use a local template directory instead of the default Git template\n- **[`--git \u003CURL>`]** Override the Git URL for the template\n- **[`--subfolder \u003CNAME>`]** Override the template subfolder\n- **[`--branch \u003CNAME>`]** Override the template branch\n- **[`--override`]** Allow generated files to overwrite existing files\n\nBehavior:\n\n- **[creates target directory]** If it does not exist\n- **[fails on file path]** Errors if `\u003Cpath>` already exists and is not a directory\n- **[uses directory name as project name]** The final path segment becomes the generated project name unless `--name` is\n  provided\n- **[uses template registry]** Template names resolve through the built-in registry and then manifest-defined templates\n- **[forces git init]** Template generation runs with Git initialization enabled\n- **[pins dylint lints]** Pins `cargo-gears-lints` to the CLI's release tag in the generated workspace's Dylint\n  metadata, as `lint --pin-dylint` does. If that fails (for example, the template has no workspace `Cargo.toml`), it\n  only warns\n\nExamples:\n\n```bash\ncargo gears generate workspace \u002Ftmp\u002Fcf-demo\n```\n\n```bash\ncargo gears generate workspace \u002Ftmp\u002Fcf-demo --git https:\u002F\u002Fgithub.com\u002Fconstructorfabric\u002Fcf-template-rust --branch main --subfolder Init\n```\n\n```bash\ncargo gears generate workspace \u002Ftmp\u002Fcf-demo --local-path ~\u002Fdev\u002Fcf-template-rust\n```\n\n```bash\ncargo gears generate workspace --list\n```\n\n#### `generate gear`\n\nGenerate a gear template inside an existing workspace's `gears\u002F` directory and wire Cargo workspace dependencies.\n\nSynopsis:\n\n```bash\ncargo gears generate gear [--template \u003CTEMPLATE>] [--list] [--name \u003CNAME>] [--path \u003CPATH>] [--verbose] [--local-path \u003CPATH>] [--git \u003CURL>] [--subfolder \u003CNAME>] [--branch \u003CNAME>]\n```\n\nAvailable built-in templates:\n\n- **[`background-worker`]** Background worker module template\n- **[`api-db-handler`]** API\u002Fdatabase handler module template\n- **[`api-gateway`]** API gateway module template. Unless the user instruct to implement its own api-gateway, prefer the system module cf-api-gateway\n\nArguments:\n\n- **[`-t, --template \u003CTEMPLATE>`]** Gear template name; not required with `--list`\n- **[`-l, --list`]** List built-in gear templates plus manifest `templates.gear` entries when a `Gears.toml` exists at the selected path\n- **[`-n, --name \u003CNAME>`]** Generated gear folder\u002Fcrate name; defaults to the template name. Prefer passing this when\n  the generated gear should use the user's chosen name.\n- **[`-p, --path \u003CPATH>`]** Workspace root, defaults to `.`\n- **[`-v, --verbose`]** Verbose template generation output\n- **[`--local-path \u003CPATH>`]** Use a local template directory instead of the default Git template\n- **[`--git \u003CURL>`]** Override the Git URL for the template\n- **[`--subfolder \u003CNAME>`]** Override the template subfolder\n- **[`--branch \u003CNAME>`]** Override the template branch\n\nBehavior:\n\n- **[requires `gears\u002F`]** Fails unless `\u003Cworkspace>\u002Fgears` already exists\n- **[creates `gears\u002F\u003Cname>`]** Uses `--name` when provided, otherwise the template name\n- **[prevents duplicate]** Fails if that gear directory already exists\n- **[updates workspace members]** Adds generated modules to `workspace.members`\n- **[promotes dependencies]** Moves new gear dependency source\u002Fversion metadata into `workspace.dependencies`\n- **[rewrites gear Cargo files]** Rewrites gear dependencies to `workspace = true`\n- **[inherits workspace lints]** Adds `lints.workspace = true` to generated modules if needed\n- **[includes SDK crate when present]** If the generated gear contains `sdk\u002F`, it is also added as a workspace member\n\nExamples:\n\n```bash\ncargo gears generate gear --template background-worker -p \u002Ftmp\u002Fcf-demo\n```\n\n```bash\ncargo gears generate gear --template background-worker --name jobs -p \u002Ftmp\u002Fcf-demo\n```\n\n```bash\ncargo gears generate gear --template rest-api -p \u002Ftmp\u002Fcf-demo\n```\n\n```bash\ncargo gears generate gear --list -p \u002Ftmp\u002Fcf-demo\n```\n\n#### `generate config`\n\nGenerate a runtime YAML config file from a built-in template.\n\nSynopsis:\n\n```bash\ncargo gears generate config --template \u003Cdev|prod|db> [--app \u003CAPP>] [--env \u003CENV>] [--name \u003CNAME>] [--path \u003CPATH>]\n```\n\nBuilt-in templates:\n\n- **[`dev`]** Development-friendly runtime config\n- **[`prod`]** Production-oriented runtime config\n- **[`db`]** Development config with a `database.servers.main` section\n\nArguments:\n\n- **[`-t, --template \u003CTEMPLATE>`]** Config template name\n- **[`--app \u003CAPP>`]** Application name used for output filename\n- **[`--env \u003CENV>`]** Environment name used for output filename\n- **[`--name \u003CNAME>`]** Custom output filename; `.yml` is appended when no YAML extension is provided\n- **[`-p, --path \u003CPATH>`]** Workspace root, defaults to `.`\n\nBehavior:\n\n- **[writes under `config\u002F`]** Output path is `\u003Cworkspace>\u002Fconfig\u002F\u003Cfilename>`\n- **[filename resolution]** `--name` wins; otherwise `\u003Capp>-\u003Cenv>.yml`, `\u003Capp>.yml`, `\u003Cenv>.yml`, or `\u003Ctemplate>.yml`\n- **[prevents overwrites]** Fails if the target config file already exists\n- **[runtime values only]** Generated config contains runtime settings, not dependency metadata\n\nExamples:\n\n```bash\ncargo gears generate config --template dev --app app1 --env dev -p \u002Ftmp\u002Fcf-demo\n```\n\n```bash\ncargo gears generate config --template db --name local-db -p \u002Ftmp\u002Fcf-demo\n```\n\n### `new`\n\nAlias for `generate workspace`.\n\nSynopsis:\n\n```bash\ncargo gears new \u003Cpath> [--template \u003CTEMPLATE>] [--verbose] [--name \u003CNAME>] [--local-path \u003CPATH>] [--git \u003CURL>] [--subfolder \u003CNAME>] [--branch \u003CNAME>] [--override]\n```\n\n### `config`\n\nManages the YAML application config file used by `build` and `run`.\n\nThere are two branches:\n\n- **[`config mod ...`]** Module configuration\n- **[`config db ...`]** Global database server configuration\n\n### `config mod`\n\nManage the `modules` section in the app config.\n\n#### `config mod add`\n\nAdd or update a module entry in the config file's `modules` section.\n\nSynopsis:\n\n```bash\ncargo gears config mod add -c \u003CCONFIG> [-p \u003CPATH>] [--package \u003CNAME>] [--module-version \u003CVER>] [--default-features \u003CBOOL>] [-F, --feature \u003CFEATURES>]... [--dep \u003CNAME>]... \u003Cmodule>\n```\n\nArguments:\n\n- **[`\u003Cmodule>`]** Module name in the config\n- **[`-c, --config \u003CCONFIG>`]** Required config file path\n- **[`-p, --path \u003CPATH>`]** Optional workspace directory\n- **[`--package \u003CNAME>`]** Override metadata package name\n- **[`--module-version \u003CVER>`]** Override metadata version\n- **[`--default-features \u003CBOOL>`]** Persist Cargo `default_features`\n- **[`-F, --feature \u003CFEATURES>`]** Feature list; accepts comma-separated values and can be repeated\n- **[`--dep \u003CNAME>`]** Metadata dependency name; repeat to add more\n\nBehavior:\n\n- **[upsert]** Creates or updates `modules.\u003Cmodule>`\n- **[path activation]** If `-p\u002F--path` is provided, Clap changes the current working directory while parsing that value,\n  before `-c\u002F--config` is resolved\n- **[local-first discovery]** Tries to discover module metadata from the workspace\n- **[remote module support]** If the module is not local, you must provide both `--package` and `--module-version`\n- **[portable metadata]** Local filesystem paths are intentionally not persisted into config metadata\n- **[merge semantics]** Existing metadata fields are preserved unless you explicitly override them\n- **[metadata requirements]** Package and version are required in the resulting metadata, whether sourced locally or\n  passed explicitly\n\nExamples:\n\n```bash\ncargo gears config mod add background-worker -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fquickstart.yml\n```\n\n```bash\ncargo gears config mod add api-gateway -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fquickstart.yml -F json,metrics -F tracing --dep authn-resolver --dep tenant-resolver\n```\n\n```bash\ncargo gears config mod add credstore -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fquickstart.yml --package cf-credstore --module-version 0.4.2\n```\n\n```bash\ncargo gears config mod add api-db-handler -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fquickstart.yml --default-features false\n```\n\n#### `config mod rm`\n\nRemove a module from the config file's `modules` section.\n\nSynopsis:\n\n```bash\ncargo gears config mod rm -c \u003CCONFIG> [-p \u003CPATH>] \u003Cmodule>\n```\n\nBehavior:\n\n- **[path activation]** If `-p\u002F--path` is provided, Clap changes the current working directory while parsing that value,\n  before `-c\u002F--config` is resolved\n- **[strict removal]** Fails if the module is not present in config\n\nExample:\n\n```bash\ncargo gears config mod rm background-worker -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fquickstart.yml\n```\n\n#### `config mod db`\n\nManage module-level database config under `modules.\u003Cmodule>.database`.\n\nSubcommands:\n\n- **[`add`]** Add or patch a module DB config\n- **[`edit`]** Edit an existing module DB config\n- **[`rm`]** Remove a module DB config\n\nShared DB flags:\n\n- **[`--engine \u003Cpostgres|mysql|sqlite>`]**\n- **[`--dsn \u003CDSN>`]**\n- **[`--host \u003CHOST>`]**\n- **[`--port \u003CPORT>`]**\n- **[`--user \u003CUSER>`]**\n- **[`--password \u003CPASSWORD>`]**\n- **[`--dbname \u003CNAME>`]**\n- **[`--params \u003CK=V,...>`]**\n- **[`--sqlite-file \u003CFILE>`]**\n- **[`--sqlite-path \u003CPATH>`]**\n- **[`--pool-max-conns \u003CN>`]**\n- **[`--pool-min-conns \u003CN>`]**\n- **[`--pool-acquire-timeout-secs \u003CSECS>`]**\n- **[`--pool-idle-timeout-secs \u003CSECS>`]**\n- **[`--pool-max-lifetime-secs \u003CSECS>`]**\n- **[`--pool-test-before-acquire \u003CBOOL>`]**\n- **[`--server \u003CNAME>`]** Reference a named global DB server\n\nRules:\n\n- **[path activation]** If `-p\u002F--path` is provided, each subcommand changes the current working directory while Clap is\n  parsing that value, before `-c\u002F--config` is resolved\n- **[payload required]** `add` and `edit` require at least one DB-related field\n- **[module must exist]** `add` requires the module already exist in config and recommends `config mod add` first\n- **[edit requires existing DB config]** `edit` fails if no module DB config exists yet\n- **[patch semantics]** `add` and `edit` patch only the fields you provide\n\nExamples:\n\n```bash\ncargo gears config mod db add background-worker -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fquickstart.yml --server primary\n```\n\n```bash\ncargo gears config mod db add api-db-handler -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fquickstart.yml --engine postgres --host localhost --port 5432 --user app --password '${DB_PASSWORD}' --dbname appdb --pool-max-conns 20\n```\n\n```bash\ncargo gears config mod db edit api-db-handler -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fquickstart.yml --pool-acquire-timeout-secs 30 --pool-test-before-acquire true\n```\n\n```bash\ncargo gears config mod db rm api-db-handler -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fquickstart.yml\n```\n\n### `config db`\n\nManage global database server config under `database.servers`.\n\nSubcommands:\n\n- **[`add`]** Add or upsert a named global DB server\n- **[`edit`]** Edit an existing global DB server\n- **[`rm`]** Remove an existing global DB server\n\nSynopsis:\n\n```bash\ncargo gears config db add  -c \u003CCONFIG> [-p \u003CPATH>] \u003Cname> \u003Cdb-flags...>\ncargo gears config db edit -c \u003CCONFIG> [-p \u003CPATH>] \u003Cname> \u003Cdb-flags...>\ncargo gears config db rm   -c \u003CCONFIG> [-p \u003CPATH>] \u003Cname>\n```\n\nBehavior:\n\n- **[path activation]** If `-p\u002F--path` is provided, each subcommand changes the current working directory while Clap is\n  parsing that value, before `-c\u002F--config` is resolved\n- **[server name]** Stored under `database.servers.\u003Cname>`\n- **[add is upsert]** `add` creates or patches an existing server entry\n- **[edit is strict]** `edit` requires the server to already exist\n- **[payload required]** `add` and `edit` require at least one DB-related field\n- **[cleanup]** `rm` removes the top-level `database` section if it becomes empty and `auto_provision` is unset\n\nExamples:\n\n```bash\ncargo gears config db add primary -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fquickstart.yml --engine postgres --host localhost --port 5432 --user app --password '${DB_PASSWORD}' --dbname appdb\n```\n\n```bash\ncargo gears config db edit primary -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fquickstart.yml --pool-max-conns 30 --pool-idle-timeout-secs 120\n```\n\n```bash\ncargo gears config db add local-sqlite -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fquickstart.yml --engine sqlite --sqlite-path \u002Ftmp\u002Fcf-demo\u002Fdev.db\n```\n\n```bash\ncargo gears config db rm primary -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fquickstart.yml\n```\n\n### `src`\n\nResolve Rust source for a crate\u002Fmodule\u002Fitem query from local workspace metadata, the local source cache, or crates.io.\n\nSynopsis:\n\n```bash\ncargo gears src [--path \u003CPATH>] [--registry \u003CREGISTRY>] [--verbose] [--libs] [--version \u003CVERSION>] [--clean] [\u003Cquery>]\n```\n\nArguments:\n\n- **[`-p, --path \u003CPATH>`]** Workspace or crate to inspect, defaults to `.`\n- **[`--registry \u003CREGISTRY>`]** Registry fallback, defaults to `crates.io`\n- **[`-v, --verbose`]** Print resolution metadata before the source\n- **[`-l, --libs`]** Print `library_name -> package_name` mappings for a package query instead of source\n- **[`--version \u003CVERSION>`]** Resolve a specific crate version after metadata\u002Fcache lookup misses\n- **[`--clean`]** Remove the source cache for the selected registry before resolving\n- **[`[\u003Cquery>]`]** Rust path to resolve, starting with the package name; omitted only when `--clean` is used by itself\n\nSupported query examples:\n\n- **[`cf-gears-toolkit`]**\n- **[`tokio::sync`]**\n- **[`cf-gears-toolkit::gts::plugin::BaseGearsPluginV1`]**\n- **[`cf-gears-toolkit::gts::schemas::get_core_gts_schemas`]**\n\nBehavior:\n\n- **[query requirement]** A query is required unless `--clean` is passed by itself\n- **[package-only libs mode]** `--libs` requires a package-only query such as `cf-gears-toolkit`\n- **[local resolution first]** Tries workspace metadata before hitting the network\n- **[cache-first registry fallback]** Reuses cached crate sources before downloading from the registry\n- **[crates.io fallback]** Downloads and extracts crate source if local resolution and cache lookup both fail\n- **[exact version fallback]** `--version` pins the registry\u002Fcache fallback to that exact crate version\n- **[recursive re-export resolution]** Follows re-exports across `crate`, `self`, `super`, and dependency boundaries\n  until it reaches the final source\n- **[library mapping output]** `--libs` prints the Rust source-code library name on the left and the Cargo package\n  name on the right, including renamed dependencies like `gears_toolkit_macros -> cf-gears-toolkit-macros`\n- **[cache location]** Registry sources are cached under the OS temp directory in `gears-docs-cache\u002F\u003Cregistry>\u002F` (legacy name)\n- **[cache cleaning]** `--clean` removes the selected registry cache before resolution\n- **[source output]** Prints the resolved Rust source to stdout\n- **[verbose metadata]** Also prints query, package, library, version, manifest path, and source path\n- **[registry support]** Only `crates.io` is supported today\n\nExamples:\n\n```bash\ncargo gears src -p \u002Ftmp\u002Fcf-demo cf-gears-toolkit\n```\n\n```bash\ncargo gears src cf-gears-toolkit::module\n```\n\n```bash\ncargo gears src --verbose tokio::sync\n```\n\n```bash\ncargo gears src --libs cf-gears-toolkit\n```\n\n```bash\ncargo gears src --version 1.0.217 serde::de::Deserialize\n```\n\n```bash\ncargo gears src --clean\n```\n\n```bash\ncargo gears src --clean -p \u002Ftmp\u002Fcf-demo tokio::sync\n```\n\n### `help`\n\nSchema, topic, and source-code help for developers and LLMs. Groups three subcommands under a\nsingle discoverable entry point.\n\n#### `help schema`\n\nPrint the schema for manifest, config, or module formats.\n\nSynopsis:\n\n```bash\ncargo gears help schema \u003Cmanifest|config|module> [--section \u003CSECTION>]\n```\n\nArguments:\n\n- **[`\u003Ctarget>`]** Schema target: `manifest`, `config`, or `module`\n- **[`--section \u003CSECTION>`]** Drill into a specific section of the schema\n\nBehavior:\n\n- **[overview mode]** Without `--section`, prints a top-level overview of the schema\n- **[section mode]** With `--section`, prints detailed field documentation for that section\n- **[manifest sections]** `workspace`, `apps`, `templates`\n- **[config sections]** `server`, `database`, `logging`, `opentelemetry`, `modules`\n- **[module sections]** None (only the overview is available)\n\nExamples:\n\n```bash\ncargo gears help schema manifest\n```\n\n```bash\ncargo gears help schema config --section database\n```\n\n```bash\ncargo gears help schema module\n```\n\n#### `help src`\n\nAlias for the top-level `src` command. Resolves Rust source code from a crate.\n\nSynopsis:\n\n```bash\ncargo gears help src [--path \u003CPATH>] [--registry \u003CREGISTRY>] [--verbose] [--libs] [--version \u003CVERSION>] [--clean] [\u003Cquery>]\n```\n\nBehavior identical to `src`; see the `src` section above.\n\n#### `help topic`\n\nPrint operational documentation for a named topic.\n\nSynopsis:\n\n```bash\ncargo gears help topic \u003CTOPIC>\n```\n\nAvailable topics:\n\n- **[`architecture`]** Framework architecture, three-tier hierarchy, and principles\n- **[`cli`]** CLI reference, guidelines, and command overview\n- **[`clienthub`]** Typed ClientHub, plugins, and GTS\n- **[`database`]** SecureConn, transactions, migrations, and repository pattern\n- **[`errors`]** RFC-9457 Problem error handling\n- **[`fips`]** FIPS mode activation and usage\n- **[`gear-layout`]** Gear directory structure and SDK pattern\n- **[`gear-refs`]** How local and remote gears are referenced\n- **[`gears-catalog`]** Gear categories and dependency rules\n- **[`generated-server`]** How the ephemeral generated server project works\n- **[`lifecycle`]** Gear lifecycle, cancellation, and background tasks\n- **[`manifest`]** Overview of `Gears.toml` and manifest-driven workflows\n- **[`otel`]** OpenTelemetry activation and runtime configuration\n- **[`rest-api`]** OperationBuilder, OpenAPI, SSE, and OData\n- **[`security`]** AuthN, AuthZ, SecureConn, and AccessScope\n\nExamples:\n\n```bash\ncargo gears help topic architecture\n```\n\n```bash\ncargo gears help topic gear-layout\n```\n\n```bash\ncargo gears help topic generated-server\n```\n\n```bash\ncargo gears help topic otel\n```\n\n### `tools`\n\nInstall or upgrade a small set of Rust tooling dependencies.\n\nKnown tool names:\n\n- **[`rustup`]**\n- **[`cargofmt`]** Installs the `rustfmt` rustup component\n- **[`clippy`]**\n\nSynopsis:\n\n```bash\ncargo gears tools (--all | --install \u003Ctool,...>) [--upgrade] [--yolo] [--verbose]\n```\n\nArguments:\n\n- **[`-a, --all`]** Select all known tools\n- **[`--install \u003Ctool,...>`]** Comma-separated tool names\n- **[`-u, --upgrade`]** Upgrade instead of initial install\n- **[`-y, --yolo`]** Skip confirmation prompts\n- **[`-v, --verbose`]** Show subprocess output\n\nBehavior:\n\n- **[selection required]** You must pass either `--all` or `--install`\n- **[interactive by default]** Without `--yolo`, the command prompts before installing\u002Fupgrading\n- **[rustup bootstrap]** If `rustup` is missing, the CLI can attempt to install it\n- **[component installs]** `cargofmt` and `clippy` are installed through `rustup component add`\n- **[upgrade mode]** Selected `rustup` upgrades via `rustup self update`; selected components upgrade via\n  `rustup update`\n\nExamples:\n\n```bash\ncargo gears tools --all\n```\n\n```bash\ncargo gears tools --install clippy,cargofmt --yolo\n```\n\n```bash\ncargo gears tools --install rustup,clippy --upgrade --verbose\n```\n\n#### `tools check-version`\n\nCheck that an external tool satisfies a semver version requirement by running `\u003Ctool> --version`,\nparsing the version from the output, and comparing it against the requirement. Exits 0 (printing\nthe version) if satisfied, or 1 if not.\n\nSynopsis:\n\n```bash\ncargo gears tools check-version \u003CTOOL> \u003CREQUIREMENT>\n```\n\nArguments:\n\n- **[`\u003CTOOL>`]** Tool binary name (e.g. `cargo-deny`, `cargo-nextest`)\n- **[`\u003CREQUIREMENT>`]** Semver requirement (e.g. `>=0.20.0`, `^0.9.130`)\n\nBehavior:\n\n- **[runs tool]** Invokes `\u003Ctool> --version` and parses the first semver token from stdout\n- **[exit code]** Exits 0 and prints the version if the requirement is satisfied; exits 1 with an error\n  message if not satisfied, if the tool is not installed, or if the version cannot be parsed\n\nExamples:\n\n```bash\ncargo gears tools check-version cargo-deny '>=0.20.0'\n```\n\n```bash\ncargo gears tools check-version cargo-nextest '^0.9.130'\n```\n\n### `run`\n\nGenerate a server project under the manifest `\u003Cworkspace.generated-dir>\u002F\u003Cname>` and run it.\n\nSynopsis:\n\n```bash\ncargo gears run [--app \u003CAPP>] [--env \u003CENV>] [--manifest \u003CGears.toml>] [-p \u003CPATH>] [--name \u003CNAME>] [--watch|--no-watch] [--otel|--no-otel] [--fips|--no-fips] [--release|--no-release] [--locked] [--clean|--no-clean] [--dry-run]\n```\n\nArguments:\n\n- **[`--manifest \u003CPATH>`]** Manifest file, defaults to `Gears.toml`\n- **[`--app \u003CAPP> --env \u003CENV>`]** Manifest app\u002Fenvironment selection (inferred from manifest if omitted)\n- **[`-p, --path \u003CPATH>`]** Optional workspace directory\n- **[`--name \u003CNAME>`]** Override the generated server project and binary name; defaults to the config filename stem\n- **[`-w, --watch` \u002F `--no-watch`]** Override manifest watch policy on or off\n- **[`--otel` \u002F `--no-otel`]** Override manifest OpenTelemetry policy on or off\n- **[`--fips` \u002F `--no-fips`]** Override manifest FIPS policy on or off\n- **[`-r, --release` \u002F `--no-release`]** Override manifest build profile to release or non-release\n- **[`--locked`]** Require `Cargo.lock` is up to date; passed as `--locked` to `cargo run`\n- **[`--clean` \u002F `--no-clean`]** Override manifest clean policy on or off\n- **[`--dry-run`]** Generate the project structure and print the generated files without building or running\n\nBehavior:\n\n- **[name resolution]** Uses the manifest build policy name when present, otherwise `\u003Capp>-\u003Cenv>`\n- **[path activation]** If `-p\u002F--path` is provided, Clap changes the current working directory while parsing that value,\n  before `Gears.toml` is resolved and the generated project directory is created\n- **[generates server structure]** Writes `\u003Cgenerated-dir>\u002F\u003Cname>\u002FCargo.toml`,\n  `\u003Cgenerated-dir>\u002F\u003Cname>\u002F.cargo\u002Fconfig.toml`, and `\u003Cgenerated-dir>\u002F\u003Cname>\u002Fsrc\u002Fmain.rs`; `generated-dir` comes from\n  manifest `workspace.generated-dir` and defaults to `.gears`\n- **[runtime config handoff]** The generated `src\u002Fmain.rs` reads the config path from `GEARS_CONFIG`, and\n  `cargo gears run` sets that environment variable automatically before invoking `cargo run`\n- **[dry run]** `--dry-run` writes the generated project structure under `\u003Cgenerated-dir>\u002F\u003Cname>\u002F` and prints JSON with the\n  generated project directory plus each generated file path and contents; it does not invoke Cargo build\u002Frun\n- **[manifest mode]** Reads generation dependencies, runtime config path, and policies from `Gears.toml`; runtime YAML\n  stays focused on server configuration\n- **[exclusive boolean overrides]** Boolean flag pairs are mutually exclusive. Use either the positive or negative form,\n  not both; for example, `--otel --no-otel` is rejected. When neither side is present, the manifest policy is used.\n- **[runs inside generated project]** Executes `cargo run` in `\u003Cgenerated-dir>\u002F\u003Cname>\u002F`\n- **[watch mode]** Restarts on runtime config changes and changes in watched local modules; regenerates and reruns when\n  workspace `Cargo.toml` or the selected `Gears.toml` changes\n- **[watch policy]** Manifest `run.watch.include` replaces the default watch set; `run.watch.exclude` removes matching\n  paths from either the default set or an explicit include set\n- **[manual generated-project execution]** If you invoke the generated project or compiled binary yourself instead of\n  using `cargo gears run`, you must set `GEARS_CONFIG` manually\n\nExamples:\n\n```bash\ncargo gears run -p \u002Ftmp\u002Fcf-demo --app app1 --env dev\n```\n\n```bash\ncargo gears run -p \u002Ftmp\u002Fcf-demo --app app1 --env dev --watch\n```\n\n```bash\ncargo gears run -p \u002Ftmp\u002Fcf-demo --app app1 --env dev --otel --fips --release --clean\n```\n\n```bash\ncargo gears run -p \u002Ftmp\u002Fcf-demo --app app1 --env dev --name demo-server\n```\n\n```bash\ncargo gears run -p \u002Ftmp\u002Fcf-demo --app app1 --env dev --dry-run\n```\n\n```bash\ncargo gears run -p \u002Ftmp\u002Fcf-demo --app app1 --env dev --manifest \u002Ftmp\u002Fcf-demo\u002FGears.toml\n```\n\n### `manifest`\n\nInspect and validate Gears manifest files.\n\nSynopsis:\n\n```bash\ncargo gears manifest [-p \u003CPATH>] [--manifest \u003CGears.toml>] validate [--format table|json]\ncargo gears manifest [-p \u003CPATH>] [--manifest \u003CGears.toml>] ls [--format table|json]\n```\n\nBehavior:\n\n- **[path activation]** If `-p\u002F--path` is provided, relative manifest paths are resolved from that workspace directory.\n- **[environment gears]** Manifest environments declare generation dependencies under the `gears` key.\n- **[validate]** Parses the manifest and resolves every app\u002Fenvironment entry.\n- **[ls]** Lists configured app\u002Fenvironment pairs with their resolved config paths and generated build names.\n- **[generated structure]** Use `build --dry-run` or `run --dry-run` to write and print the generated project structure.\n\n### `build`\n\nGenerate a server project under the manifest `\u003Cworkspace.generated-dir>\u002F\u003Cname>` and build it.\n\nSynopsis:\n\n```bash\ncargo gears build [--app \u003CAPP>] [--env \u003CENV>] [--manifest \u003CGears.toml>] [-p \u003CPATH>] [--name \u003CNAME>] [--otel|--no-otel] [--fips|--no-fips] [--release|--no-release] [--locked] [--clean|--no-clean] [--dry-run]\n```\n\nArguments:\n\n- **[`--manifest \u003CPATH>`]** Manifest file, defaults to `Gears.toml`\n- **[`--app \u003CAPP> --env \u003CENV>`]** Manifest app\u002Fenvironment selection (inferred from manifest if omitted)\n- **[`-p, --path \u003CPATH>`]** Optional workspace directory\n- **[`--name \u003CNAME>`]** Override the generated server project and binary name; defaults to the config filename stem\n- **[`--otel` \u002F `--no-otel`]** Override manifest OpenTelemetry policy on or off\n- **[`--fips` \u002F `--no-fips`]** Override manifest FIPS policy on or off\n- **[`-r, --release` \u002F `--no-release`]** Override manifest build profile to release or non-release\n- **[`--locked`]** Require `Cargo.lock` is up to date; passed as `--locked` to `cargo build`\n- **[`--clean` \u002F `--no-clean`]** Override manifest clean policy on or off\n- **[`--dry-run`]** Generate the project structure and print the generated files without building\n\nBehavior:\n\n- **[generates before build]** Recreates the generated server project before invoking Cargo\n- **[name resolution]** Uses the manifest build policy name when present, otherwise `\u003Capp>-\u003Cenv>`\n- **[path activation]** If `-p\u002F--path` is provided, Clap changes the current working directory while parsing that value,\n  before `Gears.toml` is resolved and the generated project directory is created\n- **[exclusive boolean overrides]** Boolean flag pairs are mutually exclusive. Use either the positive or negative form,\n  not both; for example, `--clean --no-clean` is rejected. When neither side is present, the manifest policy is used.\n- **[manifest mode]** Reads module dependency metadata, runtime config path, and build\u002Frun policy from `Gears.toml`\n  instead of runtime YAML module metadata\n- **[builds inside generated project]** Executes `cargo build` in `\u003Cgenerated-dir>\u002F\u003Cname>\u002F`\n- **[runtime config source]** The generated server no longer embeds the config path; the resulting binary reads it from\n  `GEARS_CONFIG` when you execute it\n- **[dry run]** `--dry-run` writes the generated project structure under `\u003Cgenerated-dir>\u002F\u003Cname>\u002F` and prints JSON with the\n  generated project directory plus each generated file path and contents; it does not invoke Cargo build\n- **[manual generated-project execution]** If you later run the generated project or binary outside the CLI, you must\n  set `GEARS_CONFIG` yourself\n\nExamples:\n\n```bash\ncargo gears build -p \u002Ftmp\u002Fcf-demo --app app1 --env dev\n```\n\n```bash\ncargo gears build -p \u002Ftmp\u002Fcf-demo --app app1 --env dev --release\n```\n\n```bash\ncargo gears build -p \u002Ftmp\u002Fcf-demo --app app1 --env dev --otel --fips --clean\n```\n\n```bash\ncargo gears build -p \u002Ftmp\u002Fcf-demo --app app1 --env dev --name demo-server\n```\n\n```bash\ncargo gears build -p \u002Ftmp\u002Fcf-demo --app app1 --env prod\n```\n\n```bash\ncargo gears build -p \u002Ftmp\u002Fcf-demo --app app1 --env prod --dry-run\n```\n\n### `clean`\n\nSuperset of `cargo clean`: removes build artifacts, the generated server project, and its workspace member entry\nfrom the root `Cargo.toml`.\n\nSynopsis:\n\n```bash\ncargo gears clean [--app \u003CAPP>] [--env \u003CENV>] [--manifest \u003CGears.toml>] [-p \u003CPATH>]\n```\n\nArguments:\n\n- **[`--manifest \u003CPATH>`]** Manifest file, defaults to `Gears.toml`\n- **[`--app \u003CAPP> --env \u003CENV>`]** Manifest app\u002Fenvironment selection (inferred from manifest if omitted)\n- **[`-p, --path \u003CPATH>`]** Optional workspace directory\n\nBehavior:\n\n- **[runs `cargo clean` first]** Removes build artifacts from the workspace `target\u002F` directory. If this fails due to\n  a broken workspace (e.g. missing generated member), the error is ignored and cleanup continues -- fixing such\n  broken state is the purpose of this command. Other `cargo clean` failures (permissions, disk errors, etc.) are\n  propagated as errors.\n- **[resolves target without dependencies]** Reads `Gears.toml` to determine the generated project directory and name\n  without resolving module dependencies or running `cargo metadata`\n- **[deletes generated project]** Removes `\u003Cgenerated-dir>\u002F\u003Cname>\u002F` (e.g. `.gears\u002Fproducts-dev\u002F`)\n- **[removes workspace member]** Removes the generated project entry from the `workspace.members` array in the root\n  `Cargo.toml`\n- **[cleans up empty generated dir]** If the generated directory (e.g. `.gears\u002F`) is empty after removal, it is also\n  deleted\n- **[runs `cargo clean` last]** After fixing the workspace, runs `cargo clean` to remove build artifacts from the\n  `target\u002F` directory. By running last, the workspace is guaranteed to be consistent so `cargo clean` succeeds\n  even when the generated member was previously missing or broken.\n- **[idempotent]** Running `clean` when the generated project does not exist is a no-op\n\nExamples:\n\n```bash\ncargo gears clean\n```\n\n```bash\ncargo gears clean --app app1 --env dev\n```\n\n```bash\ncargo gears clean -p \u002Ftmp\u002Fcf-demo\n```\n\n### `deploy`\n\nBuild a Docker image for the generated or provided server manifest.\n\nSynopsis:\n\n```bash\ncargo gears deploy [--app \u003CAPP>] [--env \u003CENV>] [--manifest \u003CGears.toml>] [-p \u003CPATH>] [-t \u003CTAG>] [-m \u003CCargo.toml>] [-c \u003CCONFIG>] [--debug] [--dockerfile \u003CPATH>] [--args \u003CKEY=VALUE>]...\n```\n\nArguments:\n\n- **[`-p, --path \u003CPATH>`]** Optional workspace directory used to resolve relative manifest paths\n- **[`--manifest \u003CPATH>`]** Gears manifest file, defaults to `Gears.toml`\n- **[`--app \u003CAPP> --env \u003CENV>`]** Manifest app\u002Fenvironment selection (inferred from manifest if omitted)\n- **[`-t, --tag \u003CTAG>`]** Tag for the Docker image; defaults to `gears:\u003Cversion>`\n- **[`-m, --manifest \u003CCargo.toml>`]** Optional Cargo manifest override; when omitted, uses the auto-resolved\n  generated project's `Cargo.toml` from the selected app\u002Fenv\n- **[`-c, --config \u003CCONFIG>`]** Optional config file override; when omitted, uses the config resolved from\n  the Gears.toml manifest\n- **[`--debug`]** Docker build mode; defaults to release mode. Use this flag to build in debug mode.\n- **[`--dockerfile \u003CPATH>`]** Dockerfile path to use instead of the default (Dockerfile from workspace root)\n- **[`--args \u003CKEY=VALUE>`]** Dockerfile `ARG` override passed as `docker build --build-arg`; repeat for multiple\n  overrides\n\nBehavior:\n\n- **[manifest selection]** Resolves the selected app\u002Fenvironment from `Gears.toml`, auto-selecting when there is\n  only one app\u002Fenv. The generated project's `Cargo.toml` and config path are derived automatically.\n- **[manifest override]** With `-m\u002F--manifest`, uses the provided Cargo.toml instead of the auto-resolved one;\n  its `package.name` is used as the artifact name\n- **[config override]** With `-c\u002F--config`, uses the provided config path instead of the manifest-resolved one\n- **[Dockerfile bootstrap]** If `Dockerfile` is missing from the selected workspace root, writes the shared CLI\n  Dockerfile there before running Docker\n- **[build context requirement]** The config file and selected manifest must be inside the workspace root because Docker\n  can only copy files from the build context\n- **[Docker args]** The CLI provides `BUILDER_MANIFEST`, `BUILD_MODE`, `ARTIFACT_NAME`, `LOCAL_CONFIG_PATH`, and\n  `CONFIG_EXT`; repeated `--args` values are appended afterward so they can override Dockerfile arguments\n\nExamples:\n\n```bash\n# Deploy using Gears.toml auto-selection (single app\u002Fenv)\ncargo gears deploy -p \u002Ftmp\u002Fcf-demo\n```\n\n```bash\n# Deploy a specific app\u002Fenv\ncargo gears deploy --app myapp --env dev -t my-app:latest\n```\n\n```bash\n# Deploy in debug mode\ncargo gears deploy --app myapp --env dev --debug\n```\n\n```bash\n# Deploy with an explicit Cargo manifest override\ncargo gears deploy --app myapp --env dev -m .gears\u002Fcustom-server\u002FCargo.toml\n```\n\n```bash\n# Deploy with extra Docker build args\ncargo gears deploy --app myapp --env dev --args BUILDER_FLAGS=\"--features metrics\"\n```\n\n### `lint`\n\nRun workspace linting helpers from the selected workspace directory.\n\nSynopsis:\n\n```bash\ncargo gears lint [--app \u003CAPP>] [--env \u003CENV>] [--manifest \u003CGears.toml>] [-p \u003CPATH>] [--all] [--fmt] [--clippy] [--strict] [--dylint] [-P \u003CSPEC>]... [--gear \u003CNAME>]... [--include-dependents] [-F \u003CFEATURES>]... [--all-features | --no-default-features] [--locked] [--list] [--pin-dylint]\n```\n\nArguments:\n\n- **[`-p, --path \u003CPATH>`]** Optional workspace directory used to resolve relative manifest paths\n- **[`--manifest \u003CPATH>`]** Manifest file, defaults to `Gears.toml`\n- **[`--app \u003CAPP> --env \u003CENV>`]** Manifest app\u002Fenvironment selection (inferred from manifest if omitted)\n- **[`--all`]** Runs all available lint suites instead of the selected manifest lint policy\n- **[`--fmt`]** Runs `cargo fmt --check` for the selected package scope; with no `-P\u002F--package` or `--gear`, it uses\n  `--all`. If passed by itself, it runs only formatting checks.\n- **[`--clippy`]** Runs workspace Clippy checks; if passed by itself, it runs only Clippy\n- **[`--strict`]** Turns Clippy warnings into errors; valid only when Clippy is selected explicitly or through `--all`\n- **[`--dylint`]** Runs `cargo dylint --all` against the workspace rooted at the current or selected directory, which\n  loads every library declared in `workspace.metadata.dylint.libraries`. Fails unless `cargo-gears-lints` is declared\n  there and pinned to the CLI's own release tag (see `--pin-dylint`)\n- **[`-P, --package \u003CSPEC>`]** Restricts formatting, Clippy, and Dylint to the given workspace package(s); repeatable.\n  Supports Cargo package ID specifications and package-name globs such as `cf-gears-*`. When omitted together with\n  `--gear`, the whole workspace is linted.\n- **[`--gear \u003CNAME>`]** Restricts formatting, Clippy, and Dylint to the local workspace package(s) belonging to a\n  discovered gear; repeatable. Includes the conventional nested gear SDK package. Use `cargo gears ls gears --local` to\n  list valid names. Can be combined with `-P\u002F--package`.\n- **[`--include-dependents`]** Expands the `-P\u002F--package` and `--gear` selection to also include every workspace crate\n  that (transitively) depends on the selected package(s) — the reverse-dependency closure. Requires at least one package\n  or gear selection; otherwise the command fails.\n- **[`-F, --features \u003CFEATURES>`]** Enables Cargo features for Clippy and Dylint. Accepts comma-separated values and is\n  repeatable. Default features remain enabled unless `--no-default-features` is also passed.\n- **[`--all-features`]** Enables every Cargo feature. Conflicts with `--features` and `--no-default-features`.\n- **[`--no-default-features`]** Disables Cargo default features. May be combined with `--features`.\n- **[`--locked`]** Requires `Cargo.lock` to be up to date; passed to Clippy and Dylint's `cargo check`.\n- **[`--list`]** Lists available lint rules instead of running them. When combined with `--dylint`, lists only the\n  dylint rules. Does not require a manifest or workspace path.\n- **[`--pin-dylint`]** Writes or updates the `cargo-gears-lints` entry in `workspace.metadata.dylint.libraries` so it is\n  pinned to the CLI's own release tag, then exits without running lints. Edits `dylint.toml` when it declares at least\n  one library, otherwise the workspace `Cargo.toml`; an empty `libraries = []` does not count. Fails without editing\n  when both files declare libraries, which Dylint rejects. Other libraries and keys are kept. Conflicts with `--all`, `--fmt`,\n  `--clippy`, `--strict`, `--dylint`, and `--list`.\n\nBehavior:\n\n- **[path activation]** If `-p\u002F--path` is provided, relative manifest paths are resolved from that workspace directory\n- **[manifest mode]** Reads lint policy from the selected `Gears.toml` app\u002Fenvironment and runs from the resolved\n  manifest workspace root\n- **[default lint selection]** With no explicit lint-selection flags, `lint` runs the selected manifest lint policy\n- **[explicit selection disables default all]** Passing `--fmt`, `--clippy`, and\u002For `--dylint` opts into just those\n  requested lint suites unless `--all` is also provided\n- **[package-scoped formatting]** `--fmt` runs `cargo fmt --check --all` when no package or gear is selected. With an\n  explicit package\u002Fgear scope, it passes each effective package as `--package \u003CSPEC>`. `--include-dependents` expands\n  this scope before formatting, matching Clippy and Dylint.\n- **[workspace Clippy]** Clippy runs as `cargo clippy --workspace --all-targets`, or as\n  `cargo clippy --package \u003CSPEC> ... --all-targets` when one or more `-P\u002F--package` flags are supplied. Cargo feature\n  flags are appended when selected. Without feature flags, each package's default features are used. Manifest\n  `feature-set-test` remains reserved for future feature-matrix linting and is not currently applied.\n- **[strict scope]** `--strict` is rejected unless Clippy is active through `--clippy` or `--all`\n- **[workspace-scoped dylint]** `cargo dylint` runs from the resolved workspace root with\n  `--manifest-path \u003Croot>\u002FCargo.toml`, so `-p\u002F--path` is the way to lint another workspace without manually changing\n  directories, and a workspace whose metadata cannot be loaded fails the run instead of linting nothing. It runs with\n  `--workspace`, or with `--package \u003CSPEC>` for\n  each effective package when a package\u002Fgear scope is selected; features, skips, and `--locked` are forwarded to its\n  `cargo check`.\n- **[pinned dylint lints]** Before running Dylint, the CLI checks the workspace's Dylint libraries (in `dylint.toml`\n  when it declares at least one, otherwise in the workspace `Cargo.toml`; declaring libraries in both is an error) for exactly one `cargo-gears-lints` entry. A git entry\n  must point at `https:\u002F\u002Fgithub.com\u002Fconstructorfabric\u002Fcargo-gears` with `tag = \"cargo-gears-v\u003CCLI version>\"`,\n  `pattern = \"crates\u002Fcargo-gears-lints\"`, and no `branch` or `rev`. A `path` entry to a local `cargo-gears-lints`\n  checkout is accepted with a warning, for developing the lints. A missing, duplicated, or differently pinned entry\n  fails the run and points at `--pin-dylint`.\n- **[external dylint lints]** Any other library in `workspace.metadata.dylint.libraries` runs together with\n  `cargo-gears-lints`, so third-party or in-house Dylint lints need only a standard Dylint entry\n- **[package-scoped linting]** Passing one or more `-P\u002F--package \u003CSPEC>` flags restricts formatting, Clippy, and Dylint\n  to those packages instead of the whole workspace; the flag is repeatable and supports Cargo package ID specifications\n  plus package-name globs. A bare `*` intentionally selects every workspace package while remaining an explicit scope.\n- **[gear-scoped linting]** Each `--gear \u003CNAME>` is resolved through local workspace gear discovery to its annotated\n  package and conventional nested SDK workspace package, when present. Gear-derived packages are merged and\n  de-duplicated with explicit `-P\u002F--package` selections. System registry gears that are not local workspace members\n  cannot be selected.\n- **[dependent expansion]** With `--include-dependents`, the selected packages are expanded to their reverse-dependency\n  closure (the seed packages plus every workspace crate that depends on them) before formatting, Clippy, and Dylint run,\n  so a change to a crate can be linted together with everything it may break. Unknown package names are rejected.\n- **[feature-scoped linting]** `--features`, `--all-features`, and `--no-default-features` use Cargo's standard feature\n  semantics and apply to both Clippy and Dylint. Package-qualified features such as `crate-name\u002Ffeature-name` can be used\n  when linting multiple workspace packages.\n- **[manifest dylint skips]** Manifest `lint.dylint.skip` entries are passed to Dylint as allowed rustc lints, so\n  listed rules are ignored for that lint run. They apply to external libraries' lints as well. They are passed both\n  as `build.rustflags` and appended to `DYLINT_RUSTFLAGS`, so they still hold when `RUSTFLAGS` is set, even to\n  `-D warnings`.\n- **[tool bootstrap]** Before running Dylint, the CLI installs `cargo-dylint` and `dylint-link` with\n  `cargo install --locked` if either is missing. Dylint itself fetches and builds the declared libraries on the first\n  run, with each library's pinned toolchain, so it needs access to GitHub.\n- **[list mode]** `--list` prints available lints grouped by category and exits without running any checks.\n  `--list --dylint` prints only the `cargo-gears-lints` rules. `--list` alone prints all lint suites plus those rules.\n  Lints from other Dylint libraries are not listed.\n\nExamples:\n\n```bash\ncargo gears lint --app app1 --env dev\n```\n\n```bash\ncargo gears lint --app app1 --env dev --clippy --strict\n```\n\n```bash\ncargo gears lint --app app1 --env dev --fmt\n```\n\n```bash\ncargo gears lint --app app1 --env dev --fmt --gear file-parser\n```\n\n```bash\ncargo gears lint --app app1 --env dev --dylint\n```\n\n```bash\ncargo gears lint -p \u002Ftmp\u002Fcf-demo --app app1 --env dev --dylint\n```\n\n```bash\ncargo gears lint --app app1 --env dev --clippy --package cf-gears-file-parser\n```\n\n```bash\ncargo gears lint --app app1 --env dev --dylint -P cf-gears-file-parser -P cf-gears-file-parser-sdk\n```\n\n```bash\ncargo gears lint --app app1 --env dev --dylint --gear file-parser\n```\n\n```bash\ncargo gears lint --app app1 --env dev --clippy --gear file-parser --include-dependents\n```\n\n```bash\ncargo gears lint --app app1 --env dev --clippy -P shared-utils --gear file-parser\n```\n\n```bash\ncargo gears lint --app app1 --env dev --clippy -P cf-gears-file-parser --include-dependents\n```\n\n```bash\ncargo gears lint --app app1 --env dev --clippy -P cf-gears-file-parser --features json,otel\n```\n\n```bash\ncargo gears lint --app app1 --env dev --dylint -P cf-gears-file-parser --no-default-features -F sqlite\n```\n\n```bash\ncargo gears lint --app app1 --env dev --clippy -P cf-gears-file-parser --all-features\n```\n\n```bash\ncargo gears lint --list --dylint\n```\n\n```bash\ncargo gears lint --app app1 --env dev --pin-dylint\n```\n\n```bash\ncargo gears lint --list\n```\n\nWorkspace `Cargo.toml` pin written by `--pin-dylint`, next to an external library:\n\n```toml\n[workspace.metadata.dylint]\nlibraries = [\n    { git = \"https:\u002F\u002Fgithub.com\u002Fconstructorfabric\u002Fcargo-gears\", tag = \"cargo-gears-v\u003CCLI version>\", pattern = \"crates\u002Fcargo-gears-lints\" },\n    { git = \"https:\u002F\u002Fgithub.com\u002Fexample\u002Fmy-lints\", tag = \"v1.0.0\" },\n]\n```\n\nManifest Dylint skip example:\n\n```toml\n[apps.app1.dev.lint]\ndylint = { enabled = true, skip = [\"de0301_no_infra_in_domain\"] }\n```\n\n### `ls`\n\nInspect workspace gears, system gears, templates, features, dependencies, and packages.\n\n#### `ls gears`\n\nList all gears — both system-registry and workspace-discovered — in a single unified view.\n\nSynopsis:\n\n```bash\ncargo gears ls gears [-p \u003CPATH>] [--system] [--local] [--verbose] [--registry crates.io] [--format table|json|list|cargo-flags] [--filter \u003CREGEX>] [--dirs \u003CDIR,...>] [--include-rdeps]\n```\n\nArguments:\n\n- **[`-p, --path \u003CPATH>`]** Optional workspace directory used for local gear discovery\n- **[`--system`]** Only print built-in system registry gears\n- **[`--local`]** Only print workspace-discovered gears\n- **[`-v, --verbose`]** Show full metadata for both system and local gears (fetches registry metadata for system\n  gears)\n- **[`--registry \u003CREGISTRY>`]** Registry to query for system-crate metadata; defaults to `crates.io`\n- **[`-f, --format \u003CFORMAT>`]** Output format; defaults to `json`. Supported values: `table`, `json`, `list`,\n  `cargo-flags`\n- **[`--filter \u003CREGEX>`]** Filter gear names by regex pattern. Applied before `--include-rdeps`\n- **[`--dirs \u003CDIR,...>`]** Comma-separated directory paths (relative to workspace root) to restrict results\n  to gears whose crate directory is under one of the given directories. Applied before `--include-rdeps`\n- **[`--include-rdeps`]** After filtering\u002Fscoping, expand the result set with every workspace crate that\n  transitively depends on the matched gears (reverse-dependency closure)\n\nBehavior:\n\n- **[combined output]** Prints system gears first, then workspace gears, separated by a blank line\n- **[filtered output]** `--system` prints only system gears; `--local` prints only workspace gears; passing both is\n  equivalent to the default combined output\n- **[json output]** `--format json` prints a `modules` array with each gear's `source` (`system` or `local`), static\n  metadata, and verbose metadata when `--verbose` is enabled\n- **[system usage marker]** System gears include `used: yes\u002Fno` in table output and `used: true\u002Ffalse` in JSON output,\n  based on whether `Gears.toml` references the system gear as a remote module or the workspace has a discovered gear\n  with the same name\n- **[config-independent]** Does not require a `-c\u002F--config` file\n- **[workspace scanning]** Local output runs `cargo metadata --no-deps` and discovers crates with a gears annotation\n  (`#[toolkit::gear(...)]`) in any `src\u002F**\u002F*.rs` file\n- **[system registry]** System output uses the compiled-in registry, and `--verbose` fetches crate metadata from the\n  selected registry\n- **[cargo-flags format]** `--format cargo-flags` prints `-p \u003Cpackage>` flags suitable for passing to Cargo commands\n- **[filter → scope → rdeps pipeline]** Filters and scope directories are applied first to narrow the initial gear\n  set; `--include-rdeps` then expands that set with reverse dependents\n\nExamples:\n\n```bash\ncargo gears ls gears\n```\n\n```bash\ncargo gears ls gears -p \u002Ftmp\u002Fcf-demo --verbose\n```\n\n```bash\ncargo gears ls gears --local\n```\n\n```bash\ncargo gears ls gears --system --verbose\n```\n\n```bash\ncargo gears ls gears --local --filter 'api-.*' --include-rdeps\n```\n\n```bash\ncargo gears ls gears --local --dirs gears\u002Fapi -f cargo-flags\n```\n\n#### `ls templates`\n\nList all available generation templates.\n\nSynopsis:\n\n```bash\ncargo gears ls templates [-p \u003CPATH>]\n```\n\nArguments:\n\n- **[`-p, --path \u003CPATH>`]** Optional workspace directory used to find `Gears.toml`; defaults to `.`\n\nBehavior:\n\n- **[built-in templates]** Always prints built-in workspace and gear templates with their names and descriptions\n- **[manifest templates]** Also prints manifest `templates.workspace` and `templates.gear` entries when `Gears.toml`\n  exists at the selected path\n- **[config-independent]** Does not require a `-c\u002F--config` file\n\nExamples:\n\n```bash\ncargo gears ls templates\n```\n\n```bash\ncargo gears ls templates -p \u002Ftmp\u002Fcf-demo\n```\n\n#### `ls features`\n\nList all feature names defined in a Cargo.toml's `[features]` section.\n\nSynopsis:\n\n```bash\ncargo gears ls features --manifest \u003CPATH> [-f \u003CFORMAT>]\n```\n\nArguments:\n\n- **[`--manifest \u003CPATH>`]** Path to the Cargo.toml to inspect\n- **[`-f, --format \u003CFORMAT>`]** Output format; defaults to `list`. Supported values: `list`, `table`, `json`,\n  `cargo-flags`\n\nBehavior:\n\n- **[sorted output]** Features are listed in lexicographic order\n- **[cargo-flags format]** `--format cargo-flags` prints features as a comma-separated list suitable for\n  `--features \u003CLIST>`\n\nExamples:\n\n```bash\ncargo gears ls features --manifest gears\u002Fapi-gateway\u002FCargo.toml\n```\n\n```bash\ncargo gears ls features --manifest Cargo.toml -f json\n```\n\n#### `ls deps`\n\nList dependency names from a Cargo.toml's `[dependencies]` section.\n\nSynopsis:\n\n```bash\ncargo gears ls deps --manifest \u003CPATH> [--non-optional] [-f \u003CFORMAT>]\n```\n\nArguments:\n\n- **[`--manifest \u003CPATH>`]** Path to the Cargo.toml to inspect\n- **[`--non-optional`]** Only list non-optional (always-linked) dependencies\n- **[`-f, --format \u003CFORMAT>`]** Output format; defaults to `list`. Supported values: `list`, `table`, `json`,\n  `cargo-flags`\n\nBehavior:\n\n- **[sorted output]** Dependencies are listed in lexicographic order\n- **[package field]** Uses the `package` field from the dependency table when present, otherwise uses the key name\n- **[cargo-flags format]** `--format cargo-flags` prints `-p \u003Cpackage>` flags\n\nExamples:\n\n```bash\ncargo gears ls deps --manifest gears\u002Fapi-gateway\u002FCargo.toml\n```\n\n```bash\ncargo gears ls deps --manifest Cargo.toml --non-optional -f json\n```\n\n#### `ls packages`\n\nList all Cargo packages (crates) in the workspace or under specific directories, with optional\nfiltering and reverse-dependency expansion.\n\nSynopsis:\n\n```bash\ncargo gears ls packages [-p \u003CPATH>] [--dirs \u003CDIR,...>] [--filter \u003CREGEX>] [--include-rdeps] [-f \u003CFORMAT>]\n```\n\nArguments:\n\n- **[`-p, --path \u003CPATH>`]** Optional workspace directory\n- **[`--dirs \u003CDIR,...>`]** Comma-separated directory paths to restrict discovery to crates under those directories\n  (relative to workspace root)\n- **[`--filter \u003CREGEX>`]** Filter package names by regex pattern. Applied before `--include-rdeps`\n- **[`--include-rdeps`]** After filtering\u002Fscoping, expand the result set with every workspace crate that transitively\n  depends on the matched packages (reverse-dependency closure)\n- **[`-f, --format \u003CFORMAT>`]** Output format; defaults to `list`. Supported values: `list`, `table`, `json`,\n  `cargo-flags`\n\nBehavior:\n\n- **[all packages by default]** Without `--dirs`, lists all workspace packages\n- **[dirs discovery]** With `--dirs`, only packages whose manifest path is inside one of the given directories\n  are included\n- **[scope → filter → rdeps pipeline]** Scoping is applied first, then filters, then `--include-rdeps` expands\n  the filtered set\n- **[cargo-flags format]** `--format cargo-flags` prints `-p \u003Cpackage>` flags\n\nExamples:\n\n```bash\ncargo gears ls packages -p \u002Ftmp\u002Fcf-demo\n```\n\n```bash\ncargo gears ls packages -p \u002Ftmp\u002Fcf-demo --dirs gears\u002Fapi\n```\n\n```bash\ncargo gears ls packages --filter 'cf-gears-.*' --include-rdeps\n```\n\n```bash\ncargo gears ls packages --filter 'api' --include-rdeps -f cargo-flags\n```\n\n### `test`\n\nOrchestrates manifest-driven Rust tests with either `cargo test` or the in-process nextest runner.\n\nSynopsis:\n\n```bash\ncargo gears test [-p \u003CPATH>] [--manifest \u003CPATH>] [--app \u003CAPP>] [--env \u003CENV>] [--runner \u003Ccargo|nextest>] [--module \u003CNAME>] [--include-dependents] [--coverage] [--locked]\n```\n\nArguments:\n\n- **[`--runner \u003Ccargo|nextest>`]** Overrides the manifest `test.runner`; defaults to `nextest` that it's integrated in the tool\n- **[`--module \u003CNAME>`]** Limits tests to a module\u002Fpackage. When manifest `test.feature-set` contains that module, its feature matrix is used.\n- **[`--include-dependents`]** Also tests every workspace crate that (transitively) depends on `--module` — the reverse-dependency closure. Requires `--module`; has no effect on its own.\n- **[`--coverage`]** Runs coverage with `cargo llvm-cov` using the selected or manifest test runner\n- **[`--locked`]** Require `Cargo.lock` is up to date; passed as `--locked` to `cargo test`, nextest build, and `cargo llvm-cov`\n\nBehavior:\n\n- **[manifest selection]** Resolves the selected app\u002Fenvironment and passes its config path to tests via `GEARS_CONFIG`\n- **[cargo runner]** Runs `cargo test` with `--workspace` by default, or `-p \u003Cpackage>` for module-specific runs\n- **[nextest runner]** Builds test binaries with Cargo JSON messages, then executes them through the embedded nextest runner from `cargo-nextest`\n- **[coverage runner]** Cleans llvm-cov artifacts once, executes every selected module\u002Ffeature-set run, then generates one aggregate report across all collected profiles\n- **[cargo coverage]** With `cargo`, runs each selected module\u002Ffeature-set through `cargo llvm-cov --no-report --no-clean`, then reports once with `cargo llvm-cov report`\n- **[nextest coverage]** With `nextest`, uses `cargo llvm-cov show-env`, runs the embedded nextest runner under the coverage environment for every selected module\u002Ffeature-set, then reports once with `cargo llvm-cov report`\n- **[feature-set policy]** Expands manifest `test.feature-set` module entries by `mode`: `all-features` uses `--all-features`, `no-default-features` uses `--no-default-features`, `default-features` uses Cargo defaults, and `features` uses `--no-default-features --features \u003CLIST>`\n- **[dependent expansion]** With `--module \u003CNAME> --include-dependents`, the resolved package is expanded to its reverse-dependency closure and each additional dependent crate is added as a default-feature test run (de-duplicated against runs already produced by the feature-set policy)\n\n## Practical End-to-End Flows\n\n### Create a workspace and run it\n\n```bash\ncargo gears {new|generate workspace} \u002Ftmp\u002Fcf-demo\ncargo gears generate module --template background-worker -p \u002Ftmp\u002Fcf-demo\ncargo gears generate config --template dev --app app1 --env dev -p \u002Ftmp\u002Fcf-demo\ncargo gears config mod add background-worker -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fapp1-dev.yml\ncargo gears run -p \u002Ftmp\u002Fcf-demo --app app1 --env dev\n```\n\n### Add a module and wire a shared DB server\n\n```bash\ncargo gears generate module --template api-db-handler -p \u002Ftmp\u002Fcf-demo\ncargo gears config db add primary -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fquickstart.yml --engine postgres --host localhost --port 5432 --user app --password '${DB_PASSWORD}' --dbname appdb\ncargo gears config mod add api-db-handler -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fquickstart.yml\ncargo gears config mod db add api-db-handler -p \u002Ftmp\u002Fcf-demo -c \u002Ftmp\u002Fcf-demo\u002Fconfig\u002Fquickstart.yml --server primary\ncargo gears run -p \u002Ftmp\u002Fcf-demo --app app1 --env dev --watch\n```\n\n### Inspect source for a dependency\n\n```bash\ncargo gears src --verbose tokio::sync\n```\n\n## Important Caveats\n\n- **[`-c\u002F--config` is mandatory]** For `config ...` and `deploy`; `build` and `run` use `Gears.toml` instead\n- **[generated servers expect `GEARS_CONFIG`]** `cargo gears run` sets it for you, but manual execution of\n  generated project directory or its compiled binary must provide it explicitly\n- **[`lint --dylint` needs the lints pinned]** Run `cargo gears lint --pin-dylint` after creating a workspace by\n  other means than `generate workspace`, and after every CLI upgrade\n- **[`lint --strict` depends on Clippy]** Use it together with `--clippy` or `--all`\n- **[`test` is not ready]** It is part of the CLI surface but currently panics at runtime\n- **[`tools` can mutate your system]** It may install `rustup` or rustup components\n- **[`src --registry`]** Only `crates.io` is supported\n- **[`src`]** Accepts a single query, and that query is only optional when `--clean` is used by itself\n- **[`config mod add`]** Remote modules require both `--package` and `--module-version`\n- **[`config mod db add`]** The module must already exist in config\n\n## Quick Reference\n\n```bash\ncargo gears {new|generate workspace} \u003Cpath> [--template \u003Ctemplate>] [--name \u003Cname>]\ncargo gears generate module --template \u003Cbackground-worker|api-db-handler|api-gateway> [--name \u003Cname>] [-p \u003Cworkspace>]\ncargo gears generate config --template \u003Cdev|prod|db> [--app \u003Capp>] [--env \u003Cenv>] [--name \u003Cname>] [-p \u003Cworkspace>]\n\ncargo gears config mod add \u003Cmodule> [-p \u003Cworkspace>] -c \u003Cconfig>\ncargo gears config mod rm \u003Cmodule> [-p \u003Cworkspace>] -c \u003Cconfig>\ncargo gears config mod db add \u003Cmodule> [-p \u003Cworkspace>] -c \u003Cconfig> ...\ncargo gears config mod db edit \u003Cmodule> [-p \u003Cworkspace>] -c \u003Cconfig> ...\ncargo gears config mod db rm \u003Cmodule> [-p \u003Cworkspace>] -c \u003Cconfig>\n\ncargo gears config db add \u003Cname> [-p \u003Cworkspace>] -c \u003Cconfig> ...\ncargo gears config db edit \u003Cname> [-p \u003Cworkspace>] -c \u003Cconfig> ...\ncargo gears config db rm \u003Cname> [-p \u003Cworkspace>] -c \u003Cconfig>\n\n\ncargo gears ls gears [-p \u003Cworkspace>] [--system] [--local] [--verbose] [--registry crates.io] [-f table|json|list|cargo-flags] [--filter \u003Cregex>] [--dirs \u003Cdirs>] [--include-rdeps]\ncargo gears ls templates [-p \u003Cworkspace>]\ncargo gears ls features --manifest \u003CCargo.toml> [-f list|json|cargo-flags]\ncargo gears ls deps --manifest \u003CCargo.toml> [--non-optional] [--dev] [--build] [-f list|json|cargo-flags]\ncargo gears ls packages [-p \u003Cworkspace>] [--dirs \u003Cdirs>] [--filter \u003Cregex>] [--include-rdeps] [-f list|json|cargo-flags]\ncargo gears ls targets --manifest \u003CCargo.toml> [-f list|json|cargo-flags]\n\ncargo gears src [-p \u003Cpath>] [--version \u003Cversion>] [--clean] [\u003Cquery>]\ncargo gears lint [-p \u003Cworkspace>] [--app \u003Capp>] [--env \u003Cenv>] [--manifest \u003CGears.toml>] [--all] [--fmt] [--clippy] [--strict] [--dylint] [-P \u003Cspec>]... [--gear \u003Cname>]... [--include-dependents] [-F \u003Cfeatures>]... [--all-features | --no-default-features] [--locked] [--list] [--pin-dylint]\ncargo gears tools --all\ncargo gears tools check-version \u003Ctool> '\u003Crequirement>'\ncargo gears run [-p \u003Cworkspace>] [--app \u003Capp>] [--env \u003Cenv>] [--manifest \u003CGears.toml>] [--name \u003Cname>] [--watch] [--locked]\ncargo gears build [-p \u003Cworkspace>] [--app \u003Capp>] [--env \u003Cenv>] [--manifest \u003CGears.toml>] [--name \u003Cname>] [--locked]\ncargo gears deploy [--app \u003Capp>] [--env \u003Cenv>] [-p \u003Cworkspace>] [-t \u003Ctag>] [-m \u003CCargo.toml>] [-c \u003Cconfig>] [--debug] [--args \u003CKEY=VALUE>]...\n```\n",{"name":5,"description":7},"main","13a73e9a00d41e4bfdf40e2374c7fc9e4656a6bc","crates\u002Fcargo-gears-core\u002Fshared",7,"https:\u002F\u002Fgithub.com\u002Fconstructorfabric\u002Fcargo-gears","https:\u002F\u002Fgithub.com\u002Fconstructorfabric","https:\u002F\u002Fconstructorfabric.org","A unified fabric that automates the entire XaaS software development lifecycle  from planning to building to running services in prod","2026-10-29 22:09:42",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add constructorfabric\u002Fcargo-gears --skill gears",{"tool":39,"command":40},"bunx","bunx skills add constructorfabric\u002Fcargo-gears --skill gears",{"tool":42,"command":43},"pnpm","pnpm dlx skills add constructorfabric\u002Fcargo-gears --skill gears","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fconstructorfabric\u002Fcargo-gears\u002Fblob\u002Fmain\u002Fcrates\u002Fcargo-gears-core\u002Fshared\u002FSKILL.md",true,[47,53],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},".dockerignore","OTHER","其他",47,"https:\u002F\u002Fgithub.com\u002Fconstructorfabric\u002Fcargo-gears\u002Fblob\u002Fmain\u002Fcrates\u002Fcargo-gears-core\u002Fshared\u002F.dockerignore",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"Dockerfile",1362,"https:\u002F\u002Fgithub.com\u002Fconstructorfabric\u002Fcargo-gears\u002Fblob\u002Fmain\u002Fcrates\u002Fcargo-gears-core\u002Fshared\u002FDockerfile",[58],{"skillNo":59,"name":60,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":61,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M74EJ17FX3VEKA7KMXA63Y9Y","cargo-gears","https:\u002F\u002Fgithub.com\u002Fconstructorfabric\u002Fcargo-gears\u002Fblob\u002Fmain\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fconstructorfabric\u002Fcargo-gears\u002Fblob\u002Fmain\u002FSKILL.md",[],[]]