メニュー
Use when implementing or refactoring service classes in deb_scripts. Covers the expected public API, private helper structure, idempotent install/uninstall behavior, status design, and how services should interact with CLI and interactive layers.
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-service-pattern |
| description | Use when implementing or refactoring service classes in deb_scripts. Covers the expected public API, private helper structure, idempotent install/uninstall behavior, status design, and how services should interact with CLI and interactive layers. |
Use this skill when editing code under app/services/.
Services should expose:
install()uninstall()is_installed()get_status()get_info_lines()Activatable services should also expose:
activate()deactivate()is_active()Use app/services/protocols.py as the source of truth for the current contracts.
install() and uninstall() must be idempotent.True.False on failure.activate() and deactivate() should be idempotent for activatable services.is_installed() should answer a boolean question cheaply and predictably.get_status() should provide a short multi-line snapshot for humans.get_info_lines() should return operator-facing info used by the menu layer.ru and --lang en.app/i18n/messages.py via t(...); localized low-level logs may use tr(...).deb-scripts-system-commands when the change adds or alters subprocess behavior.deb-scripts-logging when changing user-visible operational messages.deb-scripts-testing after changing service behavior.