feat: add commit skill for conventional commit messages

[feloy]

Adds a new skill that helps generate conventional commit messages based on git changes. The skill analyzes git status, diff, and recent commit history to suggest well-structured commit messages following the project's conventions.

Closes #55

[coderabbitai]

Warning

Rate limit exceeded

@feloy has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 10 minutes and 32 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 2157e5fd-dfc1-4816-9798-b438ffbadd85

📥 Commits

Reviewing files that changed from the base of the PR and between 389a0ee and e7979dd.

📒 Files selected for processing (3)

• .claude/skills/commit
• skills/README.md
• skills/commit/SKILL.md

📝 Walkthrough

Walkthrough

Introduces a new "commit" skill that generates conventional commit messages from staged changes. Includes a reference pointer, README documentation entry, and comprehensive skill documentation with format specifications, guidelines, and examples. No functional code changes.

Changes

Cohort / File(s)	Summary
Skill Registration .claude/skills/commit, skills/README.md	Adds a reference pointer to the commit skill and documents it in the skills registry as a tool for generating conventional commit messages.
Skill Documentation skills/commit/SKILL.md	Comprehensive documentation covering the skill's purpose, conventional commit format, commit types with semantic version implications, scoped keywords, guidelines for subject/scope/body/footer construction, step-by-step process workflow, examples of various commit scenarios, and usage instructions.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'feat: add commit skill for conventional commit messages' accurately and concisely describes the main change—adding a new commit skill for generating conventional commit messages.
Description check	✅ Passed	The description explains the skill's purpose (generating conventional commit messages from git changes) and clearly relates to the changeset, including the issue closure reference.
Linked Issues check	✅ Passed	The PR implements the core requirement from issue #55 by adding a commit skill with documentation and setup that enables autonomous commit generation following conventional commit formats.
Out of Scope Changes check	✅ Passed	All changes (new commit skill setup file, README entry, and SKILL.md documentation) directly support the stated objective of adding a commit skill without introducing unrelated modifications.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@skills/commit/SKILL.md`:
- Around line 135-138: Replace the hardcoded "Co-Authored-By: Claude Code
(Claude Sonnet 4.5) <noreply@anthropic.com>" trailer in SKILL.md with
logic/instructions to derive the trailer from the current agent metadata (agent
name and agent noreply email) or to prompt the user to confirm/enter the
co-author info when agent metadata is unavailable; update the examples and
heredoc snippet that reference this trailer (the occurrences around the existing
Co-Authored-By lines) to use a placeholder like "<current agent name> <agent
noreply email>" and add a short note instructing implementers to populate that
placeholder from the runtime agent metadata or via explicit user confirmation.
- Around line 38-45: Update the skill to base its analysis on the index (staged
changes) rather than the working tree: replace uses of `git diff HEAD`/`git
diff` in the SKILL.md examples and checks with `git diff --cached`/`git diff
--cached --stat` (or equivalent) and change the user-facing messages to indicate
"staged" vs "no staged changes"; if nothing is staged, have the skill explicitly
ask the user which files to stage before composing the commit message instead of
proceeding; and stop using a blanket `git add -A` in the workflow—replace that
step with instructing the agent to run `git add` only on the user-approved files
(e.g., the files the user selected to include in the commit).

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 700032ef-a4ea-40fa-b55a-27774bf337e3

📥 Commits

Reviewing files that changed from the base of the PR and between 6dcec2e and 389a0ee.

📒 Files selected for processing (3)

• .claude/skills/commit
• skills/README.md
• skills/commit/SKILL.md

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!