@codigodoleo/wp-kit 1.0.0

package/modules/docs/templates/docs/Monitoramento.md

@@ -0,0 +1,302 @@
+# 📊 Monitoramento
+
+Documentação do sistema de monitoramento e observabilidade do Pipefy Website, incluindo métricas, alertas e pontos que necessitam detalhamento pela equipe SRE.
+
+## 🎯 **Visão Geral do Monitoramento**
+
+### **Objetivos**
+- Garantir disponibilidade e performance do site
+- Detectar problemas antes que afetem usuários
+- Fornecer insights para otimização
+- Manter SLAs definidos
+
+### **Stack de Observabilidade**
+- **Metrics**: `[SRE_DETAIL: Prometheus, CloudWatch, OCI Monitoring]`
+- **Logs**: `[SRE_DETAIL: ELK Stack, Fluentd, OCI Logging]`
+- **Traces**: `[SRE_DETAIL: Jaeger, Zipkin, ou APM solution]`
+- **Dashboards**: `[SRE_DETAIL: Grafana, OCI Console, ou custom]`
+
+## 📈 **Métricas Principais**
+
+### **Application Metrics**
+| Métrica | Threshold | Alertas | Responsável |
+|---------|-----------|---------|-------------|
+| **Response Time** | `[SRE_DETAIL: < Xs]` | `[SRE_DETAIL: Alert rules]` | Dev Team |
+| **Error Rate** | `[SRE_DETAIL: < X%]` | `[SRE_DETAIL: Alert rules]` | Dev Team |
+| **Throughput** | `[SRE_DETAIL: > X req/s]` | `[SRE_DETAIL: Alert rules]` | SRE Team |
+| **Availability** | `[SRE_DETAIL: > XX.X%]` | `[SRE_DETAIL: Alert rules]` | SRE Team |
+
+### **Infrastructure Metrics**
+| Componente | Métricas Monitoradas | Thresholds |
+|------------|---------------------|------------|
+| **Kubernetes Pods** | CPU, Memory, Restarts | `[SRE_DETAIL: Limites específicos]` |
+| **Database** | Connections, Query time, Locks | `[SRE_DETAIL: Limites específicos]` |
+| **Storage** | Disk usage, I/O operations | `[SRE_DETAIL: Limites específicos]` |
+| **Network** | Bandwidth, Latency, Packet loss | `[SRE_DETAIL: Limites específicos]` |
+
+### **Business Metrics**
+- **Page Views**: `[SRE_DETAIL: Tracking method e baseline]`
+- **User Sessions**: `[SRE_DETAIL: Analytics integration]`
+- **Conversion Rate**: `[SRE_DETAIL: Goals e funnels]`
+- **Search Performance**: `[SRE_DETAIL: Internal search metrics]`
+
+## 🚨 **Sistema de Alertas**
+
+### **Níveis de Severidade**
+| Nível | Descrição | Resposta Esperada | Escalação |
+|-------|-----------|-------------------|-----------|
+| **P1 - Critical** | Site down, data loss | Imediata (< 15 min) | `[SRE_DETAIL: On-call rotation]` |
+| **P2 - High** | Performance degraded | < 1 hora | `[SRE_DETAIL: Team lead]` |
+| **P3 - Medium** | Minor issues | < 4 horas | `[SRE_DETAIL: Dev team]` |
+| **P4 - Low** | Warnings, capacity | Next business day | `[SRE_DETAIL: Planning]` |
+
+### **Canais de Notificação**
+- **Slack**: `[SRE_DETAIL: Channels configurados (#alerts, #devops)]`
+- **Email**: `[SRE_DETAIL: Distribution lists]`
+- **PagerDuty**: `[SRE_DETAIL: On-call schedule]`
+- **SMS**: `[SRE_DETAIL: Critical alerts only]`
+
+### **Alert Rules**
+```
+Site Down (P1):
+- HTTP 5xx > 50% por 2 minutos
+- [SRE_DETAIL: Specific conditions and thresholds]
+
+High Response Time (P2):
+- Response time > Xs por 5 minutos
+- [SRE_DETAIL: Specific conditions and thresholds]
+
+Database Issues (P1/P2):
+- Connection errors > X%
+- [SRE_DETAIL: Specific conditions and thresholds]
+```
+
+## 📋 **Dashboards**
+
+### **Executive Dashboard**
+- **Uptime**: Overall availability
+- **Performance**: Average response time
+- **User Impact**: Active users, page views
+- **Business KPIs**: `[SRE_DETAIL: Specific business metrics]`
+
+### **Operations Dashboard**
+- **Infrastructure Health**: Pods, nodes, storage
+- **Application Performance**: Response times, errors
+- **Security Events**: `[SRE_DETAIL: Security monitoring metrics]`
+- **Deployment Status**: `[SRE_DETAIL: CI/CD pipeline metrics]`
+
+### **Development Dashboard**
+- **Error Rates**: By endpoint, feature
+- **Performance Trends**: Historical data
+- **User Experience**: `[SRE_DETAIL: Frontend performance metrics]`
+- **API Usage**: `[SRE_DETAIL: API endpoint metrics]`
+
+## 🔍 **Health Checks**
+
+### **Application Health Checks**
+| Endpoint | Frequency | Timeout | Expected Response |
+|----------|-----------|---------|-------------------|
+| `/wp-json/wp/v2/` | `[SRE_DETAIL: Xs]` | `[SRE_DETAIL: Xs]` | HTTP 200 |
+| `/wp-admin/admin-ajax.php` | `[SRE_DETAIL: Xs]` | `[SRE_DETAIL: Xs]` | HTTP 200 |
+| `[SRE_DETAIL: Custom endpoint]` | `[SRE_DETAIL: Xs]` | `[SRE_DETAIL: Xs]` | `[SRE_DETAIL: Expected]` |
+
+### **External Dependencies**
+- **Database**: `[SRE_DETAIL: Connection check frequency]`
+- **CDN (CloudFlare)**: `[SRE_DETAIL: Edge health monitoring]`
+- **Third-party APIs**: `[SRE_DETAIL: External service monitoring]`
+- **Object Storage**: `[SRE_DETAIL: Storage accessibility check]`
+
+### **Kubernetes Health Checks**
+```yaml
+livenessProbe:
+  # [SRE_DETAIL: Configuração específica]
+  
+readinessProbe:
+  # [SRE_DETAIL: Configuração específica]
+  
+startupProbe:
+  # [SRE_DETAIL: Configuração específica]
+```
+
+## 📊 **SLIs e SLOs**
+
+### **Service Level Indicators (SLIs)**
+| SLI | Medição | Fonte de Dados |
+|-----|---------|----------------|
+| **Availability** | Successful requests / Total requests | `[SRE_DETAIL: Load balancer logs]` |
+| **Latency** | Response time < Xms | `[SRE_DETAIL: Application metrics]` |
+| **Error Rate** | Error responses / Total responses | `[SRE_DETAIL: Application logs]` |
+| **Throughput** | Requests per second | `[SRE_DETAIL: Ingress metrics]` |
+
+### **Service Level Objectives (SLOs)**
+| SLO | Target | Measurement Window | Error Budget |
+|-----|--------|-------------------|--------------|
+| **Availability** | `[SRE_DETAIL: 99.X%]` | 30 days | `[SRE_DETAIL: X hours]` |
+| **Response Time** | `[SRE_DETAIL: XX% < Xs]` | 24 hours | `[SRE_DETAIL: X% budget]` |
+| **Error Rate** | `[SRE_DETAIL: < X%]` | 24 hours | `[SRE_DETAIL: X% budget]` |
+
+### **Error Budget Policy**
+- **Budget Remaining > 50%**: `[SRE_DETAIL: Normal operations]`
+- **Budget Remaining 10-50%**: `[SRE_DETAIL: Increased monitoring]`
+- **Budget Remaining < 10%**: `[SRE_DETAIL: Feature freeze policy]`
+
+## 🔐 **Security Monitoring**
+
+### **Security Events**
+- **Failed Login Attempts**: `[SRE_DETAIL: Threshold e response]`
+- **Unusual Traffic Patterns**: `[SRE_DETAIL: DDoS detection]`
+- **File System Changes**: `[SRE_DETAIL: File integrity monitoring]`
+- **Privilege Escalation**: `[SRE_DETAIL: RBAC violations]`
+
+### **Compliance Monitoring**
+- **Access Logs**: `[SRE_DETAIL: Retention policy]`
+- **Data Protection**: `[SRE_DETAIL: GDPR compliance metrics]`
+- **Security Patches**: `[SRE_DETAIL: Vulnerability scanning]`
+- **Certificate Expiration**: `[SRE_DETAIL: SSL monitoring]`
+
+## 📝 **Logging Strategy**
+
+### **Log Types**
+| Log Type | Retention | Format | Storage |
+|----------|-----------|--------|---------|
+| **Application Logs** | `[SRE_DETAIL: X days]` | `[SRE_DETAIL: JSON/Plain]` | `[SRE_DETAIL: Location]` |
+| **Access Logs** | `[SRE_DETAIL: X days]` | `[SRE_DETAIL: Format]` | `[SRE_DETAIL: Location]` |
+| **Error Logs** | `[SRE_DETAIL: X days]` | `[SRE_DETAIL: Format]` | `[SRE_DETAIL: Location]` |
+| **Security Logs** | `[SRE_DETAIL: X days]` | `[SRE_DETAIL: Format]` | `[SRE_DETAIL: Location]` |
+
+### **Log Aggregation**
+- **Collection**: `[SRE_DETAIL: Fluentd, Filebeat, ou similar]`
+- **Processing**: `[SRE_DETAIL: Logstash, ou stream processing]`
+- **Storage**: `[SRE_DETAIL: Elasticsearch, OCI Logging]`
+- **Visualization**: `[SRE_DETAIL: Kibana, Grafana]`
+
+### **Log Analysis**
+- **Error Pattern Detection**: `[SRE_DETAIL: Automated analysis]`
+- **Performance Insights**: `[SRE_DETAIL: Slow query detection]`
+- **Security Analysis**: `[SRE_DETAIL: Threat detection]`
+- **Trend Analysis**: `[SRE_DETAIL: Historical patterns]`
+
+## 🔄 **Incident Response**
+
+### **Runbooks**
+| Cenário | Runbook | Owner | Automation Level |
+|---------|---------|-------|------------------|
+| **Site Down** | `[SRE_DETAIL: Link para runbook]` | SRE Team | `[SRE_DETAIL: Manual/Auto]` |
+| **High CPU** | `[SRE_DETAIL: Link para runbook]` | Dev Team | `[SRE_DETAIL: Manual/Auto]` |
+| **Database Issues** | `[SRE_DETAIL: Link para runbook]` | DBA Team | `[SRE_DETAIL: Manual/Auto]` |
+| **Security Incident** | `[SRE_DETAIL: Link para runbook]` | Security Team | `[SRE_DETAIL: Manual/Auto]` |
+
+### **Auto-Remediation**
+- **Pod Restart**: `[SRE_DETAIL: Conditions for automatic restart]`
+- **Scale Up**: `[SRE_DETAIL: HPA triggers]`
+- **Cache Clear**: `[SRE_DETAIL: Performance degradation triggers]`
+- **Circuit Breaker**: `[SRE_DETAIL: Dependency failure handling]`
+
+### **Escalation Matrix**
+```
+Level 1: On-call Engineer (0-15 min)
+Level 2: Team Lead (15-30 min)
+Level 3: Manager (30-60 min)
+Level 4: Director (60+ min)
+
+[SRE_DETAIL: Specific contact information and triggers]
+```
+
+## 📱 **Synthetic Monitoring**
+
+### **Uptime Monitoring**
+- **External Providers**: `[SRE_DETAIL: Pingdom, StatusCake, etc.]`
+- **Check Frequency**: `[SRE_DETAIL: Interval]`
+- **Global Locations**: `[SRE_DETAIL: Geographic distribution]`
+- **Alert Thresholds**: `[SRE_DETAIL: Failure conditions]`
+
+### **User Journey Monitoring**
+- **Critical Paths**: `[SRE_DETAIL: Key user flows to monitor]`
+- **Performance Budgets**: `[SRE_DETAIL: Load time thresholds]`
+- **Browser Testing**: `[SRE_DETAIL: Cross-browser compatibility]`
+- **Mobile Monitoring**: `[SRE_DETAIL: Mobile-specific checks]`
+
+## 🎯 **Performance Monitoring**
+
+### **Frontend Performance**
+- **Core Web Vitals**: `[SRE_DETAIL: LCP, FID, CLS thresholds]`
+- **Page Load Times**: `[SRE_DETAIL: Measurement tools]`
+- **JavaScript Errors**: `[SRE_DETAIL: Error tracking solution]`
+- **User Experience**: `[SRE_DETAIL: Real User Monitoring]`
+
+### **Backend Performance**
+- **API Response Times**: `[SRE_DETAIL: Endpoint-specific SLOs]`
+- **Database Performance**: `[SRE_DETAIL: Query optimization metrics]`
+- **Cache Hit Rates**: `[SRE_DETAIL: CDN and application cache]`
+- **Resource Utilization**: `[SRE_DETAIL: CPU, memory, storage trends]`
+
+## 📊 **Capacity Planning**
+
+### **Growth Metrics**
+- **Traffic Trends**: `[SRE_DETAIL: Historical growth patterns]`
+- **Resource Usage**: `[SRE_DETAIL: Infrastructure scaling needs]`
+- **Storage Growth**: `[SRE_DETAIL: Data retention and archival]`
+- **Cost Optimization**: `[SRE_DETAIL: Resource right-sizing]`
+
+### **Forecasting**
+- **Predictive Analysis**: `[SRE_DETAIL: Tools and methodologies]`
+- **Seasonal Patterns**: `[SRE_DETAIL: Traffic seasonality]`
+- **Scaling Triggers**: `[SRE_DETAIL: Proactive scaling thresholds]`
+- **Budget Planning**: `[SRE_DETAIL: Infrastructure cost projections]`
+
+## 📋 **Action Items para SRE**
+
+### **🔴 Crítico (Implementação Necessária)**
+- [ ] Definir e implementar SLOs específicos para o site
+- [ ] Configurar alertas críticos com thresholds apropriados
+- [ ] Estabelecer on-call rotation e escalation procedures
+- [ ] Implementar health checks abrangentes
+
+### **🟡 Importante (Melhoria)**
+- [ ] Configurar dashboards operacionais e executivos
+- [ ] Implementar synthetic monitoring externo
+- [ ] Estabelecer log aggregation e analysis
+- [ ] Criar runbooks para cenários comuns
+
+### **🟢 Desejável (Otimização)**
+- [ ] Implementar auto-remediation para problemas comuns
+- [ ] Configurar capacity planning automatizado
+- [ ] Implementar advanced APM solution
+- [ ] Estabelecer chaos engineering practices
+
+## 📞 **Responsabilidades e Contatos**
+
+### **Monitoring Ownership**
+- **SRE Team**: Infrastructure metrics, alerting, SLOs
+- **Development Team**: Application metrics, error tracking
+- **Security Team**: Security monitoring, compliance
+- **Business Team**: Business metrics, user experience
+
+### **Tools and Access**
+- **Monitoring Tools**: `[SRE_DETAIL: Access management]`
+- **Alert Management**: `[SRE_DETAIL: Who can modify alerts]`
+- **Dashboard Creation**: `[SRE_DETAIL: Self-service capabilities]`
+- **Incident Management**: `[SRE_DETAIL: Incident commander rotation]`
+
+## 🔄 **Continuous Improvement**
+
+### **Monitoring Review Process**
+- **Monthly SLO Review**: `[SRE_DETAIL: Meeting cadence]`
+- **Alert Tuning**: `[SRE_DETAIL: Noise reduction process]`
+- **Dashboard Optimization**: `[SRE_DETAIL: User feedback integration]`
+- **Tool Evaluation**: `[SRE_DETAIL: Technology refresh cycle]`
+
+### **Metrics Evolution**
+- **New Metrics**: `[SRE_DETAIL: Request and approval process]`
+- **Deprecated Metrics**: `[SRE_DETAIL: Sunset process]`
+- **Business Alignment**: `[SRE_DETAIL: KPI alignment reviews]`
+- **Industry Benchmarks**: `[SRE_DETAIL: External comparison]`
+
+---
+
+📝 **Última atualização**: Junho 2025  
+📊 **Stack**: `[SRE_DETAIL: Current monitoring stack]`  
+🚨 **Alerting**: `[SRE_DETAIL: Primary alerting system]`  
+📈 **SLOs**: A serem definidos pela equipe SRE  
+🔄 **Estado**: Necessita implementação detalhada  
+🎯 **Próximos passos**: Preenchimento dos `[SRE_DETAIL]` e implementação das action items

