skills.rest
vesviet
vesvietCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

commit-code

Validate and package finished code changes into clean, approved git commits.

Updated Feb 10, 2026
Search Tags:#git#commit#conventional commits#release notes#pre-commit#code validation#secret scanning
One-click install
npx skills add https://github.com/vesviet/agent-skills --skill commit-code-vesviet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-code
Source: https://github.com/vesviet/agent-skills/tree/main/core/skills/repo-ops/commit-code
Command: npx skills add https://github.com/vesviet/agent-skills --skill commit-code-vesviet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It prevents broken, oversized, or unsafe commits by enforcing repo-local validation, generation, secret scanning, and explicit approval rules before any commit is created. ## Core Features & Use Cases - Pre-commit validation: Runs tests, lint, and build gates, regenerates required code artifacts, and removes local-only files before staging. - Commit hygiene and security: Enforces GPG/SSH signing, secret scanning on staged changes, conventional commit messages, and .git-blame-ignore-revs for bulk reformats. - Gated actions: Treats commit, push, tag, and release as separately approved actions, and emits structured output contracts for multi-role delivery. - Use Case: After finishing a feature branch change, ask the agent to validate the diff, regenerate API clients, run the test suite, and prepare a signed conventional commit for your approval. ## Quick Start Use the commit-code skill to validate my current changes and prepare a clean commit for review.

Frequently Asked Questions about commit-code

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

FAQPage Schema
How do I prepare a clean git commit before pushing?▼

Review the diff against the intended scope, remove local-only artifacts, regenerate required files, run tests and lint, then create the commit only after explicit approval. Push, tag, and release remain separate gated actions.

What checks should run before committing code?▼

Run the repo's normal quality gates: tests, lint or static analysis, build, and targeted checks for migrations or contracts. Also run secret scanning on staged changes and verify no generated files were hand-edited.

Does this skill push commits or create releases automatically?▼

No. The skill covers commit preparation and creation only. Pushing branches, creating tags, and publishing releases are treated as separate actions that each require their own explicit approval.

How do I keep AI-assisted bulk reformats out of git blame?▼

Add the reformat commit hash to a `.git-blame-ignore-revs` file so git blame continues pointing to the human authors of the business logic. Enable GPG or SSH commit signing for identity verification.

Why should secrets be scanned before every commit?▼

Commits are permanent, user-visible artifacts that can expose credentials, internal hostnames, or customer identifiers. Secret scanning on staged changes rejects any commit containing high-entropy matches before it enters history.

Related Skills

Explore More Software Engineering Skills→
caseyrtalbotcaseyrtalbot

prove-first

Enforce test-first development by writing failing tests before minimal code.

Community
Intermediate
GenEducationGenEducation

ship

Prepare feature branches for release with tests, versioning, and pull requests.

Official
Advanced
TrevorPLamTrevorPLam

pre-commit-guard

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

Community
Intermediate
wadvancedwadvanced
11

gate-commit

Gate commits on mix consistency and group staged changes into conventional commit messages.

Official
Intermediate