commit

Analyze git status and diffs to create atomic commits with conventional standards.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/goffity/dev-km --skill commit-goffity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/goffity/dev-km/tree/main/skills/commit
Command: npx skills add https://github.com/goffity/dev-km --skill commit-goffity

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of committing code by ensuring commits are atomic, well-described, and linked to relevant issues, improving code quality and project traceability.

Core Features & Use Cases

  • Atomic Commits: Analyzes changes and groups them by purpose for clean, focused commits.
  • Conventional Commits: Enforces a standardized commit message format for better readability and automation.
  • Issue Linking: Automatically comments on associated GitHub issues with commit details.
  • Use Case: After completing a specific feature, you can run this Skill to ensure all related code changes are committed atomically and that the corresponding GitHub issue is updated with the implementation details.

Quick Start

Run the tdg:atomic skill to analyze your changes and create atomic commits.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I create atomic commits that group code changes by purpose?

You can create atomic commits by using the TDG framework to analyze git status, staged diff, and unstanged diff, grouping changes by purpose before staging, reviewing, testing, and committing to ensure clean, focused commits.

Can I automatically update GitHub issues when making a conventional commit?

Yes, you can automatically update GitHub issues by linking commits to specific issues during the commit process, which posts an automatic comment on the associated issue with the implementation and commit details.

What is the best way to enforce conventional commit standards in my git workflow?

The best way to enforce conventional commit standards is to automate the commit creation process, analyzing your code diffs to generate standardized commit messages that improve readability and project traceability.

How does issue linking work when automating commits for code review?

Issue linking works by analyzing your git diff and grouping related changes, allowing the commit automation to comment on associated GitHub issues with specific commit details to facilitate code review and project management.

Do I need to manually stage files before running atomic commit automation?

No, you do not need to manually stage files beforehand because the automation analyzes your git status and unstaged diff to group changes by purpose, handling the staging, reviewing, and testing steps before committing.