skills.rest
emiljuchnikowski
emiljuchnikowskiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

commit

Generate conventional commit messages from Linear tasks and staged git changes.

1|Updated Sep 15, 2023
Search Tags:#automation#git#devops#commit#linear#task-tracking#conventional-commits
One-click install
npx skills add https://github.com/emiljuchnikowski/smartsoft001 --skill commit-emiljuchnikowski
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/emiljuchnikowski/smartsoft001/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/emiljuchnikowski/smartsoft001 --skill commit-emiljuchnikowski

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of standardized commit messages by deriving content from Linear tasks and staged changes, removing guesswork and speeding up code reviews.

Core Features & Use Cases

  • Generate conventional commit messages (type(scope): subject) from Linear task details and git changes.
  • Ensure Refs: <linearTaskId> is included for traceability in issue trackers.
  • Fits into CI pipelines and local development workflows to maintain consistent history.

Quick Start

Provide the Linear task ID and run the commit skill to generate a ready-to-commit message.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate conventional commit messages from Linear tasks and staged git changes?▼

Conventional commit messages follow the type(scope): subject format to standardize git history and automate changelog generation. Using a task tracker like Linear provides the context needed to derive the scope and subject from the actual development work.

How to include a Linear task ID reference in a conventional commit message?▼

To include a Linear task ID reference, the commit message must append a line containing Refs: <linearTaskId>. This links the git history directly to the issue tracker, ensuring traceability between code changes and project management tasks.

Can I automate git commit message creation in CI pipelines using Linear task details?▼

Yes, you can automate commit message creation in CI pipelines and local development workflows by deriving the message content from Linear tasks and git diffs. This removes guesswork and maintains consistent version control history across automated environments.

What do I need to provide to automatically draft a conventional commit from a Linear task?▼

You need to provide the Linear task ID and ensure your git changes are staged. The commit skill reads both the Linear task details and the git diff of staged changes to scope and draft the final conventional commit message.

Does automating conventional commits with Linear task tracking work without manual editing?▼

Automating conventional commits with Linear task tracking produces a ready-to-commit message that reflects both the task details and staged changes. It is designed to remove guesswork and speed up code reviews without requiring manual message drafting.

Related Skills

Explore More Software Engineering Skills→
zapierzapier
373

Git Commit

Generate Conventional Commits with Jira context and push changes.

Official
Advanced
u9401066u9401066

git-pusher

Automate Git commit, push, and CI workflow triggering with pre-push validation.

Community
Intermediate
auldsyababuaauldsyababua
6

Update Linear Post-Job

Mark child Linear issues as Done and update parent work blocks.

Community
Intermediate
kirvinkirvin

commit

Stage Git changes and create conventional commit messages with preflight checks.

Community
Intermediate