commit

Generates conventional commits with build checks and changelog updates for .NET projects.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/gmolike/Claude-Template --skill commit-gmolike
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/gmolike/Claude-Template/tree/main/template-backend-dotnet/.claude/skills/commit
Command: npx skills add https://github.com/gmolike/Claude-Template --skill commit-gmolike

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually writing consistent commit messages, verifying builds before committing, and keeping a changelog up to date is repetitive and error-prone. This Skill standardizes the entire commit workflow for .NET repositories. ## Core Features & Use Cases - Status Inspection: Reviews staged and unstaged changes via git status and diff statistics before committing. - Pre-Commit Verification: Runs dotnet build and dotnet test to catch broken code before it enters history. - Conventional Commits: Generates messages in the format type(scope): description with predefined scopes like domain, application, infrastructure, api, tests, and ci. - Changelog Maintenance: Updates CHANGELOG.md automatically and commits only after user confirmation. - Use Case: After finishing a bugfix in a .NET API, invoke the Skill to verify the build passes, generate a properly scoped commit message, and update the changelog in one guided flow. ## Quick Start Ask the assistant to commit the current changes in your .NET project with a conventional commit message and changelog update.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I create conventional commits in a .NET project?

Use the format type(scope): description with scopes like domain, application, infrastructure, api, tests, or ci. This Skill generates the message automatically after inspecting your staged changes and verifying the build.

How to run build and test checks before committing?

Run dotnet build --no-restore and dotnet test --no-build before committing to catch compilation errors and failing tests early. The Skill executes these pre-commit checks automatically and shows the last 20 lines of output.

Does this commit workflow update the changelog automatically?

Yes, the workflow includes a dedicated step that updates CHANGELOG.md based on the changes being committed. The commit is only executed after you confirm the generated message and changelog entry.

Can I provide my own commit message instead of a generated one?

Yes, the Skill accepts an optional message argument that you can pass when invoking it. If omitted, it generates a conventional commit message from the staged diff and repository status.

What happens if the dotnet build or tests fail before committing?

The pre-commit checks surface build errors and test failures before any commit is created. You can fix the issues first, then re-run the workflow so only verified code enters the git history.