From tehik-dev-skills
Create a conventional git commit. Use this whenever the user says 'commit', 'stage and commit', 'make a commit', 'push my changes', or implies they are done with a task and want to save their work. Also trigger when the user asks to write a commit message or wants to understand how to format one.
How this skill is triggered — by the user, by Claude, or both
Slash command
/tehik-dev-skills:conventional-commitThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **Before you start:** Run `git status` to review what has changed. Do not stage or commit anything until you have reviewed the diff and selected the correct type.
Before you start: Run
git statusto review what has changed. Do not stage or commit anything until you have reviewed the diff and selected the correct type.
Follow the Conventional Commits standard.
git status
git diff --stat
git diff --staged
Read the actual diff content — --stat shows only file names, but understanding what changed is essential for writing a meaningful message body.
| Type | Use |
|---|---|
feat | New functionality |
fix | Bug fix |
docs | Documentation only |
refactor | Restructuring without functional change |
test | Adding or changing tests |
ci | CI/CD configuration |
chore | Dependency updates, build tooling |
perf | Performance improvement |
style | Code formatting |
revert | Reverting a previous commit |
Format:
<type>[(<scope>)]: <short description>
[optional body — explain WHY, not HOW]
[footer: BREAKING CHANGE: ... / Closes #123]
Breaking change shorthand — ! after the type (or type+scope) signals a breaking change and is equivalent to a BREAKING CHANGE: footer entry:
feat!: remove deprecated /api/v1 endpoint
feat(api)!: change response payload shape
Rules:
! shorthand and/or add BREAKING CHANGE: in the footer with migration notesExample:
feat(reports): add approval deadline calculation
Deadline is now calculated from submission date based on report type.
Weekends and public holidays are excluded from working day count.
Closes #42
# Preferred: add specific files (safer)
git add <file1> <file2> ...
# Alternative: when all changes are intended
git add .
⚠️ Before using
git add ., checkgit statusso you do not stage unwanted files (e.g..env, temporary files, build artifacts).
git commit -m "<type>(<scope>): <short description>"
For a longer commit message, use a heredoc:
git commit -m "$(cat <<'EOF'
<type>(<scope>): <short description>
[body — explain WHY]
[footer: Closes #123]
EOF
)"
If a pre-commit hook fails, the commit did not happen. Fix the issue, re-stage, and create a new commit — do not amend, as that would modify the previous commit instead.
git log --oneline -3
Report:
✅ Commit created:
- Message: <type>(<scope>): <short description>
npx claudepluginhub tehik-ee/ai-generic-skills --plugin tehik-dev-skillsProvides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.