commit

Commit staged Git changes and update Todoist tasks interactively.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/swat9013/dotfiles --skill commit-swat9013
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/swat9013/dotfiles/tree/main/.claude-global/skills/commit
Command: npx skills add https://github.com/swat9013/dotfiles --skill commit-swat9013

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes scripts (resource) components.

What problem does it solve?

This Skill streamlines committing staged Git changes and keeps task tracking in sync by automating repository state checks, generating convention-aware commit messages, suggesting documentation updates, and updating Todoist tasks.

Core Features & Use Cases

  • Prepare and Inspect Changes: Runs a pre-commit inspection to detect staged, unstaged, and untracked files and produces diff stats and recent commit context.
  • Commit Message Generation: Analyzes diffs and recent commits to propose a concise, convention-aware commit message that the user can review and edit.
  • Documentation & Task Sync: Suggests updates to README/CLAUDE.md/docs when relevant and integrates with Todoist to close or add tasks related to the commit.
  • Use Case: When finishing a feature branch, use this workflow to ensure commits follow project conventions, update necessary docs, and close associated Todoist tasks in one interactive flow.

Quick Start

Run the commit workflow to prepare changes, review or edit the proposed commit message, create the commit, and optionally close or add related Todoist tasks.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate git commit messages and sync Todoist tasks?

To automate git commit messages and sync Todoist tasks, run the workflow to inspect staged changes, generate convention-aware messages, create the commit, and close or add related Todoist tasks.

What's the best way to generate conventional commit messages from staged git changes?

Generating conventional commit messages from staged git changes is done by analyzing file diffs and recent commit context to propose a concise message you can review and edit before committing.

Does this commit workflow check for documentation updates before committing?

Yes, the commit workflow checks for documentation updates by suggesting changes to README, CLAUDE.md, or docs files when relevant to your staged git changes before finalizing the commit.

Do I need Todoist credentials configured to use this git commit workflow?

You need Todoist credentials or configuration if you want to manage tasks, as the workflow requires them to perform task list and close or add operations during your local git commit process.

Can I use this workflow to inspect untracked and unstaged files before committing?

Yes, you can use this workflow to inspect untracked and unstaged files, as it runs a pre-commit inspection to detect all file states and produces diff stats before staging and committing.

What are the limitations of automating commits with local git scripts?

Automating commits with local git scripts requires access to a local Git working tree and repository, limiting the workflow to local environments rather than remote or cloud-based git operations.