commit

Name: commit
Availability: InStock
Author: UXname

Run npm checks, stage changes, and create conventional git commits.

30|3|Updated Mar 8, 2020

Search Tags:#automation #git #commit #pre-check #lint #conventional-commits

Ready to run

npx skills add https://github.com/uxname/liteend --skill commit-uxname

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/uxname/liteend/tree/main/.agents/skills/commit
Command: npx skills add https://github.com/uxname/liteend --skill commit-uxname

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the process of committing code changes to a git repository, ensuring that quality checks are run before a commit is created.

Core Features & Use Cases

Runs npm run check before committing to catch lint/typing/build errors.
Stages all changes and writes a conventional, scoped commit message.
Provides guardrails for pre-commit hooks and recoverable failures during the commit process.

Quick Start

Ask me to commit changes and I will perform checks, stage changes, and create a properly formatted commit message.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I automate a git commit with lint and pre-checks?▼

Automating a git commit with lint and pre-checks involves running npm run check to catch errors, staging all changes with git add -A, and composing a conventional commit message before executing git commit.

Can I generate conventional commit messages automatically?▼

Yes, you can generate conventional commit messages automatically. This skill composes a scoped conventional commit message based on your staged changes, ensuring your git history follows standardized conventional-commits formatting without manual effort.

What happens if pre-commit hooks fail during the commit process?▼

If pre-commit hooks fail during the commit process, this skill handles the recoverable failures by invoking the /check skill. This provides guardrails to manage pre-commit hook failures without aborting the entire workflow.

Do I need to run npm run check separately before staging changes?▼

No, you do not need to run npm run check separately before staging changes. This skill implements a deterministic workflow that automatically runs the check, stages all changes with git add -A, and commits in sequence.

How to handle unstaged changes when committing to a git repository?▼

To handle unstaged changes when committing to a git repository, this skill automatically stages all modifications using git add -A. It ensures no changes are left behind before generating a conventional commit message and executing the commit.