菜单
Use when adding a new managed service to deb_scripts or expanding the service surface. Covers the required files, service interface contract, CLI wiring, interactive menu integration, and test updates.
用 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-new-service |
| description | Use when adding a new managed service to deb_scripts or expanding the service surface. Covers the required files, service interface contract, CLI wiring, interactive menu integration, and test updates. |
Use this skill when the task introduces a new managed component such as a firewall helper, daemon setup, package installer, or server-hardening feature.
deb-scripts-service-pattern for the service class shape and public contract.deb-scripts-system-commands when the service adds subprocess-heavy behavior.deb-scripts-cli-ux for menu labels, prompts, and status wording.deb-scripts-logging for operator-facing logs.deb-scripts-testing for validation scope.Create:
app/services/<service>.pyapp/interfaces/menu/<service>.pytests/unit/test_<service>.pyAdd integration or system tests when the behavior interacts with real subprocesses, files, or host capabilities.
deb-scripts-service-pattern.get_info_lines() to every service.activate()/deactivate()/is_active() only for services whose runtime state differs from package installation.app/i18n/, not hardcoded menu constants.Update:
app/core/service_registry.pyapp/bootstrap/args.pyapp/interfaces/cli/non_interactive.pyapp/i18n/messages.py for stable menu/help/status/info textMake sure the new service gets a unique numeric code and labels in the service registry entry.
00 for service information.0 for returning back.service.get_info_lines(), not a duplicated local constant.deb-scripts-cli-ux for wording and prompt design.t(...).deb-scripts-testing to choose the minimum sufficient test set.Update README.md when the new service changes: