skills.rest
krystophny
krystophnyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

commit

Create conventional git commits from explicitly staged files after tests pass.

Updated Aug 23, 2026
Search Tags:#automation#git#workflow#testing#commit#code-review#conventional-commits
One-click install
npx skills add https://github.com/krystophny/prompts --skill commit-krystophny
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/krystophny/prompts/tree/main/skills/commit
Command: npx skills add https://github.com/krystophny/prompts --skill commit-krystophny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces safe, reproducible commits by ensuring changes are explicitly staged and that tests pass before committing, reducing the risk of leaking secrets or breaking builds.

Core Features & Use Cases

  • Explicit staging: Only files you select are included in the commit.
  • Test guardrails: Runs tests and blocks commits if failures occur.
  • Conventional messaging: Creates standardized commit messages with types like fix, feat, and chore.
  • Use Case: When finishing a bug fix, you commit with a compliant message after verifying tests pass.

Quick Start

Provide an optional message to /commit and rely on the tool to generate a compliant commit after tests pass and files are explicitly staged.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate git commits to only include explicitly staged files?▼

Automating git commits with explicit staging ensures only selected files are committed. This skill enforces explicit file selection and validates tests before creating a commit, preventing unintended changes from entering your repository history.

Can I block git commits if tests fail during CI workflows?▼

Blocking git commits when tests fail is supported by running test validation before staging. If tests fail, the commit process stops entirely, ensuring broken code or failing validations do not pollute your predictable git history.

How do I generate conventional commit messages for bug fixes and features?▼

Generating conventional commit messages for bug fixes and features requires applying standard types like fix, feat, and refactor. This skill automatically formats your commit messages to comply with conventional commits standards for strict commit hygiene.

What is the best way to prevent committing secrets into a git repository?▼

Preventing secrets from entering a git repository involves enforcing strict commit guardrails. This skill applies rules to never commit secrets and only stages explicitly selected files, reducing the risk of leaking sensitive data during automation.

Does this automated commit tool work for software repositories needing strict commit hygiene?▼

This automated commit tool works directly for software repositories requiring strict commit hygiene. It applies to CI workflows where bug fixes, features, or refactors need predictable history and compliant commit messages.

Related Skills

Explore More Software Engineering Skills→
jk278jk278

git-analyzer

Analyze git repositories to summarize commit history and file changes.

Community
Intermediate
sumrae412sumrae412
2

shipping-workflow

Automate conventional commits, pull requests, and 10-step code review before merging.

Community
Advanced
burgebjburgebj

ship

Automate testing, code review, pull request creation, and deployment workflows.

Community
Advanced
toilahuonggtoilahuongg
10

git-cm

Commit staged or unstaged git changes with conventional commit messages.

Community
Basic