skills.rest
juxt
juxtOFFICIAL
Explore all skills by this author →
Website𝕏@juxtproGitHub

commit

Generate context-rich git commit messages with Chalk issue links.

10|6|Updated Feb 8, 2026
Search Tags:#git#commit#chalk#issue-tracking#version-control#commit-message#code-changes
One-click install
npx skills add https://github.com/juxt/claude-plugins --skill commit-juxt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/juxt/claude-plugins/tree/main/plugins/chalk/skills/commit
Command: npx skills add https://github.com/juxt/claude-plugins --skill commit-juxt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing git commit messages that lack context about why changes were made leads to hard-to-navigate version history, especially for teams using issue tracking systems like Chalk. Inconsistent commit voice and bundled unrelated changes make code reviews and historical debugging more time-consuming.

Core Features & Use Cases

  • Atomic Change Staging: Automatically stages only files related to the current commit, separating unrelated bugfixes, refactors, and feature changes to enable independent merges.
  • Context-Aware Commit Drafting: Creates commit bodies that explain decision rationale, rejected alternatives, and constraints (not just what changed) using the project's Chalk explanatory voice.
  • Issue Tracking Integration: Links commits to associated GitHub issues via subject line suffixes and body footers, and updates Chalk issue comments with commit outcomes automatically.
  • Use Case: A developer working on a Chalk-tracked bug fix uses this skill to stage only the modified logic files, draft a commit body explaining why the fix was chosen over alternative approaches, link the commit to the related GitHub issue, and update the Chalk issue comment with the final commit details.

Quick Start

Use the commit skill to create a git commit for your current changes with a contextual body explaining the reasoning behind the work, aligned to your project's Chalk voice conventions.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I write git commit messages that explain the reasoning behind code changes?▼

To generate context-rich git commit messages, you draft commit bodies that explain decision rationale, rejected alternatives, and constraints rather than just listing modified files. This ensures version history captures why changes were made, improving code reviews and historical debugging.

What is the best way to stage atomic git commits for unrelated code changes?▼

Staging atomic git commits involves separating unrelated bugfixes, refactors, and feature changes so each represents an independent, standalone modification. This enables independent merges and prevents bundled changes from cluttering project version history.

Can I link git commits to GitHub issues for issue tracking?▼

Yes, you can link git commits to GitHub issues by appending subject line suffixes and body footers referencing the associated issue. This issue tracking integration automatically updates issue comments with the final commit outcomes and details.

Does the commit skill work with Chalk for GitHub issue tracking?▼

Yes, the commit skill works with Chalk for GitHub issue tracking by applying a project-specific Chalk explanatory voice to commit bodies and automatically updating Chalk issue comments with the final commit outcomes and details.

Why do my git commit messages fail to follow project formatting conventions?▼

Git commit messages fail formatting conventions when they omit mandatory co-author headers, line-per-paragraph body structure, or project-specific explanatory voice. Adhering to these formatting rules ensures commits meet required project standards for version control.

When should I not bundle unrelated bugfixes and features into a single git commit?▼

You should not bundle unrelated bugfixes, refactors, and features into a single git commit when independent merges are required. Bundling obscures decision rationale and hinders historical debugging within version control history.

Related Skills

Explore More Software Engineering Skills→
CivicActionsCivicActions
2

commit-message-writer

Generate standardized git commit messages from diff context and project conventions.

Official
Intermediate
MohibShaikhMohibShaikh
11

commit

Stage changes, create a contextual commit message, and push the current branch.

Community
Intermediate
SingularGuyLeBornSingularGuyLeBorn

github-assistant

Manage GitHub repositories, pull requests, issues, and workflows via API.

Community
Intermediate
dbensmithdbensmith

git-commit

Automate git commits with conventional message analysis and intelligent file staging.

Community
Intermediate