Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From terminal-specialist
Unix signal handling - SIGINT, SIGTERM, SIGHUP with handler patterns and best practices
npx claudepluginhub mwguerra/claude-code-plugins --plugin terminal-specialistHow this command is triggered — by the user, by Claude, or both
Slash command
/terminal-specialist:signals [SIGINT | SIGTERM | SIGHUP | all]This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# Signal Handling Guide You are providing signal handling guidance. Follow these steps: ## 1. Query The user needs help with: $ARGUMENTS ## 2. Read Documentation Read the signal handling documentation: `skills/terminal-docs/references/09-signals.md` ## 3. Common Signals | Signal | Number | Keyboard | Description | |--------|--------|----------|-------------| | SIGHUP | 1 | | Hangup | | SIGINT | 2 | Ctrl+C | Interrupt | | SIGQUIT | 3 | Ctrl+\ | Quit | | SIGKILL | 9 | | Force kill | | SIGTERM | 15 | | Graceful terminate | | SIGTSTP | 20 | Ctrl+Z | Terminal stop | | SIGCONT | 18 | | Con...
/pwsh-scriptCreates, reviews, or optimizes bash/shell scripts with 2025 best practices, ShellCheck compliance, error handling, security checks, and cross-platform support.
/architectProvides system design, architecture definition, review, and technical decision oversight for the specified request.
/hookifyCreates custom behavioral rules from instructions to block or warn on unwanted actions like dangerous bash commands, debug code in files, or missing tests, saving regex-based rules to .claude/ files. Also analyzes conversation history for rule suggestions.
/guidelines-generateGenerates a comprehensive development guideline document for a specified language like Go or Python, customizable via optional parameters for ORM, web framework, DB, testing, logging, and more.
/devkit.fix-debuggingGuides systematic debugging and bug fixing with root cause analysis using language-specific agents. Specify --lang (java, spring, typescript, nestjs, react, python, general) and issue details.
/cliSelects and executes optimal CLI tools for a given task using terminal-native expert patterns, with optional preference like 'modern' or 'standard'.
Share bugs, ideas, or general feedback.
You are providing signal handling guidance. Follow these steps:
The user needs help with: $ARGUMENTS
Read the signal handling documentation:
skills/terminal-docs/references/09-signals.md
| Signal | Number | Keyboard | Description |
|---|---|---|---|
| SIGHUP | 1 | Hangup | |
| SIGINT | 2 | Ctrl+C | Interrupt |
| SIGQUIT | 3 | Ctrl+\ | Quit |
| SIGKILL | 9 | Force kill | |
| SIGTERM | 15 | Graceful terminate | |
| SIGTSTP | 20 | Ctrl+Z | Terminal stop |
| SIGCONT | 18 | Continue | |
| SIGWINCH | 28 | Window resize |
trap 'cleanup' EXIT
trap 'echo "Interrupted"' INT TERM
struct sigaction sa;
sa.sa_handler = handler;
sigemptyset(&sa.sa_mask);
sa.sa_flags = SA_RESTART;
sigaction(SIGINT, &sa, NULL);
import signal
signal.signal(signal.SIGINT, handler)
Based on the user's query: