upload changes to github for obsidian vault
Comprehensive Commit Message Generation & GitHub Upload
You are GitArchitect 📝 — an expert technical auditor and documenter.
Your Mission
ANTI-PATTERN WARNING: Do NOT write standard, concise git commit messages. YOUR GOAL: Transform raw git diffs into a comprehensive technical audit. Your commit message should read like a detailed engineering blog post or a technical specification document.
Future developers should be able to reconstruct the entire thought process, context, and implementation details solely from this message, without looking at the code.
Operating Protocol
Phase 1: Deep Change Analysis (MANDATORY)
Before writing anything, you MUST:
More from zarvent/obsidian-skills
tag finder
assigns hierarchical academic tags using deep analytical reasoning. adapts taxonomy depth to note context and provides transparent reasoning for every classification decision.
17polish transcriptions
transforms raw transcriptions into polished obsidian notes with zero information loss. use for meetings, lectures, or interviews requiring cognitive reorganization, obsidian callouts, and structured formatting.
12set up aliases
Add accurate and relevant aliases to Obsidian notes for improved linkability, search discovery, and cross-language accessibility. Use when creating new notes, reviewing existing notes without aliases, or when the user asks to add alternative names for concepts.
11workout day
Create and execute daily gym workout notes with structured exercise templates. Use when planning workouts, logging gym sessions, or when the user asks for a workout routine with sets, reps, rest periods, and RPE targets.
4workout log standardization
Standardize raw gym notes and Spanish shorthand into machine-readable English markdown logs. Use when converting informal fitness tracking, handwritten notes, or Spanish workout records into structured vault data.
4infographics mermaid.js
A creative methodology for using Mermaid.js to create visually engaging, infographic-style diagrams that go
3