メニュー
Add a CLI flag to shipctl end-to-end — argument parser definition, help text, shell completion scripts, documentation, and tests. Use when adding a new option or flag, when extending an existing subcommand, or when asked to "add a --flag-name option".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Close implementation loops with target-bound independent evidence and a portable proof receipt. Use when an agent changes a real system and must earn a completion claim that survives the session.
First fixture skill for skdd add tests. Use when testing drop installation.
Second fixture skill for skdd add tests. Use when testing multi-skill drops.
Safely backfill historical data for a pipeline stage — scope the date range, run a dry-run, execute in chunks to avoid overwhelming the database, and verify row counts after each chunk. Use when historical data is missing, when a pipeline stage is added retroactively, or when asked to "backfill the {stage} table from {start_date}".
Add or extend data validation checks in the pipeline when data quality issues are detected — null-percentage thresholds, value ranges, referential integrity, and row-count sanity checks. Use when a pipeline breaks on bad data, when onboarding a new dataset, or when asked to "add a quality check for {column}".
Onboard a new raw dataset into the data platform — sniff the schema, generate a profiling notebook, create the ingestion job, and add an entry to the data dictionary. Use when adding a new data source, when a partner delivers a new CSV/Parquet drop, or when asked to "onboard the {name} dataset".
| name | flag-add |
| description | Add a CLI flag to shipctl end-to-end — argument parser definition, help text, shell completion scripts, documentation, and tests. Use when adding a new option or flag, when extending an existing subcommand, or when asked to "add a --flag-name option". |
| metadata | {"forged-by":"cursor-agent","forged-from":"session-2026-04-02","forged-reason":"Added --output, --format, and --timeout flags in three consecutive tasks with identical boilerplate — parser, help, completion, docs, test","usage-count":"22","last-used":"2026-06-01"} |
Add a new CLI flag to a shipctl command end-to-end.
release, build cross, config set)--output-dir)-o)required if mandatory)Define the flag in the parser
For Rust + clap:
// In the relevant Args struct (src/cmd/{command}.rs)
#[arg(long, short = '{alias}', default_value = "{default}",
help = "{description}")]
pub {flag_name}: {type},
For Go + cobra:
// In the relevant command file (cmd/{command}.go)
cmd.Flags().{TypeVar}(&opts.{FlagName}, "{flag-name}", {default}, "{description}")
Wire the value into the command logic
Pass the flag value through to whatever downstream call needs it.
Verify the happy path compiles: cargo check / go build ./....
Update the help text
Run shipctl {command} --help and confirm the flag appears with the correct description and default.
Add shell completions
Regenerate completions (invoke manpage-sync skill, or manually):
shipctl completions bash > completions/shipctl.bash
shipctl completions zsh > completions/_shipctl
shipctl completions fish > completions/shipctl.fish
Commit the updated completion files.
Update documentation
Edit docs/reference/{command}.md:
| --{flag-name} | {type} | {default} | {description} |Write or extend a test
// tests/cmd_{command}.rs
#[test]
fn test_{flag_name}_flag() {
let output = Command::cargo_bin("shipctl").unwrap()
.arg("{command}")
.arg("--{flag-name}").arg("{test-value}")
.assert().success();
// assert output contains expected value
}
Verify the full suite passes
cargo test --workspace
--output-dir, not --outputDir)--flag / --no-flag pair when toggling a default-on behaviorENOENT message)shipctl --help on the parent command to audit existing aliases; pick a different letter or omit the alias.PersistentFlags() (cobra) or Args flattening (clap).true: Document this prominently; many users expect flags to be opt-in.