commit-sentinel

Original：🇺🇸 English

Translated

Master of Ceremonies for Git. Architect of High-Integrity Repositories. Expert in Git 3.0, Forensic Bisecting, and Interactive Rebasing.

1installs

Sourceyuniorglez/gemini-elite-core

Added on2026-03-04

NPX Install

npx skill4agent add yuniorglez/gemini-elite-core commit-sentinel

SKILL.md Content

View Translation Comparison →

🛡️ Skill: Commit Sentinel (v2.1.0)

Executive Summary

The

commit-sentinel

is the guardian of repository health and historical clarity. In 2026, where AI agents generate thousands of lines of code daily, the role of the sentinel is critical to prevent "History Pollution" and "Type Decay." This skill enforces a rigorous 4-step validation protocol, promotes surgical history sculpting via rebasing, and leverages automated hooks to ensure that only elite-level code reaches the main branch.

🛡️ The 4-Step Validation Protocol

Before every commit, the Sentinel MUST execute:

Surgical Diff Review:
```
git diff --cached
```
to verify every line.
- Filter: Remove all
```
console.log
```
  ,
```
TODO
```
  (unless planned), and debug artifacts.
Strict Type Audit:
```
bun x tsc --noEmit
```
(Mandatory).
- Standard: ZERO type errors allowed in the entire workspace.
Linter Enforcement:
```
bun run lint
```
.
- Standard: Adherence to the project's formatting and security rules.
Logical Atomicity: Ensure the commit does exactly ONE thing.
- Check: If the diff covers multiple features/fixes, use
```
git add -p
```
  to split.

🚫 The "Do Not" List (Anti-Patterns)

Anti-Pattern	Why it fails in 2026	Modern Alternative
`--no-verify`	Bypasses safety hooks.	Fix the underlying issue.
`git commit -m "update"`	Useless for forensics/AI context.	Use Conventional Commits.
Pushed Rebases	Breaks the team's local history.	Only rebase local branches.
Massive "Cleanup" Commits	Makes `git bisect` impossible.	Use Atomic, Incremental Changes.
SHA-1 Assumptions	Security risk in modern Git.	Prepare for SHA-256 (Git 3.0).

📝 Conventional Commits 2026

We follow the strictly typed commit standard:

```
feat(scope):
```
A new feature.
```
fix(scope):
```
A bug fix.
```
refactor(scope):
```
No feature or bug change.
```
perf(scope):
```
Performance improvements.
```
chore(scope):
```
Internal tools/config.
```
docs(scope):
```
Documentation only.

Structure:

text

type(scope)!: short description (max 50 chars)

Detailed body explaining WHY this change was made.
Wrapped at 72 chars.

BREAKING CHANGE: [details]
Resolves #123

🔨 History Sculpting (Interactive Rebase)

The Sentinel never pushes messy local history.

bash

# Clean up the last 3 local commits before pushing
git rebase -i HEAD~3

Use
squash
to combine small "fix" commits into a single "feat" or "fix".

🔍 Forensic Validation (Git Bisect)

When a bug appears, find the source with binary search.