allof-composition-custom-commands
How to author custom commands for the allof-composition CLI using the co-generated SDK.
适合你,如果需要在 allof-composition CLI 中添加自定命令。
npx oh-my-skill add fern-api/fern/allof-composition-custom-commandscurl -fsSL https://oh-my-skill.com/install.sh | bash -s -- fern-api/fern/allof-composition-custom-commandsnpx oh-my-skill verify fern-api/fern/allof-composition-custom-commands怎么用
商店整理自技能原文 · 版本 aeafcf1 · 表述以原文为准安装此技能后,Claude能够指导你如何为 allof-composition CLI 编写自定义命令,包括注册命令、获取 SDK 客户端、执行异步调用等,并给出 Rust 代码示例。
当你询问如何编写 allof-composition 的自定义命令,或要求添加新命令时触发。
技能原文 SKILL.md
Custom Commands for allof-composition
Overview
The allof-composition 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/allof-composition/custom.rs ← Your command handlers (protected by .fernignore) cli/allof-composition/sdk.rs ← Generated bridge: client() + block_on() cli/allof-composition/main.rs ← Generated entrypoint (calls custom::register) allof-composition-sdk/ ← Co-generated typed SDK crate allof-composition-types/ ← Co-generated typed model crate
Adding a Custom Command
1. Edit cli/allof-composition/custom.rs
This file is protected by .fernignore — fern generate will never overwrite it. Register commands in the register() function:
use allof_composition_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 allof_composition_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 allof_composition_sdk::api::*;
Regeneration Safety
| File | Regenerated? | Notes | |------|-------------|-------| | cli/allof-composition/custom.rs | No | Protected by .fernignore | | cli/allof-composition/sdk.rs | Yes | Bridges AppContext → SDK client | | cli/allof-composition/main.rs | Yes | Calls custom::register(app) | | allof-composition-sdk/ | Yes | Co-generated typed SDK crate | | allof-composition-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 allof-composition <your-command> [args] # Run with verbose output for debugging RUST_LOG=debug allof-composition <your-command> [args]