gxpm-hygiene

Enforce atomic commits with GXPM-N messages and pre-commit hook checks.

1|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/laozhong86/gxpm --skill gxpm-hygiene
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gxpm-hygiene
Source: https://github.com/laozhong86/gxpm/tree/main/skills/gxpm-hygiene
Command: npx skills add https://github.com/laozhong86/gxpm --skill gxpm-hygiene

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-commit hygiene and atomic commit discipline ensure every change is committed as a single, auditable unit, reducing risk and improving traceability.

Core Features & Use Cases

  • Enforces one logical change per commit to maintain clean history.
  • Provides a checklist for review, secret leakage scan, and hook-based validations.
  • Guides preparation for self-review and ship-phase PR readiness with enforced discipline.

Quick Start

Run the pre-commit hygiene checks before committing to guarantee atomic commits.

Frequently Asked Questions about gxpm-hygiene

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

FAQPage Schema
How do I enforce atomic commits in my git workflow?

Enforcing atomic commits involves applying pre-commit hygiene checks before every commit. This discipline maintains clean git history by ensuring one logical change per commit and requiring a GXPM-N identifier in commit messages for traceability.

What is atomic commit discipline and when do I need it for self-review?

Atomic commit discipline is the practice of keeping one logical change per commit. You need it during self-review preparation and ship-phase PR readiness to guarantee every change is a single, auditable unit that reduces risk and improves traceability.

Can I bypass pre-commit hooks when preparing a PR for ship?

You cannot bypass pre-commit hooks when preparing a PR for ship. Pre-commit hygiene checks actively block bypassing hooks, ensuring validations and secret leakage scans are executed before committing changes.

Does this pre-commit hygiene check require any external dependencies?

This pre-commit hygiene check does not require any external dependencies. It operates as a standalone workflow component to enforce commit quality and atomic commit discipline directly.

Why does my git workflow need a GXPM-N identifier in commit messages?

Your git workflow needs a GXPM-N identifier in commit messages to enforce atomic commit discipline. This identifier ensures every committed change is a single, auditable unit that improves traceability and reduces risk.