skills.rest
Oskarovsky
OskarovskyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

sprint-commit

Creates conventional commit messages and commits staged feature changes with git.

Updated May 20, 2026
Search Tags:#git#code review#version control#commit#conventional commits#feature workflow
One-click install
npx skills add https://github.com/Oskarovsky/Sprinter --skill sprint-commit-oskarovsky
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sprint-commit
Source: https://github.com/Oskarovsky/Sprinter/tree/main/project-skills/sprint-commit
Command: npx skills add https://github.com/Oskarovsky/Sprinter --skill sprint-commit-oskarovsky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, well-formatted commit messages for completed feature work is repetitive and often inconsistent across a team. This Skill reviews your working tree changes and produces a conventional commit message before committing. ## Core Features & Use Cases - Change Review: Inspects the working tree with git status and git diff to understand what was modified. - Conventional Commit Messages: Proposes a commit message following the conventional commit format that references the feature name. - User Confirmation: Shows the proposed message for approval before staging and committing. - Use Case: After finishing a login feature, ask the assistant to commit the work; it reviews the diff, proposes "feat: add user login flow", and commits after your confirmation. ## Quick Start Ask the assistant to commit the changes for the feature you just implemented and provide the feature name when prompted.

Frequently Asked Questions about sprint-commit

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

FAQPage Schema
How do I write a conventional commit message for a feature?▼

A conventional commit message uses a type prefix like feat or fix followed by a short summary, such as "feat: add password reset flow". This Skill generates the message automatically by reviewing your git diff and referencing the feature name you provide.

How to commit staged and unstaged changes with git?▼

Use git status and git diff to review modifications, then git add to stage files and git commit to record them. This Skill performs that full sequence after you confirm the proposed commit message.

Can I review the commit message before it is committed?▼

Yes. The Skill proposes a commit message and explicitly asks for your confirmation before running git add and git commit, so nothing is committed without your approval.

What git commands does this commit workflow run?▼

It runs git status and git diff to review changes, then git add to stage them and git commit with the approved message. It finally shows you the commit result for verification.

When should I not use an automated commit workflow?▼

Avoid it when the working tree contains unrelated changes mixed together, since everything gets staged and committed under one message. Split unrelated work into separate commits manually first.

Related Skills

Explore More Software Engineering Skills→
jtucker9jtucker9

verify

Verify completed work with automated build, test, and lint checks before committing.

Community
Advanced
tachiiri-orgtachiiri-org

release

Create a pull request from the dev branch to main after verifying branch and remote state.

Official
Intermediate
DataDogDataDog
648

lint

Run Hatch-based lint, format, and quality checks on modified files.

Official
Advanced
laicluselaicluse
4

commit-all-the-things

Groups all uncommitted git changes into logical commits with descriptive messages.

Official
Intermediate