skills.rest
dudusoar
dudusoarCOMMUNITY
Explore all skills by this author →
GitHub

git-log

Generate Conventional Commits messages and update GIT_LOG.md documentation.

Updated Apr 23, 2024
Search Tags:#documentation#commit messages#version-control#conventional-commits#git-log#change-log
One-click install
npx skills add https://github.com/dudusoar/VRP-Toolkit --skill git-log
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-log
Source: https://github.com/dudusoar/VRP-Toolkit/tree/main/.claude/skills/git-log
Command: npx skills add https://github.com/dudusoar/VRP-Toolkit --skill git-log

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams maintain clean, consistent git histories by automating commit message generation and documenting changes in a structured git log.

Core Features & Use Cases

  • Structured commit messages following Conventional Commits.
  • Automated git log maintenance and change-log generation.
  • Quick-reference commands and workflow guidance for daily development.

Quick Start

Use the git-log skill when preparing to commit changes, reviewing history, or updating project changelogs. Steps:

  1. Review changes with git status.
  2. Invoke the skill to generate a Conventional Commits-compliant message.
  3. Commit using git commit -m "<generated message>".
  4. Update .claude/GIT_LOG.md with the new entry.

Frequently Asked Questions about git-log

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

FAQPage Schema
How do I generate conventional commit messages automatically?▼

To generate conventional commit messages, invoke the git-log skill after running git status to review changes. The skill produces a compliant message string to use directly with git commit.

What is the best way to maintain a structured git log for project documentation?▼

Maintaining a structured git log involves appending generated commit entries to a central GIT_LOG.md file. The git-log skill automates this by tracking changed files and providing templates to update your project's change documentation consistently.

How do I format commit messages to follow the Conventional Commits standard?▼

Formatting commit messages to follow the Conventional Commits standard requires applying specific structural prefixes to your changes. The skill enforces this format automatically by generating messages that comply with the standard's formatting rules.

Can I track changed files and update a central change log automatically?▼

Yes, you can track changed files and update a central change log by integrating the skill's workflow into your development process. It tracks file modifications and provides steps to append new structured entries into your GIT_LOG.md documentation.

Do I need any dependencies to automate version-control commit message generation?▼

No dependencies are required to automate version-control commit message generation with this skill. It operates independently to provide guidance on message formatting, change tracking, and quick-reference commands for your daily workflow.

Related Skills

Explore More Software Engineering Skills→
chcardozchcardoz

commit

Generate git commit messages by analyzing staged and unstaged changes.

Community
Intermediate
derrybirkettderrybirkett
1

activity-log

Log git commit activity and query filtered summaries from notes/activity-log.md.

Community
Intermediate
AnveioAnveio
1

task-pull-request

Automate GitHub pull request creation, reviews, feedback, and merges via gh CLI.

Community
Intermediate
DrLuggelsDrLuggels
3

changelog-automation

Generate changelogs and release notes from Conventional Commits.

Community
Advanced