How this command is triggered — by the user, by Claude, or both
Slash command
/claude-code-backup:backup [dry-run] [no-project] [no-history] [full] [strict-secrets] [include-env]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
You are running the `claude-backup` CLI. It is a standalone tool; do not assume anything about Claude Code's internal state. The user's arguments are: `$ARGUMENTS` Map each space-separated keyword to a flag (ignore unknown words): | keyword | flag | |------------------|--------------------| | `dry-run` | `--dry-run` | | `no-project` | `--no-project` | | `no-history` | `--no-history` | | `full` | `--full` | | `strict-secrets` | `--strict-secrets` | | `include-env` | `--include-env` | Then run `claude-backup` w...
You are running the claude-backup CLI. It is a standalone tool; do not assume
anything about Claude Code's internal state.
The user's arguments are: $ARGUMENTS
Map each space-separated keyword to a flag (ignore unknown words):
| keyword | flag |
|---|---|
dry-run | --dry-run |
no-project | --no-project |
no-history | --no-history |
full | --full |
strict-secrets | --strict-secrets |
include-env | --include-env |
Then run claude-backup with the mapped flags via the Bash tool, for example:
/backup → claude-backup/backup dry-run → claude-backup --dry-run/backup no-history → claude-backup --no-history/backup dry-run strict-secrets → claude-backup --dry-run --strict-secretsReport the resulting archive path and surface any secret warnings the tool
prints. If the claude-backup command is not found, tell the user to run the
project's install.sh and ensure ~/.local/bin is on their PATH.
npx claudepluginhub dberuben/claude-code-backup --plugin claude-code-backup/backupGenerates automated database backup scripts, restore procedures, cron schedules, monitoring setups, and recovery plans for systems like PostgreSQL, MySQL, MongoDB.
/backupDesigns backup strategies and disaster recovery plans: inventories data assets, defines RPO/RTO targets, automates verification, tests recovery, generates runbooks with PROTECTED/PARTIAL/AT-RISK verdict. Supports inventory, strategy, runbook, test, and scenario flags.
/backupBacks up MCP server configurations by running the armour backup script, creating ~/.armour/backup.json for restoration.