domains / families / devops / doca-argp

doca-argp

separate

Use this skill for hands-on DOCA Arg Parser CLI work on a shipped sample or new DOCA-using app — adding / removing / renaming flags; wiring `doca_argp_init` → register params → `doca_argp_start` → `doca_argp_destroy` in order; picking a parameter type from the full public enum (`DOCA_ARGP_TYPE_STRING`, `_INT`, `_BOOLEAN`, `_DEVICE`, `_DEVICE_REP`, `_DOUBLE` — six values, not three); preserving the built-in DOCA flags (`-h` `-v` `-l` `--sdk-log-level` `--log-filter` `-j`/`--json`, NOT `--json-config`); `--device` is per-program; or debugging `DOCA_ERROR_BAD_STATE` / `INVALID_VALUE` / `NOT_SUPPORTED` / `IO_FAILED` from `doca_argp_*`. Trigger on implicit phrasings: "add a custom flag to a DOCA sample", "should I use getopt here", "BAD_STATE registering a new param", "my JSON config key is rejected", or "my sample's --json is ignored". Refuse and route elsewhere for variadic-flag / subcommand / shell-completion features, DOCA Core context, or DOCA Log internals.

When to use

• adding / removing / renaming flags
• wiring doca_argp_init to doca_argp_destroy
• picking a parameter type from the public enum
• preserving built-in DOCA flags
• debugging DOCA_ERROR_BAD_STATE
• debugging INVALID_VALUE
• debugging NOT_SUPPORTED
• debugging IO_FAILED

When not to use

• variadic-flag features
• subcommand features
• shell-completion features
• DOCA Core context
• DOCA Log internals

Skill page

Source