commit

Stage code changes, generate semantic commit messages, and create pull requests.

4|Updated Feb 5, 2026

Search Tags:#git #code review #documentation #version control #pull request #commit

Ready to run

npx skills add https://github.com/kvnwolf/devtools --skill commit-kvnwolf

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/kvnwolf/devtools/tree/main/plugins/base/skills/commit
Command: npx skills add https://github.com/kvnwolf/devtools --skill commit-kvnwolf

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of committing code, syncing documentation, and creating pull requests, reducing manual effort and ensuring consistency.

Core Features & Use Cases

Automated Staging: Stages all changes or specific documentation files automatically.
Intelligent Commit Messages: Generates semantic commit messages with subjects and bodies.
Documentation Sync: Updates relevant Markdown files based on code changes.
PR Creation: Creates pull requests with relevant context from commit history and diffs.
Use Case: After finishing a feature, use this skill to ensure your code is committed with a clear message, documentation is updated, and a pull request is ready for review.

Quick Start

Use the commit skill to wrap up your work by staging, committing, and pushing your changes.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I automate git commit messages and pull request creation?▼

Automating git commit messages and pull request creation involves staging changes, generating semantic commit messages, syncing documentation, and opening pull requests. This skill requires Git and GitHub CLI installed to execute the workflow.

What's the best way to generate semantic commit messages for version control?▼

Generating semantic commit messages is best handled by automating the process to produce subjects and bodies based on code changes. This ensures consistent version control practices and reduces manual effort across software development workflows.

Can I sync markdown documentation automatically when committing code changes?▼

Yes, you can sync markdown documentation automatically when committing code changes. The documentation sync feature updates relevant Markdown files based on staged code changes before finalizing the commit and creating a pull request.

Do I need GitHub CLI to create pull requests from the command line?▼

Yes, you need GitHub CLI to create pull requests from the command line using this automated workflow. The process requires Git and GitHub CLI for execution to stage changes and open pull requests with relevant diff context.

How does a pull request get context from commit history and diffs?▼

A pull request gets context from commit history and diffs by extracting relevant information from staged changes and generated semantic commit messages. This automated process ensures the pull request contains accurate context for code review.