commit

Stage related files and create commits with pre-commit checks and release-aware updates.

2|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/jonaseck2/slaktforskning --skill commit-jonaseck2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/jonaseck2/slaktforskning/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/jonaseck2/slaktforskning --skill commit-jonaseck2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents broken or incomplete Git commits by enforcing a safe, consistent workflow for staging the right files and creating a commit message without missing required checks.

Core Features & Use Cases

  • Concern-based staging: stages all files for the current change so unrelated work-in-progress files are not accidentally included.
  • Pre-commit verification workflow: requires reviewing git status and cached diffs, then running lint/tests before committing to catch problems early.
  • Release-aware version bump guidance: applies the repo’s rules for when to bump src-tauri/package.json/tauri.conf.json and how to add the correct CHANGELOG.md entry.

Use case: after finishing a feature or fix (including docs, plans, and manifest updates), ask the AI to commit and it will help ensure the commit includes exactly the intended files and follows the project’s versioning and release conventions.

Quick Start

Use the commit skill when you are ready to commit changes for the current concern, and tell it a summary like: "Commit the completed work for this concern, include any needed version bump and changelog updates, and only stage the files related to these changes."

Frequently Asked Questions about commit

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

FAQPage Schema
How do I stage and commit only specific files in git without including unrelated work?

Concern-based staging ensures you stage and commit only files related to the current change, preventing unrelated work-in-progress files from being accidentally included in your git commit.

How do I create a reliable git commit workflow that runs lint and tests first?

A reliable git commit workflow requires reviewing git status and cached diffs, then running lint and tests before executing the commit to catch problems early and prevent broken commits.

When do I need to bump package.json versions and update the changelog before committing?

Version bumping and changelog updates are needed during plan-driven work when repository release rules require updating manifests like package.json or tauri.conf.json and adding correct CHANGELOG.md entries before committing.

How do I write a clear multi-paragraph git commit message for complex changes?

Composing a clear multi-paragraph commit message involves summarizing the completed work for a specific concern, detailing manifest updates, and ensuring the message aligns with the project's release conventions before executing the git commit.

Does this git commit workflow support Tauri desktop application release rules?

Yes, the workflow applies repo-specific release rules for Tauri projects, guiding when to bump src-tauri, package.json, and tauri.conf.json manifests and how to add the correct CHANGELOG.md entry before committing.