원클릭으로
cli-tooling-executor
Domain guidance for implementing CLI and tooling phases. Loaded when phase category is CLI.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Domain guidance for implementing CLI and tooling phases. Loaded when phase category is CLI.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Domain guidance for implementing API and service layer phases. Loaded when phase category is API.
Domain guidance for planning API and service layer phases. Loaded when phase category is API.
Domain guidance for reviewing API and service layer phases. Loaded when phase category is API.
Domain guidance for planning authentication and security phases. Loaded when phase category is AUTH.
Domain guidance for planning CLI and tooling phases. Loaded when phase category is CLI.
Domain guidance for planning data and persistence phases. Loaded when phase category is DATA.
| name | cli-tooling-executor |
| description | Domain guidance for implementing CLI and tooling phases. Loaded when phase category is CLI. |
Use the language's standard CLI library (argparse/click for Python, cobra for Go). Define all arguments with types, defaults, and help text in the parser, not manually.
Use subparsers/subcommands rather than manual flag checks. Prevents argument/command confusion.
Always exit 0 for success, >0 for errors. Use specific codes for different error types. Ensure wrappers propagate signal exit codes correctly.
Check stdin.isatty() before prompting. Provide --no-prompt/--yes for non-interactive use. If no TTY and interactive required, exit with informative error.
Sanitize/escape user inputs for shell safety. Use shlex.quote or equivalent when building commands. Handle paths with spaces.
Test via subprocess invocation, not just function calls. Assert exit codes, stdout content, stderr content for: valid input, missing input, invalid input.