메뉴
Use when the friend wants to back up their wiki to a private remote, or check backup status. Triggers on /ren:backup with optional subcommands (--setup, --tarball, --status). Git push primary, tarball fallback.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | backup |
| description | Use when the friend wants to back up their wiki to a private remote, or check backup status. Triggers on /ren:backup with optional subcommands (--setup, --tarball, --status). Git push primary, tarball fallback. |
| version | 0.5.7 |
| license | MIT |
| framework_version | 0.5.7 |
| schema_version | 1 |
| type | skill |
| execution_tier | deterministic |
| contract | {"required_outputs":["For /ren:backup: either a successful git push to the 'backup' remote, OR a tarball at plugin_data_dir()/backups/wiki-<timestamp>.tar.gz","For /ren:backup --setup: git remote 'backup' configured on the wiki repo at the provided URL","For /ren:backup --tarball: a tarball, regardless of remote configuration","For /ren:backup --status: a printed report including last-backup timestamp + remote URL (or 'not configured')","Tarball retention enforced: at most TARBALL_RETENTION_KEEP (default 20) most-recent tarballs in the backups dir"],"budgets":{"turns":2,"files_written":1,"duration_seconds":30},"permissions":{"read":["~/.renos/wiki/**"],"write":["~/.claude/plugins/data/renos/backups/**"],"execute":[]},"completion_conditions":["On --status: status output naming wiki path, remote URL (or 'not configured'), and last-backup timestamp"],"output_paths":["~/.claude/plugins/data/renos/backups/"]} |
| tags | ["backup","wiki","remote","tarball"] |
| related_skills | ["metric-watch","doctor"] |
| references_required | [] |
| references_on_demand | [] |
Wiki-only backup: git push to a configured backup remote is primary; a local tarball is the fallback (no remote configured, push fails, or --tarball forced).
"backup", not "origin"skills.metric-watch.lib's _check_backup (Task 6.3, shipped first) already checks for a git remote literally named "backup" and reads tarballs from plugin_data_dir()/"backups". This skill's default remote name and backup directory match that contract exactly — backup_configured() (this skill) and _check_backup() (metric-watch) read the exact same state, so they can never silently disagree.
/ren:backup (commits + pushes if the backup remote is configured; else tarball)/ren:backup --setup <remote-url> to configure the backup git remote (typically a private GitHub repo)/ren:backup --tarball to force a tarball even if a remote is configured/ren:backup --status for a status report/ren:backup/ren:install).backup remote is configured: push. Success → done, no tarball. Non-fast-forward → refuse (never force-push automatically; point at the recovery doc). Transport failure → tarball fallback + warning.--setup.TARBALL_RETENTION_KEEP (default 20) most recent./ren:backup --setup <remote-url>Validates the URL shape, confirms the wiki is a git repo, adds or updates the backup remote, and reads it back to confirm.
/ren:backup --tarballSkips the push path entirely; always tarball (commits pending changes first).
/ren:backup --statusRead-only report: is the wiki a git repo, remote URL (or "not configured"), last commit sha/date, tarball count + oldest/newest tarball dates.
Donor's SKILL.md described a "confirm before changing the backup remote" behavior at the skill level. In RenOS, that confirmation is enforced structurally by the Task 6.2 write_gate PreToolUse hook (hooks/guards/write_gate.py), which already gates backup-remote-change operations per spec §3.6 A-8 item 6. This skill's setup_remote() does not duplicate that confirmation — it trusts the hook layer to have already gated the call before this function runs.
/ren:metric-watch's backup-unconfigured finding is the nag mechanism for "you haven't backed up"; this skill just performs the backup when invoked.| Failure | Behavior | User-visible |
|---|---|---|
No remote configured + /ren:backup | Tarball fallback automatic + nag | "No remote configured. Created tarball at <path>. Configure with /ren:backup --setup <url>" |
| git push network failure | Tarball fallback + warning | "Push failed (network). Tarball at <path>. Retry with /ren:backup later." |
| Non-fast-forward push rejection | Refused, no auto-tarball (user decision moment) | "Push rejected: remote diverged. See recovery doc. Force-push NOT performed automatically." |
| Wiki not a git repo | Refused | "Wiki is not a git repo. Run /ren:install to bootstrap." |
skills/metric-watch/lib) — the _check_backup contract this skill's backup_configured()/remote-name/dir match exactlyhooks/guards/write_gate.py) — the remote-change confirmation enforcement layerskills/backup/lib/__init__.py (donor, ~/Dev/startup-framework) — the carried implementationUse when the friend wants to start a brand-new project's memory — nothing to scan yet, just a name. Triggers on the /ren:bootstrap-project slash command. Stamps the shared wiki skeleton (additive) and queues an empty L2 pointer-map for the project. For an EXISTING repo with real code/git history, use /ren:ingest-project instead.
Use when the friend wants a structural map of a codebase (call graphs, symbol index, cross-file references) — beyond what wake-up/recall already surface from the wiki. Triggers on /ren:code-map [build|status]. A thin wrapper over Graphify (pinned 0.9.x), never a second hand-rolled engine; gracefully absent if Graphify isn't installed.
Use when the friend wants a framework health check, or after /ren:update to confirm nothing broke. Triggers on /ren:doctor. Runs a battery of small, isolated checks (env, wiki structure, frontmatter, schema versions, budget lint, dangling L2 pointers, graphify status, backup configuration, global-tier drift, harness neutrality) — all warn-not-block.
Use when the friend wants to bring an EXISTING project (real code/git history) into their wiki as an L2 pointer-map. Triggers on the /ren:ingest-project slash command (optional [path]). A read-only scanner mines the repo for facts; the live session drafts compact knowledge + pointers from those facts; this skill assembles and queues the map, then shows the friend the first-session artifact — the visible proof memory was captured (spec §3.8 A-10). For a brand-new project with nothing to scan, use /ren:bootstrap-project instead.
Use for first-time setup of RenOS, or to resume a partial setup. Triggers on the /ren:install slash command. Idempotent guided flow: environment check, wiki bootstrap, optional interview, backup nag, companion offers, first project, then a closing summary of what's now possible. Every stage is skippable except wiki bootstrap; re-running skips whatever's already done.
Use to build or update the friend's identity + working-style profile. Triggers on the /ren:interview slash command, or delegated to from /ren:install's onboarding flow. Asks ONLY from a capped, skippable question list — every question is optional, the whole interview can be skipped, and every unanswered field gets a sane default. No venture/founder questions in this default path.