Logs git status, inferred commit categories, and rationale to Markdown files.
npx skills add https://github.com/martylouis/agents --skill log-changes
Please help me install this Agent Skill. Skill: log-changes Source: https://github.com/martylouis/agents/tree/main/skills/log-changes Command: npx skills add https://github.com/martylouis/agents --skill log-changes
This Skill helps you capture the reasoning behind your code changes, ensuring that the 'why' is documented alongside the 'what'.
Use the log-changes skill to create a log entry for your current work.
High-intent search queries and answers about installing and using this skill.
To document the rationale behind git code changes, you can use an automated logging skill that captures conversational context and git status to generate structured Markdown files. This ensures the 'why' behind modifications is recorded alongside the code.
Yes, you can automatically categorize git commits by inferring categories like feat, fix, or chore from your discussion context. The logging skill analyzes your conversation to assign the appropriate commit type and synthesizes the reasoning into a Markdown file.
The best way to log code changes with timestamps and branch information is to automate the capture of git status and metadata. This generates a structured Markdown log file in a user-specified location, preserving the context and rationale of your work.
No, this logging skill does not require manual input for git metadata. It automatically gathers git status, branch, and timestamps, allowing you to focus on discussing the changes while it synthesizes the reasoning and generates the Markdown log.
You can generate a Markdown log file for code modifications by using a logging skill that synthesizes the reasoning behind changes. It outputs a structured Markdown file in your defined location, capturing the rationale and inferred commit categories.
saadjsConvert uncommitted changes into small conventional commits via git add -p.
AI-Foundry-CoreGenerate changelogs from commits, PRs, and releases using Keep a Changelog format.
claude-worldAutomate collection of code changes, test results, and commit history via Git hooks.
haomingzAnalyze git diffs to generate Conventional Commits with inferred type and scope.
