inline-enum-type-name-override-custom-commands
How to author custom commands for the inline-enum-type-name-override CLI using the co-generated SDK.
适合你，如果需要扩展该CLI的命令集
npx oh-my-skill add fern-api/fern/inline-enum-type-name-override-custom-commandscurl -fsSL https://oh-my-skill.com/install.sh | bash -s -- fern-api/fern/inline-enum-type-name-override-custom-commandsnpx oh-my-skill verify fern-api/fern/inline-enum-type-name-override-custom-commands怎么用
商店整理自技能原文 · 版本 aeafcf1 · 表述以原文为准装上后，Claude 会教你为 inline-enum-type-name-override CLI 编写自定义命令。你只需编辑 custom.rs 文件，注册新命令（如 load），然后构建运行。CLI 会自动处理认证、重试等。
当你想扩展 CLI 功能、添加自定义命令时触发。你问如何创建命令，或请求编写特定命令时启动。
技能原文 SKILL.md
Custom Commands for inline-enum-type-name-override
Overview
The inline-enum-type-name-override CLI supports user-authored custom commands that are compiled into the binary alongside the auto-generated API commands. Custom commands get a fully-wired SDK client that inherits the CLI's auth, retries, TLS, base URL, and global headers — zero configuration required.
Architecture
cli/inline-enum-type-name-override/custom.rs ← Your command handlers (protected by .fernignore) cli/inline-enum-type-name-override/sdk.rs ← Generated bridge: client() + block_on() cli/inline-enum-type-name-override/main.rs ← Generated entrypoint (calls custom::register) inline-enum-type-name-override-sdk/ ← Co-generated typed SDK crate inline-enum-type-name-override-types/ ← Co-generated typed model crate
Adding a Custom Command
1. Edit cli/inline-enum-type-name-override/custom.rs
This file is protected by .fernignore — fern generate will never overwrite it. Register commands in the register() function:
use inline_enum_type_name_override_sdk::api::*;
pub fn register(app: CliApp) -> CliApp {
let app = app.command(
clap::Command::new("load")
.about("Run reporting load")
,
|matches, ctx| {
let client = super::sdk::client(ctx);
let result = super::sdk::block_on(
client.reporting.load(),
)?;
println!("{}", serde_json::to_string_pretty(&result).unwrap());
Ok(())
},
);
app
}
Then build and test:
cargo build inline-enum-type-name-override load
2. Available SDK Clients
The super::sdk::client(ctx) call returns a inline_enum_type_name_override_sdk::api::Client with the following sub-clients:
| Field | Type | Description | |-------|------|-------------| | client.reporting | inline_enum_type_name_override_sdk::api::ReportingClient | reporting operations |
3. Key Patterns
Get the SDK client (execution-sharing, fully authenticated):
let client = super::sdk::client(ctx);
Run an async SDK call from a sync handler:
let result = super::sdk::block_on(
client.some_resource.some_method(args),
)?;
Use typed models for request/response serialization:
use inline_enum_type_name_override_sdk::api::*;
Regeneration Safety
| File | Regenerated? | Notes | |------|-------------|-------| | cli/inline-enum-type-name-override/custom.rs | No | Protected by .fernignore | | cli/inline-enum-type-name-override/sdk.rs | Yes | Bridges AppContext → SDK client | | cli/inline-enum-type-name-override/main.rs | Yes | Calls custom::register(app) | | inline-enum-type-name-override-sdk/ | Yes | Co-generated typed SDK crate | | inline-enum-type-name-override-types/ | Yes | Co-generated typed models |
After running fern generate, your custom.rs is preserved. All generated code (SDK, types, glue, main.rs) is updated to match the latest API spec. If the SDK surface changes (renamed methods, new sub-clients), update your custom.rs to match.
Build & Test
# Build the CLI (includes custom commands) cargo build # Run your custom command inline-enum-type-name-override <your-command> [args] # Run with verbose output for debugging RUST_LOG=debug inline-enum-type-name-override <your-command> [args]