skills.rest
dodonki1223
dodonki1223COMMUNITY
Explore all skills by this author →
Website𝕏@dodonki1223GitHub

vault-git-commit

Creates focused git commits for vault repository note changes.

Updated May 18, 2026
Search Tags:#git#version control#knowledge management#commit#vault#notes#commit message
One-click install
npx skills add https://github.com/dodonki1223/vault --skill vault-git-commit-dodonki1223
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vault-git-commit
Source: https://github.com/dodonki1223/vault/tree/main/.agents/skills/vault-git-commit
Command: npx skills add https://github.com/dodonki1223/vault --skill vault-git-commit-dodonki1223

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing a personal knowledge vault in git often leads to messy commits that mix unrelated notes, leak local-only content, or lack meaningful context. This Skill reviews vault changes, scopes them into single-intent commits, and writes messages that preserve the reasoning behind each change. ## Core Features & Use Cases - Scoped Commit Selection: Separates changes in notes/shared/, .agents/skills/, and repository configuration into distinct commits, while excluding local-only content like notes/local/ and projects/ bodies. - Content Review Before Commit: Checks notes for absolute dates, fact-versus-speculation clarity, and sensitive information such as personal data or internal URLs before staging. - Why-Focused Commit Messages: Generates Japanese commit messages following conventions like chore(vault): or docs(notes):, prioritizing rationale over diff-obvious details. - Use Case: After updating several workflow notes and a skill definition, ask the Skill to review the working tree and produce two clean commits—one for the note updates and one for the skill change—without touching unrelated edits. ## Quick Start Use the vault-git-commit skill to review my current vault changes and create focused git commits for them.

Frequently Asked Questions about vault-git-commit

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

FAQPage Schema
How do I commit note changes in a git-managed vault?▼

Run git status and diff to review changes, then stage only the files belonging to one logical intent and commit with a message explaining why. This Skill automates that review, scoping, and message-writing process for vault repositories.

How do I keep unrelated changes out of a single git commit?▼

Group changes by intent before staging: note updates, skill changes, and repository configuration each get their own commit. Avoid partial staging of mixed files unless hunks are clearly separable and the user requested it.

Should local-only notes be committed to a shared vault repository?▼

No. Directories like notes/local/ and project bodies under projects/ are local-only and must never be staged. Only their explanatory README files may be committed as placement documentation.

What should a good commit message for documentation changes include?▼

A good commit message states the why behind the change rather than restating the diff. Use a concise subject with a prefix like docs(notes): or chore(vault):, and add a short body only when background, constraints, or follow-ups are not visible from the diff.

What should I check before committing notes to git?▼

Verify that dates are absolute rather than relative, facts are separated from speculation, and no personal data, customer information, or internal-only URLs are included. Sensitive details belong in local-only notes outside git tracking.

Related Skills

Explore More Software Engineering Skills→
llm011llm011
9

life-manager

Organize work and personal records into a structured knowledge workflow.

Official
Advanced
kv0906kv0906
134

push

Stage all changes, generate commit messages, and push to the remote repository.

Community
Intermediate
galekagaleka
14

deep-clean

Audit and clean an Obsidian vault for broken links and redundant tags.

Community
Advanced
luanluan
4

git-surgeon

Perform hunk-level Git operations including staging, unstaging, discarding, and commit splitting.

Community
Intermediate