skills.rest
az9713
az9713COMMUNITY
Explore all skills by this author →
GitHub

piv-commit

Creates a git commit for all uncommitted changes with a conventional-commit message.

Updated Aug 28, 2026
Search Tags:#automation#git#version control#commit#conventional commits#git status#code workflow
One-click install
npx skills add https://github.com/az9713/claude-code-hooks-tutorial --skill piv-commit-az9713
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: piv-commit
Source: https://github.com/az9713/claude-code-hooks-tutorial/tree/main/skills/.claude/skills/piv-commit
Command: npx skills add https://github.com/az9713/claude-code-hooks-tutorial --skill piv-commit-az9713

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, well-tagged commit messages for every batch of uncommitted changes is repetitive and often skipped, leaving git history unclear. This Skill automates the full commit flow so every change lands as an atomic, conventionally-tagged commit. ## Core Features & Use Cases - Automated Commit Workflow: Runs git status and diff, stages untracked and modified files, and commits them in one pass. - Conventional Commit Messages: Generates atomic messages tagged with feat, fix, docs, refactor, test, or chore based on the actual changes. - Project Convention Awareness: Reads .claude/references/conventions.md when present so project-specific commit rules override the defaults. - Post-Commit Summaries: Prints a What Changed paragraph plus an AI Layer Changes section whenever files under .claude/ were modified. - Use Case: After finishing a feature branch with mixed staged and untracked files, invoke the skill to produce a single clean commit like "feat: add retry logic to API client" with a reviewer-ready summary. ## Quick Start Ask the assistant to commit all current uncommitted changes with an appropriate conventional commit message.

Frequently Asked Questions about piv-commit

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

FAQPage Schema
How do I commit all uncommitted git changes with a conventional commit message?▼

Invoke the skill after finishing your work. It runs git status and git diff, stages untracked and changed files, then writes an atomic message tagged feat, fix, docs, refactor, test, or chore based on the actual changes.

How to enforce project-specific commit message conventions?▼

Create a .claude/references/conventions.md file with a commit section describing your rules. The skill reads that file first and lets those project-specific rules override its default conventional-commit behavior.

Does this skill handle untracked files when committing?▼

Yes. The workflow explicitly checks git status --porcelain for untracked files and adds both untracked and modified files before creating the commit, so nothing is left out of the changeset.

What output does the skill produce after a git commit?▼

It prints a What Changed paragraph summarizing the committed work for someone skimming the git log. If any files under .claude/ changed, it also lists an AI Layer Changes section describing each modified AI configuration file.

When should I not use an automated commit skill?▼

Avoid it when changes span multiple unrelated concerns that deserve separate atomic commits, or when you need interactive staging of specific hunks. The skill commits everything uncommitted as a single unit.

Related Skills

Explore More Software Engineering Skills→
trevin-jtrevin-j
6

git-basics

Run tests, linters, and static analysis before committing with Conventional Commits.

Community
Intermediate
sumrae412sumrae412
2

shipping-workflow

Automate conventional commits, pull requests, and 10-step code review before merging.

Community
Advanced
TrevorPLamTrevorPLam

pre-commit-guard

Run lightweight linting and secret scans on staged files before Git commits.

Community
Intermediate
paywherebpaywhereb

squash

Squash all branch commits into one via interactive git rebase.

Official
Intermediate