upgrade
/upgrade
Aktualizuje vault Obsidiana do najnowszej wersji obsidian-claude-pkm: tworzy kopię zapasową, pokazuje różnice i zachowuje treści.
- Autor
- kayossouza ↗
- Repozytorium
- brain-template ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 27.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 1
Brak sygnałów. Repozytorium zmienione 27.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Aktualizuje vault Obsidiana do najnowszej wersji obsidian-claude-pkm: tworzy kopię zapasową, pokazuje różnice i zachowuje treści.
Oryginalny opis (EN)
Update vault to the latest version of obsidian-claude-pkm. Creates backup, shows diffs, preserves your content. Use when a new version is available.
Jak działa
- Usage
- What Gets Updated (System Files)
- What Never Gets Touched (Your Content)
- Upgrade Process
- Check Mode (/upgrade check)
- Output Format
- Safety Features
- Error Handling
- Integration
Podgląd SKILL.md
--- name: upgrade description: Update vault to the latest version of obsidian-claude-pkm. Creates backup, shows diffs, preserves your content. Use when a new version is available. allowed-tools: Read, Write, Edit, Glob, Grep, Bash model: sonnet user-invocable: true --- # Upgrade Skill Updates your vault's system files to the latest version while preserving all your personal content. > **Vault em pt-BR feito com o brain-template:** o upstream é o [ballred/obsidian-claude-pkm](https://github.com/ballred/obsidian-claude-pkm), em inglês. Atualizar a partir dele substitui a tradução e os acréscimos deste template (`brain-lint.py`, `agent-writes.md`, os denies de segredo e git no `settings.json`, as pastas e templates extras). Revise cada diff e pule os arquivos que quiser manter. ## Usage ``` /upgrade # Interactive upgrade with backup and diff review /upgrade check # Preview what's changed without making modifications ``` ## What Gets Updated (System Files) - `.claude/skills/*/SKILL.md` — Skill definitions - `.claude/agents/*.md` — Agent configurations - `.claude/hooks/*.sh` — Automation scripts - `.claude/rules/*.md` — Convention rules - `.claude/output-styles/*.md` — Output style definitions - `.claude/settings.json` — Permissions and hook config - `CLAUDE.md` — Root context file (merged carefully) - `Templates/*.md` — Note templates ## What Never Gets Touched (Your Content) - `Daily Notes/**` — Your daily journal entries - `Goals/**` — Your goal files and reviews - `Projects/**` — Your project folders and CLAUDE.md files - `Archives/**` — Your archived content - `Inbox/**` — Your captured items - `CLAUDE.local.md` — Your personal overrides - `vault-config.json` — Your preferences ## Upgrade Process ### Step 1: Check for Updates Read the current version from `CLAUDE.md` (look for the "Versão do sistema:" line). Compare with the upstream repo. If using git: ```bash git fetch origin git log HEAD..origin/main --oneline ``` If not a git repo or no remote, inform user they need to download the latest `vault-template/` manually. ### Step 2: Create Backup Before any changes, create a timestamped backup: ```bash BACKUP_DIR=".backup/upgrade-$(date +%Y%m%d-%H%M%S)" mkdir -p "$BACKUP_DIR" cp -r .claude "$BACKUP_DIR/" cp CLAUDE.md "$BACKUP_DIR/" cp -r Templates "$BACKUP_DIR/" 2>/dev/null ``` Tell the user: "Backup created at $BACKUP_DIR" ### Step 3: Diff Review For each system file that differs from upstream: 1. Show a summary of what changed (additions, removals, modifications) 2. Ask user to confirm: "Apply this update? (yes/skip/stop)" 3. If yes: apply the change 4. If skip: leave this file unchanged 5. If stop: halt the upgrade (backup remains, partial changes preserved) ### Step 4: Apply Changes For each confirmed file: - Copy the new version from upstream - For `CLAUDE.md`: merge carefully — preserve user customizations (`Propósito do sistema`, `Foco atual` sections) while updating system sections (`Skills disponíveis` table, version number) - For `settings.json`: merge — add new permissions/hooks, preserve existing customizations ### Step 5: Post-Upgrade 1. Make hook scripts executable: `chmod +x .claude/hooks/*.sh` 2. Show summary of changes applied 3. Update version in CLAUDE.md 4. Suggest running `/onboard` to reload context ## Check Mode (`/upgrade check`) When invoked with "check": 1. Compare system files against upstream 2. List files that would be updated with brief change description 3. Show version numbers (current → available) 4. Do NOT make any changes 5. Suggest running `/upgrade` to apply ## Output Format ```markdown ## Upgrade Check **Current version:** 3.0 (The Cascade) **Available version:** 3.1 ### Files to Update | File | Change Summary | |------|---------------| | `.claude/skills/daily/SKILL.md` | Added cascade context surfacing | | `.claude/agents/goal-aligner.md` | Added memory: project | | `.claude/hooks/session-init.sh` | Added priority surfacing | ### New Files - `.claude/skills/review/SKILL.md` — Smart review router ### No Changes Needed - `.claude/rules/` — Already up to date Run `/upgrade` to apply these updates (backup will be created first). ``` ## Safety Features - Complete backup before any modification - File-by-file confirmation - Can be stopped at any point - User content folders are never touched - `CLAUDE.local.md` personal overrides preserved - Backup includes restoration instructions ## Error Handling - If no git remote: guide user to download latest vault-template manually - If backup fails: abort entire upgrade - If a file copy fails: report error, continue with next file - Always leave vault in a usable state ## Integration Works with: - `/onboard` — Reload context after upgrade - Session init hook — Will reflect updated priorities
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · kayossouza/brain-template | 100 | MIT |
| rossumai/claude-marketplace | 100 | MIT |
| naymspace/backpex | 100 | MIT |
| hellblazer/nexus | 100 | AGPL-3.0 |
| chrs-myrs/livespec | 100 | MIT |
| jamesm-dev/payday-dev | 100 | MIT |
| kayossouza/brain-template | 100 | MIT |
| fx/cc | 100 | MIT |
| platform-engineering-labs/formae-mcp | 100 | Apache-2.0 |
Migawka bazy z 13.11.2026 · wersja paczki 91132a654afd (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 95obsidian-github-sync
Synchronizuje vault Obsidian z repozytorium GitHub, wykrywa konflikty i konfiguruje codzienną kopię zapasową. - 100obsidian-vault-setup
Interaktywnie konfiguruje nowy vault Obsidiana: dopasowuje strukturę, tworzy początkowy plik CLAUDE.md i komendy slash. - 100pkm-write
Zapisuje notatki w vaulcie: tworzy nowe, edytuje i dopisuje do istniejących, sprawdza duplikaty, znajduje powiązania, dodaje adnotacje i aktualizuje indeksy. - 100obsidian
Buduje wtyczki, automatyzuje przepływy i zarządza bazami wiedzy w Obsidian: struktury sejfów, szablony Templater, zapytania Dataview, motywy CSS, integracje, potoki publikacji i systemy PKM. - 100obsidian-git-backup-sync-automation
Automatyzuje kontrolę wersji vaultu Obsidian przez Obsidian Git: historię commitów, gałęzie i rozwiązywanie konfliktów. - 100obsidian
Obsługuje funkcje specyficzne dla Obsidiana: wikilinki, backlinki, canvas, notatki dzienne i właściwości frontmatter, gdy użytkownik wprost wskazuje Obsidiana lub jego możliwości vaulta.