메뉴
Regenerate man pages and shell completion scripts from the shipctl command tree whenever commands, flags, or subcommands change. Use when a new command or flag is added, when the help text changes, or when asked to "update the man pages" or "sync completions".
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 | manpage-sync |
| description | Regenerate man pages and shell completion scripts from the shipctl command tree whenever commands, flags, or subcommands change. Use when a new command or flag is added, when the help text changes, or when asked to "update the man pages" or "sync completions". |
| metadata | {"forged-by":"codex-agent","forged-from":"session-2026-04-15","forged-reason":"Man pages drifted after three consecutive flag additions — users complained that --help and man shipctl showed different defaults","usage-count":"8","last-used":"2026-04-28"} |
Regenerate man pages and shell completion scripts to match the current command tree.
all (default), man, or completionsdocs/man/)completions/)Build the latest binary
cargo build --release
# or: go build -o dist/shipctl ./cmd/shipctl
Man page generation requires the actual binary to self-report its command tree.
Generate man pages
# Using help2man:
help2man --no-discard-stderr ./target/release/shipctl \
-o docs/man/shipctl.1 \
--name "cross-platform deployment CLI"
# For each subcommand:
help2man --no-discard-stderr "./target/release/shipctl {subcommand}" \
-o "docs/man/shipctl-{subcommand}.1" \
--name "shipctl {subcommand}"
# Alternatively, if the binary has built-in man generation:
./target/release/shipctl man --output-dir docs/man/
Generate shell completions
./target/release/shipctl completions bash > completions/shipctl.bash
./target/release/shipctl completions zsh > completions/_shipctl
./target/release/shipctl completions fish > completions/shipctl.fish
./target/release/shipctl completions powershell > completions/shipctl.ps1
Verify the output
man -l docs/man/shipctl.1 and skim for obvious formatting errorsgrep "{new-flag}" completions/shipctl.bashCommit the generated files
git add docs/man/ completions/
git commit -m "docs(manpages): regenerate for $(./target/release/shipctl --version)"
Update install instructions if a new section or man page was added
Edit docs/install.md → the "Shell completions" and "Man pages" sections.
docs/man/; they are generated, never hand-editedcompletions/; same rule.github/workflows/docs.yml)shipctl(1), shipctl-release(1), shipctl-build(1), etc.help2man not installed: Install via brew install help2man (macOS) or apt-get install help2man (Linux); on CI it is pre-installed.--help text on stderr for help2man to parse; add the --no-discard-stderr flag.shipctl.bash-completion and instruct users to source it explicitly.cargo build --release first; if the build fails, fix it before trying to regenerate.