commit-work

Automate conventional commit messages with patch-based staging and secret checks.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Nymbo/Skills --skill commit-work
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-work
Source: https://github.com/Nymbo/Skills/tree/main/commit-work
Command: npx skills add https://github.com/Nymbo/Skills --skill commit-work

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Helps create focused, well-described commits using Conventional Commits.

Core Features & Use Cases

  • Staging & boundaries: Decide commit boundaries.
  • Message quality: Write clear messages following Conventional Commits.
  • Verification: Run small checks.

Quick Start

Use this skill to craft a well-scoped commit history for a feature or fix.

Frequently Asked Questions about commit-work

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

FAQPage Schema
How do I write better commit messages following Conventional Commits?

Conventional Commits is a specification for adding structured meaning to commit messages. It uses a format like `type(scope): description` to make commits machine-readable and easier to scan. This Skill automates message creation to ensure your commits follow the standard, improving clarity and enabling automated changelog generation.

What's the best way to decide what changes belong in a single commit?

Commit boundaries should reflect logical units of work—one feature, one fix, or one refactor per commit. This Skill helps you stage and review changes precisely, supports patch-based staging to split work across multiple commits, and guides you through boundaries so your history stays focused and reviewable.

Can I stage only specific changes instead of committing everything at once?

Yes. Patch-based staging lets you commit specific hunks or files rather than all changes at once. This Skill supports staging workflows, helps you review diffs before committing, and ensures only intended changes are included—preventing accidental commits of unrelated work or sensitive data.

How do I avoid committing secrets or tokens by mistake?

This Skill runs checks to detect secrets or tokens in staged changes before creating a commit. It flags sensitive content, helping you catch and remove credentials, API keys, or other secrets before they enter the repository history.

Why should I use a structured commit history?

A minimal, well-described commit history makes code review easier, enables automated tooling like changelog generation and semantic versioning, and helps future developers understand *why* changes were made. This Skill enforces structure so your history remains review-friendly and actionable.