git-commit

Creates scoped Conventional Commits after staged-diff review and verification gates.

Updated Sep 16, 2026
One-click install
npx skills add https://github.com/PT-Perkasa-Pilar-Utama/axentra --skill git-commit-pt-perkasa-pilar-utama
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/PT-Perkasa-Pilar-Utama/axentra/tree/main/.claude/skills/git-commit
Command: npx skills add https://github.com/PT-Perkasa-Pilar-Utama/axentra --skill git-commit-pt-perkasa-pilar-utama

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Committing code without reviewing the staged diff or running verification often leads to broken builds, leaked secrets, and out-of-scope changes landing in the repository. This Skill enforces a disciplined pre-commit workflow so every Axentra commit is scoped, verified, and safe. ## Core Features & Use Cases - Staged-Diff Review: Inspects git status, diff stats, and the exact staged diff to block unrelated files, credentials, .env files, and build output from being committed. - Verification Gate: Runs the appropriate project gate (bun run complete-check, bun run fmt, or integration tests) before allowing the commit. - Conventional Commit Messages: Generates scoped messages like feat(documents): add upload API [BE-S1-02] with task IDs and an 80-character limit. - Use Case: After finishing a documents upload API task, ask the assistant to commit; it stages only the intended paths, runs the verification gate, and produces a compliant commit message with evidence. ## Quick Start Ask the assistant to commit the completed task changes using the git-commit skill and it will review, verify, and create a scoped commit.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I create a safe Git commit after finishing a coding task?▼

Stage only the intended files with explicit paths, inspect the staged diff with git diff --cached, run the project verification gate, then commit with a Conventional Commits message. Never stage everything blindly or commit on protected branches.

What is the Conventional Commits format for commit messages?▼

Use type(scope): subject, with types like feat, fix, refactor, test, docs, chore, or perf. Keep the first line under 80 characters, use imperative English, and include the task ID such as [BE-S1-02] where applicable.

How do I prevent secrets from being committed to Git?▼

Review the exact staged diff before committing and confirm no .env files, *.pem keys, credentials, signed URLs, or document contents are staged. Stop the commit immediately if any sensitive file appears in the diff.

When should I not commit changes in Git?▼

Do not commit when verification fails, the branch is dev or main, the diff contains unrelated work, a migration is unreviewed or stale, or sensitive data is staged. Resolve the blocking condition first.

Does this workflow push commits to the remote automatically?▼

No, pushing only happens when the developer explicitly requests it. A push request additionally requires reading the commit-and-push command file and completing its pre-push gate.