commit

Create conventional git commits and resolve pre-commit hook failures in TypeScript repositories.

2|Updated Mar 27, 2019
One-click install
npx skills add https://github.com/silcam/lessons-from-luke --skill commit-silcam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/silcam/lessons-from-luke/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/silcam/lessons-from-luke --skill commit-silcam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you turn in-progress work into clean, standards-compliant git commits without tripping over pre-commit validation.

Core Features & Use Cases

  • Conventional Commit Creation: Builds commit messages that follow the expected type, subject, and body format.
  • Hook Failure Recovery: Guides you through common pre-commit failures such as lint, type-check, test, and message-length errors.
  • TypeScript Workflow Support: Tailored for repositories that use commitlint, husky, formatting, and automated checks.
  • Use Case: After finishing a feature branch, use this Skill to stage the right files, write a compliant commit message, and fix hook issues before retrying.

Quick Start

Use the commit skill to review my changes, stage the correct files, and create a conventional commit message that will pass the project hooks.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I create conventional commits that pass husky pre-commit hooks?

To create conventional commits that pass husky pre-commit hooks, you must explicitly stage files and format the commit type, subject, and body to satisfy commitlint line-length rules before triggering validation checks.

Why does my pre-commit hook fail during TypeScript type checks and linting?

Pre-commit hook failures during TypeScript type checks and linting occur when staged files contain formatting issues or type errors, requiring you to resolve these specific errors before the commit can succeed.

How do I fix commitlint errors for commit message line-length?

To fix commitlint errors for commit message line-length, adjust the commit subject and body so that header lines stay within the configured character limit before retrying the git commit.

Can I use this commit workflow for repositories without commitlint and husky?

This commit workflow is tailored for TypeScript repositories that use commitlint and husky for formatting, lint checks, type checks, and test validation, so it is not optimized for repositories lacking these tools.

What is the best way to resolve test validation failures in pre-commit hooks?

The best way to resolve test validation failures in pre-commit hooks is to troubleshoot the failing test errors directly, fix the underlying code issues, and then retry the commit process to pass the automated checks.