package/modules/docs/templates/docs/Sync-the-Production-DB-with-the-Staging-DB.md

@@ -0,0 +1,8 @@
+1. Inside GitLab:
+
+	1. Go to [CI/CD -> Schedules](https://git.pipefy.net/wordpress/pipefy-website/-/pipeline_schedules).
+	2. Press the play button on the `Download Prod Database` scheduled pipeline.
+		1. It'll create a database backup and store it in the S3 bucket.
+	3. After finishing the job above, press the play button on the `Replicate Production DB into Staging DB` scheduled pipeline.
+		1. That last job uses the database backup inside the S3 bucket
+	4. Done! Staging environment's updated now.

package/modules/docs/templates/docs/Troubleshooting.md

@@ -0,0 +1,3 @@
+### I'm having trouble accessing Pipefy's Gitlab.
+
+If you can't access git.pipefy.net connected to the VPN try accessing GitLab from the Google Apps menu.

package/modules/git/.commitlintrc.json

@@ -0,0 +1,136 @@
+{
+  "extends": ["@commitlint/config-conventional"],
+  "rules": {
+    "type-enum": [
+      2,
+      "always",
+      [
+        "feat",
+        "fix",
+        "docs",
+        "style",
+        "refactor",
+        "perf",
+        "test",
+        "chore",
+        "ci",
+        "build",
+        "revert",
+        "hotfix",
+        "release"
+      ]
+    ],
+    "type-case": [2, "always", "lower-case"],
+    "type-empty": [2, "never"],
+    "scope-case": [2, "always", "lower-case"],
+    "subject-case": [2, "never", ["sentence-case", "start-case", "pascal-case", "upper-case"]],
+    "subject-empty": [2, "never"],
+    "subject-full-stop": [2, "never", "."],
+    "header-max-length": [2, "always", 72],
+    "body-leading-blank": [1, "always"],
+    "body-max-line-length": [2, "always", 100],
+    "footer-leading-blank": [1, "always"],
+    "footer-max-line-length": [2, "always", 100]
+  },
+  "prompt": {
+    "questions": {
+      "type": {
+        "description": "Select the type of change that you're committing:",
+        "enum": {
+          "feat": {
+            "description": "A new feature",
+            "title": "Features",
+            "emoji": "✨"
+          },
+          "fix": {
+            "description": "A bug fix",
+            "title": "Bug Fixes",
+            "emoji": "🐛"
+          },
+          "docs": {
+            "description": "Documentation only changes",
+            "title": "Documentation",
+            "emoji": "📚"
+          },
+          "style": {
+            "description": "Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)",
+            "title": "Styles",
+            "emoji": "💎"
+          },
+          "refactor": {
+            "description": "A code change that neither fixes a bug nor adds a feature",
+            "title": "Code Refactoring",
+            "emoji": "📦"
+          },
+          "perf": {
+            "description": "A code change that improves performance",
+            "title": "Performance Improvements",
+            "emoji": "🚀"
+          },
+          "test": {
+            "description": "Adding missing tests or correcting existing tests",
+            "title": "Tests",
+            "emoji": "🚨"
+          },
+          "build": {
+            "description": "Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)",
+            "title": "Builds",
+            "emoji": "🛠"
+          },
+          "ci": {
+            "description": "Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)",
+            "title": "Continuous Integrations",
+            "emoji": "⚙️"
+          },
+          "chore": {
+            "description": "Other changes that don't modify src or test files",
+            "title": "Chores",
+            "emoji": "♻️"
+          },
+          "revert": {
+            "description": "Reverts a previous commit",
+            "title": "Reverts",
+            "emoji": "🗑"
+          },
+          "hotfix": {
+            "description": "Critical fix in production",
+            "title": "Hotfixes",
+            "emoji": "🚑"
+          },
+          "release": {
+            "description": "Release a new version",
+            "title": "Releases",
+            "emoji": "🎉"
+          }
+        }
+      },
+      "scope": {
+        "description": "What is the scope of this change (e.g. component or file name)"
+      },
+      "subject": {
+        "description": "Write a short, imperative tense description of the change"
+      },
+      "body": {
+        "description": "Provide a longer description of the change"
+      },
+      "isBreaking": {
+        "description": "Are there any breaking changes?"
+      },
+      "breakingBody": {
+        "description": "A BREAKING CHANGE commit requires a body. Please enter a longer description of the commit itself"
+      },
+      "breaking": {
+        "description": "Describe the breaking changes"
+      },
+      "isIssueAffected": {
+        "description": "Does this change affect any open issues?"
+      },
+      "issuesBody": {
+        "description": "If issues are closed, the commit requires a body. Please enter a longer description of the commit itself"
+      },
+      "issues": {
+        "description": "Add issue references (e.g. \"fix #123\", \"re #123\")"
+      }
+    }
+  }
+}

package/modules/git/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,42 @@
+## 📋 Description
+
+<!-- Briefly describe the changes made -->
+
+## 🎯 Change Type
+
+- [ ] 🚀 New feature (feat)
+- [ ] 🐛 Bug fix (fix)
+- [ ] 📚 Documentation (docs)
+- [ ] 🎨 Style improvement (style)
+- [ ] ♻️ Refactoring (refactor)
+- [ ] ⚡ Performance improvement (perf)
+- [ ] 🧪 Test (test)
+- [ ] 🔧 Build configuration (build)
+- [ ] 🔄 CI/CD (ci)
+- [ ] 🧹 Maintenance (chore)
+- [ ] 🔥 Hotfix (hotfix)
+
+## 🔍 Checklist
+
+- [ ] Code follows project standards
+- [ ] Tests have been added/updated (if applicable)
+- [ ] Documentation has been updated (if applicable)
+- [ ] Commits follow Conventional Commits pattern
+- [ ] Branch is up to date with base branch
+
+## 🧪 Tests
+
+<!-- Describe how to test the changes -->
+
+## 📸 Screenshots (if applicable)
+
+<!-- Add screenshots if the change affects the interface -->
+
+## 🔗 Related Issues
+
+<!-- Link to related issues -->
+Closes #(issue_number)
+
+## 📝 Additional Notes
+
+<!-- Additional information that may be useful -->

package/modules/git/.gitlab/merge_request_templates/default.md

@@ -0,0 +1,42 @@
+## 📋 Description
+
+<!-- Briefly describe the changes made -->
+
+## 🎯 Change Type
+
+- [ ] 🚀 New feature (feat)
+- [ ] 🐛 Bug fix (fix)
+- [ ] 📚 Documentation (docs)
+- [ ] 🎨 Style improvement (style)
+- [ ] ♻️ Refactoring (refactor)
+- [ ] ⚡ Performance improvement (perf)
+- [ ] 🧪 Test (test)
+- [ ] 🔧 Build configuration (build)
+- [ ] 🔄 CI/CD (ci)
+- [ ] 🧹 Maintenance (chore)
+- [ ] 🔥 Hotfix (hotfix)
+
+## 🔍 Checklist
+
+- [ ] Code follows project standards
+- [ ] Tests have been added/updated (if applicable)
+- [ ] Documentation has been updated (if applicable)
+- [ ] Commits follow Conventional Commits pattern
+- [ ] Branch is up to date with base branch
+
+## 🧪 Tests
+
+<!-- Describe how to test the changes -->
+
+## 📸 Screenshots (if applicable)
+
+<!-- Add screenshots if the change affects the interface -->
+
+## 🔗 Related Issues
+
+<!-- Link to related issues -->
+Closes #(issue_number)
+
+## 📝 Additional Notes
+
+<!-- Additional information that may be useful -->

package/modules/git/.gitmessage

@@ -0,0 +1,29 @@
+# <type>(<scope>): <description>
+#
+# <body>
+#
+# <footer>
+
+# --- REMOVE THIS LINE AND EVERYTHING BELOW ---
+# Available types:
+# feat:     A new feature
+# fix:      A bug fix
+# docs:     Documentation changes
+# style:    Formatting, white-space, etc
+# refactor: Code refactoring
+# perf:     Performance improvements
+# test:     Adding tests
+# chore:    Maintenance tasks
+# ci:       CI/CD changes
+# build:    Build system changes
+# revert:   Revert previous commit
+# hotfix:   Critical production fix
+# release:  Version release
+#
+# Remember:
+# - Use imperative mood: "add" not "added"
+# - Don't capitalize first letter
+# - No dot (.) at the end
+# - First line up to 72 characters
+# - For BREAKING CHANGES, add "BREAKING CHANGE:" in footer
+# - Reference issues: "Closes #123" or "Fixes #123"

package/modules/git/.husky/commit-msg

@@ -0,0 +1,4 @@
+#!/bin/sh
+. "$(dirname "$0")/_/husky.sh"
+
+npx --no -- commitlint --edit "$1"

package/modules/git/.husky/pre-commit

@@ -0,0 +1,27 @@
+#!/bin/sh
+. "$(dirname "$0")/_/husky.sh"
+
+echo "🔍 Running pre-commit checks..."
+
+# Check if lint-staged config exists
+if [ ! -f ".lintstagedrc.json" ]; then
+    echo "❌ .lintstagedrc.json not found, skipping lint-staged"
+    exit 0
+fi
+
+# Check if we have staged files
+if [ -z "$(git diff --cached --name-only)" ]; then
+    echo "ℹ️  No staged files, skipping lint-staged"
+    exit 0
+fi
+
+echo "📝 Running lint-staged..."
+if command -v lando >/dev/null 2>&1 && lando info >/dev/null 2>&1; then
+    echo "🐳 Using Lando environment..."
+    lando lint-staged
+else
+    echo "🏠 Using local environment..."
+    npx lint-staged
+fi
+
+echo "✅ Pre-commit checks completed!"

package/modules/git/.lintstagedrc.json

@@ -0,0 +1,7 @@
+{
+  "*.{js,jsx,ts,tsx}": "eslint",
+  "*.{css,scss,sass}": "stylelint",
+  "*.{json,yaml,yml,md}": "prettier --check",
+  "*.{html}": "prettier --check --parser html",
+  "*.{php}": "pint --test"
+}

package/modules/git/.vscode/commit-instructions.md

@@ -0,0 +1,59 @@
+# Commit Message Instructions for AI Tools
+
+When generating commit messages, follow these guidelines:
+
+## Format
+```
+<type>(<scope>): <description>
+
+<body>
+
+<footer>
+```
+
+## Rules
+- **First line max 72 characters**
+- **Use imperative mood** ("add" not "added")
+- **Lowercase first letter**
+- **No ending period**
+- **Types**: feat, fix, docs, style, refactor, perf, test, chore, ci, build, revert, hotfix, release
+- **Scope**: Optional, use component/file/area affected
+- **Body**: Optional, explain what and why
+- **Footer**: Optional, breaking changes and issue references
+
+## Available Types
+- `feat`: A new feature
+- `fix`: A bug fix
+- `docs`: Documentation changes
+- `style`: Formatting, white-space, etc
+- `refactor`: Code refactoring
+- `perf`: Performance improvements
+- `test`: Adding tests
+- `chore`: Maintenance tasks
+- `ci`: CI/CD changes
+- `build`: Build system changes
+- `revert`: Revert previous commit
+- `hotfix`: Critical production fix
+- `release`: Version release
+
+## Examples
+- `feat(auth): add user login functionality`
+- `fix(ui): resolve header alignment on mobile`
+- `docs(readme): update installation guide`
+- `style(css): format button component styling`
+- `refactor(api): extract user validation logic`
+- `perf(images): implement lazy loading`
+- `test(auth): add login validation tests`
+- `chore(deps): update dependencies to latest`
+- `ci(github): add automated deployment`
+- `build(webpack): optimize production bundle`
+
+## Breaking Changes
+Add `BREAKING CHANGE:` in footer for breaking changes.
+
+## Issue References
+Add `Closes #123` or `Fixes #123` in footer for issue references.
+
+## AI Generation Prompt
+When using AI tools (Copilot, GitLens), use this prompt:
+"Generate a conventional commit message for the staged changes. Use format: <type>(<scope>): <description>. Available types: feat, fix, docs, style, refactor, perf, test, chore, ci, build, revert, hotfix, release. Keep under 72 characters, imperative mood, lowercase, no ending period."