commit

Create conventional git commit messages from staged changes with Linear ticket IDs.

2|Updated Nov 15, 2025
One-click install
npx skills add https://github.com/kristofferremback/threa --skill commit-kristofferremback
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/kristofferremback/threa/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/kristofferremback/threa --skill commit-kristofferremback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual process of writing git commit messages and handles sandbox limitations, ensuring consistent, professional commit history without manual effort.

Core Features & Use Cases

  • Automated Commit Creation: Generate properly formatted commits with conventional commit standards.
  • Sandbox Workarounds: Bypass heredoc limitations in restricted environments.
  • Use Case: After making multiple code changes, use this Skill to automatically create a well-structured commit with proper attribution, saving you from manual message writing.

Quick Start

Use the commit skill to stage and commit the changes to README.md and src/utils.ts with a message about fixing authentication bugs.

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 with conventional commits format?

Automated commit message generation creates properly formatted commits following conventional commit standards from your staged changes. This Skill inspects git status and diffs, writes formatted messages to a temp file, and commits with proper attribution, eliminating manual message composition while ensuring consistency across your repository history.

Can I extract Linear ticket IDs from branch names into commit messages?

Yes. This Skill extracts Linear ticket IDs present in your branch name and automatically includes them in the generated commit message, linking your commits to tracked issues without manual entry.

How do I commit multiple staged files with a single formatted message?

Stage the files you need, then use this Skill to inspect all staged changes, generate a single formatted commit message covering the modifications, and commit them together with proper attribution and conventional commit structure applied.

Does this work in restricted sandbox environments with heredoc limitations?

Yes. This Skill bypasses heredoc limitations common in restricted sandbox environments by writing commit messages to temporary files and using the -F flag, enabling automated commits where standard multi-line message approaches fail.

What format do commit messages follow when auto-generated?

Generated commit messages follow conventional commits standards, ensuring structured, machine-readable commit history with proper prefixes, scopes, and descriptions that improve clarity and enable automated changelog generation.

Can I use this Skill to enforce consistent commit history across my team?

Yes. By automating commit message formatting and enforcing conventional commits standards, this Skill eliminates inconsistency in message style and structure, ensuring all commits meet professional standards without manual review or correction.