nullable-allof-extends-test-custom-commands
How to author custom commands for the nullable-allof-extends-test CLI using the co-generated SDK.
For you if you use the nullable-allof-extends-test CLI and need to extend its functionality.
npx oh-my-skill add fern-api/fern/nullable-allof-extends-test-custom-commandscurl -fsSL https://oh-my-skill.com/install.sh | bash -s -- fern-api/fern/nullable-allof-extends-test-custom-commandsnpx oh-my-skill verify fern-api/fern/nullable-allof-extends-test-custom-commands怎么用
商店整理自技能原文 · 版本 aeafcf1 · 表述以原文为准安装后,Claude 会指导你为 nullable-allof-extends-test CLI 编写自定义命令,包括在 custom.rs 中注册命令、使用 SDK 客户端和调用异步方法等步骤。
当你想为 nullable-allof-extends-test CLI 添加自定义命令,或询问如何编写自定义命令时,Claude 会接管并提供指导。
技能原文 SKILL.md
Custom Commands for nullable-allof-extends-test
Overview
The nullable-allof-extends-test 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/nullable-allof-extends-test/custom.rs ← Your command handlers (protected by .fernignore) cli/nullable-allof-extends-test/sdk.rs ← Generated bridge: client() + block_on() cli/nullable-allof-extends-test/main.rs ← Generated entrypoint (calls custom::register) nullable-allof-extends-test-sdk/ ← Co-generated typed SDK crate nullable-allof-extends-test-types/ ← Co-generated typed model crate
Adding a Custom Command
1. Edit cli/nullable-allof-extends-test/custom.rs
This file is protected by .fernignore — fern generate will never overwrite it. Register commands in the register() function:
use nullable_allof_extends_test_sdk::api::*;
pub fn register(app: CliApp) -> CliApp {
let app = app.command(
clap::Command::new("my-command")
.about("Description of your command")
.arg(clap::Arg::new("id").required(true)),
|matches, ctx| {
let id = matches.get_one::<String>("id").unwrap();
let client = super::sdk::client(ctx);
let result = super::sdk::block_on(
client.resource.get(id),
)?;
println!("{}", serde_json::to_string_pretty(&result).unwrap());
Ok(())
},
);
app
}
2. Available SDK Clients
The super::sdk::client(ctx) call returns a nullable_allof_extends_test_sdk::api::Client with the following sub-clients:
(Sub-clients are derived from the API spec at generation time.)
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 nullable_allof_extends_test_sdk::api::*;
Regeneration Safety
| File | Regenerated? | Notes | |------|-------------|-------| | cli/nullable-allof-extends-test/custom.rs | No | Protected by .fernignore | | cli/nullable-allof-extends-test/sdk.rs | Yes | Bridges AppContext → SDK client | | cli/nullable-allof-extends-test/main.rs | Yes | Calls custom::register(app) | | nullable-allof-extends-test-sdk/ | Yes | Co-generated typed SDK crate | | nullable-allof-extends-test-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 nullable-allof-extends-test <your-command> [args] # Run with verbose output for debugging RUST_LOG=debug nullable-allof-extends-test <your-command> [args]