Quality gate enforcement for PR integration. Use when verifying code through pre-review, review, pre-merge, or post-merge checkpoints. Trigger with /eia-enforce-gates.
npx claudepluginhub emasoft/emasoft-plugins --plugin emasoft-integrator-agentThis skill uses the workspace's default tool permissions.
Quality gates are **mandatory checkpoints** that code must pass before advancing through the integration pipeline. Each gate defines specific criteria, blocking conditions, and escalation paths.
references/conventional-commits-validation.mdreferences/cross-platform-hook-patterns.mdreferences/encoding-compliance-checker.mdreferences/escalation-paths.mdreferences/escalation-procedures.mdreferences/gate-checklist.mdreferences/gate-decision-flowchart.mdreferences/gate-examples.mdreferences/gate-pipeline.mdreferences/integration-verification.mdreferences/label-reference.mdreferences/op-apply-gate-label.mdreferences/op-configure-pre-push-hook.mdreferences/op-document-failure.mdreferences/op-escalate-failure.mdreferences/op-execute-post-merge-gate.mdreferences/op-execute-pre-merge-gate.mdreferences/op-execute-pre-review-gate.mdreferences/op-execute-review-gate.mdreferences/op-identify-current-gate.mdDefine automated quality gates that enforce standards without manual review. Use when setting up CI/CD checks and blocking criteria.
Creates structured quality gates for workflow boundaries like pre-merge checklists, deployments, and phase transitions with pass/fail criteria, exact commands, and escalation procedures.
Standardizes release approvals using GitHub checklists for gates on scope, quality signals, docs, comms, and operations readiness before deployment.
Share bugs, ideas, or general feedback.
Quality gates are mandatory checkpoints that code must pass before advancing through the integration pipeline. Each gate defines specific criteria, blocking conditions, and escalation paths.
Before using this skill, ensure:
gh) is installed and authenticatedStep 5: Process Overrides (if applicable)
gate:override-applied labelCopy this checklist and track your progress:
When executing quality gates, provide:
Example Output Format:
Gate: Pre-Review Gate
Status: FAILED
Checks:
- Tests: FAILED (3 failing tests in auth module)
- Linting: PASSED
- Build: PASSED
- Description: PASSED
Labels Applied:
- gate:pre-review-failed
- gate:flaky-test
Escalation:
- Commented on PR with test failure details
- Notified @author
Next Steps:
- Author must fix failing tests
- Re-run pre-review gate after fixes
Common Errors and Solutions:
CI Pipeline Not Running
.github/workflows/Labels Not Applying
gh pr edit $PR_NUMBER --add-label "label-name" manually if automation failsEscalation Notification Failure
Gate Stuck in Pending State
Override Authority Unavailable
See references/gate-examples.md for complete examples including:
Purpose of Quality Gates:
Key Principle: Quality gates use state-based triggers, not time-based values. Gates advance or block based on conditions being met, not elapsed time.
The integration pipeline has four sequential gates. See references/gate-pipeline.md for the complete flow diagram.
See references/pre-review-gate.md for:
See references/review-gate.md for:
See references/pre-merge-gate.md for:
See references/post-merge-gate.md for:
See references/escalation-paths.md for complete escalation procedures including:
See references/override-policies.md for:
See references/label-reference.md for complete list of:
See references/gate-checklist.md for a copy-paste checklist covering:
This skill uses labels defined in eia-label-taxonomy. Ensure the label taxonomy is applied to the repository before using quality gates.
See references/troubleshooting.md for solutions to common issues:
These scripts manage design documents for quality gate integration:
| Script | Purpose | Usage |
|---|---|---|
eia_design_create.py | Create new design documents with proper GUUID | python scripts/eia_design_create.py --type <TYPE> --title "<TITLE>" |
eia_design_search.py | Search design documents by UUID, type, or status | python scripts/eia_design_search.py --type <TYPE> --status <STATUS> |
eia_design_validate.py | Validate design document frontmatter compliance | python scripts/eia_design_validate.py --all |
Script: scripts/eia_check_encoding.py — Checks Python files for missing UTF-8 encoding parameters
For encoding compliance checking, see encoding-compliance-checker.md:
Script: ../../scripts/eia_unicode_compliance.py — Full Unicode compliance checker (BOM, line endings, encoding, non-ASCII identifiers)
For Unicode enforcement hook details, see unicode-enforcement-hook.md:
These scripts enforce quality gates on pull requests:
| Script | Purpose | Usage |
|---|---|---|
eia_github_pr_gate.py | Run pre-merge quality checks on PRs | python scripts/eia_github_pr_gate.py --pr <NUMBER> |
eia_github_pr_gate_checks.py | Individual check implementations for PR gates | (Internal, called by eia_github_pr_gate.py) |
eia_github_report.py | Generate comprehensive GitHub project reports | python scripts/eia_github_report.py --owner <OWNER> --repo <REPO> --project <NUM> |
eia_github_report_formatters.py | Format reports in markdown/JSON | (Internal, used by eia_github_report.py) |
All scripts are located at ../../scripts/ relative to this skill.
Version: 1.0.0 Last Updated: 2025-02-04 Skill Type: Integration Process Required Knowledge: CI/CD, code review, GitHub workflows