Automate standardized git commits with Conventional Commits format and diff-derived type, scope, and subject.
npx skills add https://github.com/nghiahsgs/taw-kit --skill taw-commit
Please help me install this Agent Skill. Skill: taw-commit Source: https://github.com/nghiahsgs/taw-kit/tree/main/skills/taw-commit Command: npx skills add https://github.com/nghiahsgs/taw-kit --skill taw-commit
Automates and standardizes commits for taw-kit projects by enforcing conventional commit structure, deriving type/scope/subject from diffs, and emitting a taw-branded commit message. This reduces human error, accelerates release notes, and ensures consistent history across builds.
Run taw-commit after making changes to generate and apply a compliant commit message.
High-intent search queries and answers about installing and using this skill.
To automate git commit messages from a diff, use a diff-aware commit helper that analyzes your changes to derive the type, scope, and subject automatically. This enforces conventional commit formats and reduces human error when standardizing project history.
The conventional commits format for automated releases structures commit messages with a specific type, scope, and subject, often including optional phase trailers like [P<n>]. This standardization accelerates release notes and ensures consistent history across builds.
To scrub secrets before committing code changes, use an automated commit helper that checks and removes sensitive data from diffs prior to finalizing the commit. This prevents accidental leakage of credentials in your version control history.
Yes, you can generate ad-hoc commit messages without orchestrator context by operating in SMART mode. This mode derives the type, scope, and subject directly from your current diffs, allowing you to create compliant conventional commits independently.
To attach phase tags to commit messages, use a context-aware commit mode that reads phase information from a checkpoint JSON file. This automatically includes optional [P<n>] phase trailers in your conventional commit messages based on the orchestrator's current state.
forgivesam168Analyze diffs and stage changes to generate conventional git commit messages.
BaGyun0107Generate Conventional Commits messages from code diffs.
nghiahsgsImplement Supabase passwordless email magic-link authentication for taw-kit projects.
RoentekStage the git working tree and generate a Conventional Commits message.
