commit

Review changes, lint/format files, and create an English commit message.

9|Updated Dec 21, 2016
One-click install
npx skills add https://github.com/ysoftman/myenv --skill commit-ysoftman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/ysoftman/myenv/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/ysoftman/myenv --skill commit-ysoftman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review changes, lint/format, then create a git commit with an English message, streamlining the commit workflow and ensuring consistent messaging.

Core Features & Use Cases

  • Review status and diffs to understand changes
  • Run lint/format on modified files with controlled rules
  • Generate an English commit message within 70 characters
  • Validate remote origin and scan for sensitive data when the repository is public (non-pushing safety)

Quick Start

Initiate the commit workflow by reviewing changes, applying lint/formatting, and creating an English commit message for the current branch.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate git commit message generation and linting before saving changes?

Automating git commit message generation and linting involves reviewing staged diffs, applying formatting rules, and generating a concise English message. This Skill automates that workflow by checking status, running lint and format on modified files, and producing a commit message under 70 characters.

What is the best way to generate English commit messages automatically from git diffs?

Generating English commit messages automatically from git diffs requires analyzing file changes and summarizing them concisely. This Skill reviews your git status and diffs, then creates an English commit message within 70 characters while enforcing lint and formatting rules before finalizing.

Does this automated commit workflow scan for sensitive data in public repositories?

Yes, this automated commit workflow scans for sensitive data in public repositories. It validates the remote origin and performs a safety scan to prevent pushing sensitive information when the repository is public, adding a non-pushing safety layer before finalizing the commit.

Can I use this to run lint and format checks only on modified files before committing?

Yes, you can use this to run lint and format checks specifically on modified files before committing. The workflow reviews the current changes and applies strict linting and formatting rules exclusively to the modified files before generating the commit message and finalizing.

What limitations exist when enforcing strict linting rules before a git commit?

A key limitation when enforcing strict linting rules before a git commit is that the process is deterministic and halts if linting or formatting fails. Additionally, it restricts commit messages to 70 characters and will block the commit if the safety scan detects sensitive data in a public repository.

How do I start the commit workflow using keywords like git ci or 커밋?

To start the commit workflow, you trigger the process using recognized keywords like 커밋, git commit, or git ci. Once initiated, the Skill automatically reviews changes, applies lint and formatting, scans for sensitive data, and generates the English commit message for the current branch.