piv-commit
/piv-commit
Creates a new git commit for all uncommitted changes with an atomic, conventionally-tagged message. Use when work is complete and ready to be committed.
- Author
- coleam00 ↗
- Repository
- skills ↗
- Licence
- MIT
- Last repository change
- 07.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 07.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Creates a new git commit for all uncommitted changes with an atomic, conventionally-tagged message. Use when work is complete and ready to be committed.
Original author description
Creates a new git commit for all uncommitted changes with an atomic, conventionally-tagged message. Use when work is complete and ready to be committed.
How it works
- Process
- Output
SKILL.md preview
--- name: piv-commit description: Creates a new git commit for all uncommitted changes with an atomic, conventionally-tagged message. Use when work is complete and ready to be committed. --- # Commit: Create a New Commit Create a new commit for all of our uncommitted changes. ## Process 0. **Read this project's conventions.** If `.claude/references/conventions.md` exists, read its `## commit` section and follow it — those rules win over the defaults below. That file is where a project's specifics live; this skill stays general. 1. Run `git status && git diff HEAD && git status --porcelain` to see what files are uncommitted. 2. Add the untracked and changed files. 3. Write an atomic commit message with an appropriate, descriptive summary. 4. Add a tag such as `feat`, `fix`, `docs`, `refactor`, `test`, `chore`, etc. that reflects our work. ## Output A single commit containing all uncommitted changes, with a conventional-commit-style message (`<tag>: <atomic description>`) that accurately reflects the work done. After the commit succeeds, print two clearly labelled summaries: ### What Changed One short paragraph (3–6 sentences) describing the feature/fix/refactor that was committed — what problem it solves and what files were the key touch points. Write for a developer skimming the git log. ### AI Layer Changes Only include this section if any files under `.claude/` were modified or added (CLAUDE.md, `.claude/references/`, `.claude/skills/`, `.claude/agents/`, etc.). List each changed AI-layer file with a one-line note on what evolved and why. If nothing in `.claude/` changed, omit this section entirely.
Versions
The database has no other skills named piv-commit.
Database snapshot: 13.11.2026 · package version 294e8723c609 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100commit
Use when creating a git commit — the user asks to commit, or a unit of work is complete and ready to commit. - 96commit
Use when writing a commit message, or before running `git commit`. - 100commit
Write a commit message and create a git commit. Use when the user wants to commit changes, asks for a commit message, or says "commit this" or "make a commit". - 96commit
Creates atomic conventional git commits using git-agent. This skill should be used when the user requests "commit", "git commit", "create commit", or wants to commit changes using AI atomic commits. - 84generate-commit-message
Generate well-structured git commit messages. Use when user says "generate commit message", "write a commit", "what should my commit message be", "create commit message for these changes", or needs help crafting conventional commit messages. - 100ce-commit
Create a git commit with a clear, value-communicating message. Use when the user asks to commit/save staged or unstaged changes with a repo-appropriate message.