Lore Framework Git Commits FAQs

Question 1

How does this skill help with semantic versioning?

Accepted Answer

By using specific types like 'feat' for minor updates and 'fix' for patches, and marking breaking changes with an exclamation mark (!), the skill ensures your commit history can be used to automate version bumps.

Question 2

What is a lore task reference?

Accepted Answer

A lore task reference is a unique ID (e.g., lore-0042) found in the 'lore/1-tasks/' directory that links a specific Git commit directly to the task it addresses for better project 'archaeology'.

Question 3

Why does the skill suggest using the imperative mood?

Accepted Answer

Using the imperative mood (e.g., 'add' instead of 'added') follows Git's own internal conventions and results in a more concise, readable, and action-oriented commit history.

Question 4

Can I use this skill if I'm not using the Lore Framework?

Accepted Answer

While the task reference feature is optimized for the Lore Framework, the conventional commit guidelines and formatting rules provided by the skill are beneficial for any standard Git-based project.

Question 5

What is the Lore Framework Git skill?

Accepted Answer

It is a specialized capability for Claude Code that helps developers write standardized Git commit messages following the Conventional Commits 1.0.0 specification integrated with Lore task references.

Lore Framework Git Commits

主な機能

ユースケース

Lore Framework Git Commits

主な機能

ユースケース