菜单
Use when changing logs, CLI output, or interactive messages in deb_scripts. Covers log levels, separation between user-facing console output and debug/file logs, and CLI UX rules to avoid noisy operational telemetry.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when writing Git commit messages or PR titles for changes in deb_scripts. Covers conventional commits, raw plain-text output, English-only output, and the supported modes single_commit, squash_commit, pr_title, and commit_with_body.
Use when working in the deb_scripts repository on existing code, bug fixes, refactors, CLI behavior, interactive menus, logging, or documentation updates. Covers the project architecture, service contracts, safety constraints, and the expected testing workflow.
Use when adding or changing tests in deb_scripts, or when deciding how to validate a code change. Covers unit, integration, and system test selection, expected smoke checks, and how to verify CLI and interactive behavior without over-testing unrelated paths.
Use when the user wants a plan-first workflow in deb_scripts, asks for a clear execution plan before any changes, or expects work to be performed step by step against an explicit plan with checkpoints.
Use when adding or changing apt, systemctl, ufw, sysctl, curl, rm, or other host-level command execution in deb_scripts. Covers safe subprocess patterns, post-command verification, and what to log versus what to keep in debug output.
Use when changing menu text, prompts, status messages, confirmations, or user-facing CLI output in deb_scripts. Covers concise operator-focused messaging, menu consistency, and avoiding duplicate or noisy output across interactive and non-interactive flows.
| name | deb-scripts-logging |
| description | Use when changing logs, CLI output, or interactive messages in deb_scripts. Covers log levels, separation between user-facing console output and debug/file logs, and CLI UX rules to avoid noisy operational telemetry. |
Use this skill whenever you touch logging, CLI output, error messaging, or interactive prompts.
Make console output useful for an operator running the tool in a terminal:
DEBUG: internal checks, retries, command stdout/stderr snippets, timings, return codes, path probes, state pollingINFO: operation start, meaningful state transitions, successful completion, concise operator guidanceWARNING: recoverable problems, degraded state, manual follow-up that may be neededERROR: operation failed or cannot continueEXCEPTION: unexpected failures onlyDo not emit low-level command return codes or repetitive "checking..." messages at INFO.
app/i18n/.print(...) for menus, prompts, and direct status screens.INFO logs in the service.t(...) for shared operator-facing log messages and tr(...) for localized low-level debug strings when a catalog key would be excessive.When refactoring logs:
args_utils, logger, and touched services.ru and --lang en.