commit

Run pre-commit scans and generate conventional commit messages for git.

5|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/namanchopra/branchwater --skill commit-namanchopra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/namanchopra/branchwater/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/namanchopra/branchwater --skill commit-namanchopra

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, typescript, eslint, prettier, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a disciplined approach to committing code, mitigating risks of leaked secrets, broken builds, and lost work by enforcing a series of checks and best practices.

Core Features & Use Cases

  • Commit Verification: Conducts a thorough safety scan, including secrets detection, conflict markers, and debug artifact scanning.
  • Quality Checks: Runs TypeScript type checks, ESLint, and Prettier to ensure code quality.
  • Conventional Commit Messages: Automatically generates intelligent commit messages with scope detection from branch names and file paths.
  • Explicit File Staging: Enforces explicit staging of files to prevent accidental commit of sensitive information.

Quick Start

Invoke the /commit command or when prompted to commit, and follow the intelligent prompts to ensure a secure and effective commit.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate secure git commits with code quality and secrets detection?

Automate secure git commits by running pre-commit scans for secrets and debug artifacts, enforcing ESLint, Prettier, and TypeScript checks, and generating conventional commit messages with explicit file staging to prevent accidental sensitive data leaks.

How do I generate conventional commit messages automatically from branch names and file paths?

Generate conventional commit messages automatically by detecting scope from branch names and staged file paths. This ensures consistent version control history while enforcing strict file staging discipline to prevent accidental commits.

Do I need TypeScript, ESLint, and Prettier configured to run automated commit checks?

Yes, you need TypeScript, ESLint, and Prettier configured in your project. The automated commit process relies on these dependencies to execute type checks, lint code, and format files before generating a secure commit.

What is the best way to prevent accidental commits of sensitive information in git?

The best way to prevent accidental commits of sensitive information is to enforce explicit file staging. This requires manually selecting specific files for staging, while a pre-commit scan detects leaked secrets, conflict markers, and debug artifacts.

Can I run security checks and code quality scans before staging files for a git commit?

Yes, you can run security checks and code quality scans before staging. The process performs a comprehensive pre-commit safety scan that detects secrets and debug artifacts, runs TypeScript type checks, and validates code with ESLint and Prettier.

Why does my automated commit fail when debug artifacts or conflict markers are detected?

Automated commits fail when debug artifacts or conflict markers are detected to maintain code quality and prevent broken builds. The pre-commit safety scan blocks the commit process until these issues are resolved and files pass TypeScript, ESLint, and Prettier checks.