skills.rest
VictorHueni
VictorHueniCOMMUNITY
Explore all skills by this author →
GitHub

util-docs-log

Generate a Markdown change log from Git history for a specified directory.

Updated Apr 8, 2026
Search Tags:#automation#git#change log#document tracking#directory history
One-click install
npx skills add https://github.com/VictorHueni/homemade-claude-kit --skill util-docs-log
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: util-docs-log
Source: https://github.com/VictorHueni/homemade-claude-kit/tree/main/skills/util-docs-log
Command: npx skills add https://github.com/VictorHueni/homemade-claude-kit --skill util-docs-log

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation of change logs for directories, using Git history as the source of truth. It saves time by generating logs that are always up-to-date with the latest changes.

Core Features & Use Cases

  • Generate Change Logs: Automatically create logs for directory changes based on Git history.
  • On-Demand Generation: Run the skill at any time to generate or refresh the log.
  • Folder Selection: Choose a specific folder to generate the log for, or let the skill prompt for a folder if none is specified.
  • Use Case: Use this Skill to keep track of changes in your project's documentation directory, ensuring that everyone is up-to-date with the latest changes.

Quick Start

Generate a change log for the 'docs' folder using the 'util-docs-log' skill.

Frequently Asked Questions about util-docs-log

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

FAQPage Schema
How do I generate a change log from Git history for a specific directory?▼

You can generate a change log by running the tool against a target folder that is a Git repository. It extracts commit history and outputs a Markdown file with a chronological list of changes grouped by date.

What is the best way to automate change log creation for a documentation directory?▼

Automating change log creation for a documentation directory involves using Git history as the source of truth. This tool runs on demand to generate or refresh a Markdown log, ensuring your project documentation stays up-to-date with the latest changes.

Does this change log generator work without a Git repository?▼

No, this change log generator requires the target directory to be a Git repository. You must also have the necessary permissions to access the repository in order to extract the chronological commit history for the Markdown output.

Can I specify which folder to track when generating a directory change log?▼

Yes, you can specify a particular folder to generate the change log for. If no directory is specified, the tool will prompt you to select a folder before extracting the Git history and creating the Markdown output.

What format is the output file when generating directory history logs from Git?▼

The output format for directory history logs is a Markdown file. This file contains a chronological list of changes extracted from Git history, grouped by date for easy tracking of project modifications.

Related Skills

Explore More Software Engineering Skills→
omerkllmomerkllm

speckit-git-initialize

Initialize a Git repository and create an initial commit.

Community
Intermediate
chengyihuachengyihua

baoyu-markdown-to-html

Convert Markdown with frontmatter into styled HTML for WeChat articles.

Community
Advanced
yakksiekyakksiek

10x-archive

Move completed change folders to an archive directory and update related documents.

Community
Advanced
jorgeavaldezjorgeavaldez
1

commit

Generate a one-line commit message from current working directory diffs.

Community
Intermediate