Git Commit Standards
by AguardicOfficial·v1.0.0
Enforce conventional commit message formats and quality standards.
About This Policy Template
Operational policy that enforces commit message conventions including conventional commits format. Helps maintain clean and understandable git history.
Policy Rules(1)
Low Severity
(1)Conventional Commit Format
Check for conventional commit format
Enforcement by Integration
What happens when a violation is detected, based on the enforcement mode and integration type.
| Integration | Block | Approval | Warn | Monitor |
|---|---|---|---|---|
Version Control GitHub, GitLab, Bitbucket | Fail check run / merge request status | Pending check run — held for review | Neutral check run / comment on PR | Pass check run (silent) |
Email — Gmail Gmail | Quarantine label; + violation label (outbound) | Quarantine label — held for review | Add warning label | Log only |
Email — Outlook Outlook | Move to quarantine folder; + flag (outbound) | Move to quarantine — held for review | Flag + categorize | Log only |
Messaging Slack, Teams | Post violation warning in channel | Post 'held for review' warning | Post warning in channel | Log only |
Storage Google Drive, Dropbox, OneDrive | Move file to quarantine folder | Quarantine file — held for review | Log only | Log only |
AI Proxy OpenAI, Anthropic, Gemini, MCP, Agent | Block request (return 403) | Hold request — return review ID | Allow request + audit trail | Log only |
API REST API | Return BLOCK outcome (client decides) | Return APPROVAL_REQUIRED + poll URL | Return WARN outcome | Log only |
Version History
1 version published
v1.0.0Active2/23/2026
Initial release
Got a vendor security questionnaire?
Answer the AI questions with real framework citations
Ready to Install Git Commit Standards?
Get started with pre-built governance policies in minutes.