commit-log

Generate git commit messages and Obsidian vault entries from session context.

1|Updated Dec 13, 2025

Search Tags:#version control #session management #commit message #Obsidian vault #research workflow

Ready to run

npx skills add https://github.com/stephendor/TDL --skill commit-log

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-log
Source: https://github.com/stephendor/TDL/tree/main/.agents/skills/commit-log
Command: npx skills add https://github.com/stephendor/TDL --skill commit-log

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill simplifies the process of creating commit messages and Obsidian vault entries by automatically drafting them after a session, saving time and ensuring consistency.

Core Features & Use Cases

Commit Message Drafting: Automatically generates commit messages based on the type of work completed (e.g., results, decisions, negative results).
Vault Entry Creation: Creates corresponding Obsidian vault entries with relevant file paths and insertion points.
Use Case: At the end of a research session, use this Skill to quickly draft a commit message and a vault entry for the day's work, without having to manually create them.

Quick Start

At the end of your session, use /commit-log to automatically draft a commit message and Obsidian vault entry for your work.

Frequently Asked Questions about commit-log

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

FAQPage Schema

How do I automatically generate git commit messages after a research session?▼

You can automatically generate git commit messages by triggering the `/commit-log` command at the session end. It drafts the commit message using predefined categories like results, decisions, or negative results based on your session context.

Can I create Obsidian vault entries directly from my git commit workflow?▼

Yes, you can create Obsidian vault entries directly alongside your commit messages. The process generates vault entries containing relevant file paths and insertion points, linking your research notes with your version control history.

What is the best way to categorize commit messages for research workflows?▼

The best way to categorize commit messages for research workflows is using predefined categories such as results, decisions, and negative results. This ensures consistent logging of research outcomes directly within your git history.

Do I need external dependencies to draft commit messages and Obsidian vault entries?▼

No, you do not need external dependencies to draft commit messages and Obsidian vault entries. The process operates entirely within the constraints of your git commit workflow and requires no additional setups.

How does session-end context improve commit message drafting?▼

Session-end context improves commit message drafting by capturing accurate details of the completed work. This context allows the system to generate relevant, categorized messages and vault entries that precisely reflect your research activities.