cerebro-commit

Stage all Obsidian vault changes, commit with a descriptive message, and push to the remote repository.

Updated May 30, 2026

Search Tags:#git #workflow #commit #push #vault #data-integrity #identity

Ready to run

npx skills add https://github.com/rhortal/cerebro-skills --skill cerebro-commit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cerebro-commit
Source: https://github.com/rhortal/cerebro-skills/tree/main/cerebro-commit
Command: npx skills add https://github.com/rhortal/cerebro-skills --skill cerebro-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that all Cerebro vault changes are staged, described, and pushed to a remote repository in a safe, auditable workflow, preventing partial commits and data loss.

Core Features & Use Cases

Stages all vault changes with git add -A to guarantee nothing is left behind
Verifies and enforces a correct GitHub identity before pushing
Produces a descriptive commit message and pushes the vault to the remote repository, ensuring a complete, auditable history

Quick Start

Run cerebro-commit to stage all changes, create a descriptive message, and push to the remote vault repository.

Frequently Asked Questions about cerebro-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I safely commit and push all Obsidian vault changes to a remote git repository?▼

To commit vault changes safely, stage all files using git add -A, create a descriptive commit message, and push to the remote repository. This workflow ensures every modification is synchronized without partial commits.

What is the best way to prevent partial commits when pushing an Obsidian vault?▼

Preventing partial vault commits requires full staging with git add -A before committing. This guarantees nothing is left behind, preserving data integrity and traceability across the entire vault synchronization process.

Do I need GitHub CLI authentication to push vault updates to a remote repository?▼

Yes, GitHub CLI authentication is required. The workflow verifies and enforces a correct GitHub identity via gh auth before pushing, ensuring secure, authorized synchronization of vault changes to the remote repository.

How does git add -A work for synchronizing Cerebro vault updates?▼

Using git add -A stages all vault changes including modifications, additions, and deletions. This guarantees a complete, auditable history by ensuring every file change is committed and pushed to the remote repository.

Can I use this git push workflow for large Obsidian vaults without data loss?▼

Yes, this workflow is designed for complete vault synchronization without data loss. By enforcing full staging and identity verification, it captures every change and preserves data integrity during the git push operation.