@codigodoleo/wp-kit 2.0.4 → 3.0.1

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

@@ -5,12 +5,14 @@ Documentação do sistema de monitoramento e observabilidade do Pipefy Website,
 ## 🎯 **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]`
@@ -19,22 +21,25 @@ Documentação do sistema de monitoramento e observabilidade do Pipefy Website,
 ## 📈 **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 |
+
+| 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]` |
+
+| 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]`
@@ -43,20 +48,23 @@ Documentação do sistema de monitoramento e observabilidade do Pipefy Website,
 ## 🚨 **Sistema de Alertas**
 
 ### **Níveis de Severidade**
-| Nível | Descrição | Resposta Esperada | Escalação |
-|-------|-----------|-------------------|-----------|
+
+| 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]` |
+| **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
@@ -74,18 +82,21 @@ Database Issues (P1/P2):
 ## 📋 **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]`
@@ -94,26 +105,29 @@ Database Issues (P1/P2):
 ## 🔍 **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 |
+
+| 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]
 ```
@@ -121,21 +135,24 @@ startupProbe:
 ## 📊 **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]` |
+
+| 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]` |
+
+| 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]`
@@ -143,12 +160,14 @@ startupProbe:
 ## 🔐 **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]`
@@ -157,20 +176,23 @@ startupProbe:
 ## 📝 **Logging Strategy**
 
 ### **Log Types**
-| Log Type | Retention | Format | Storage |
-|----------|-----------|--------|---------|
+
+| 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]` |
+| **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]`
@@ -179,20 +201,23 @@ startupProbe:
 ## 🔄 **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]` |
+
+| 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)
@@ -205,12 +230,14 @@ Level 4: Director (60+ min)
 ## 📱 **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]`
@@ -219,12 +246,14 @@ Level 4: Director (60+ min)
 ## 🎯 **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]`
@@ -233,12 +262,14 @@ Level 4: Director (60+ min)
 ## 📊 **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]`
@@ -247,18 +278,21 @@ Level 4: Director (60+ min)
 ## 📋 **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
@@ -267,12 +301,14 @@ Level 4: Director (60+ min)
 ## 📞 **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]`
@@ -281,12 +317,14 @@ Level 4: Director (60+ min)
 ## 🔄 **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]`
@@ -299,4 +337,4 @@ Level 4: Director (60+ min)
 🚨 **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
+🎯 **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

@@ -1,8 +1,7 @@
 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.
+   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

@@ -1,3 +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.
+If you can't access git.pipefy.net connected to the VPN try accessing GitLab from the Google Apps menu.

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

@@ -35,6 +35,7 @@
 ## 🔗 Related Issues
 
 <!-- Link to related issues -->
+
 Closes #(issue_number)
 
 ## 📝 Additional Notes

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

@@ -35,6 +35,7 @@
 ## 🔗 Related Issues
 
 <!-- Link to related issues -->
+
 Closes #(issue_number)
 
 ## 📝 Additional Notes

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

@@ -3,6 +3,7 @@
 When generating commit messages, follow these guidelines:
 
 ## Format
+
 ```
 <type>(<scope>): <description>
 
@@ -12,6 +13,7 @@ When generating commit messages, follow these guidelines:
 ```
 
 ## Rules
+
 - **First line max 72 characters**
 - **Use imperative mood** ("add" not "added")
 - **Lowercase first letter**
@@ -22,6 +24,7 @@ When generating commit messages, follow these guidelines:
 - **Footer**: Optional, breaking changes and issue references
 
 ## Available Types
+
 - `feat`: A new feature
 - `fix`: A bug fix
 - `docs`: Documentation changes
@@ -37,6 +40,7 @@ When generating commit messages, follow these guidelines:
 - `release`: Version release
 
 ## Examples
+
 - `feat(auth): add user login functionality`
 - `fix(ui): resolve header alignment on mobile`
 - `docs(readme): update installation guide`
@@ -49,11 +53,14 @@ When generating commit messages, follow these guidelines:
 - `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."

package/modules/git/.vscode/conventional-commits.code-snippets

@@ -1,62 +1,32 @@
 {
   "Conventional Commit - feat": {
     "prefix": "cc-feat",
-    "body": [
-      "feat($1): $2",
-      "",
-      "$3",
-      "",
-      "$4"
-    ],
-    "description": "Template for new feature"
+    "body": ["feat($1): $2", "", "$3", "", "$4"],
+    "description": "Template for new feature",
   },
   "Conventional Commit - fix": {
     "prefix": "cc-fix",
-    "body": [
-      "fix($1): $2",
-      "",
-      "$3",
-      "",
-      "Fixes #$4"
-    ],
-    "description": "Template for bug fix"
+    "body": ["fix($1): $2", "", "$3", "", "Fixes #$4"],
+    "description": "Template for bug fix",
   },
   "Conventional Commit - docs": {
     "prefix": "cc-docs",
-    "body": [
-      "docs($1): $2",
-      "",
-      "$3"
-    ],
-    "description": "Template for documentation"
+    "body": ["docs($1): $2", "", "$3"],
+    "description": "Template for documentation",
   },
   "Conventional Commit - refactor": {
     "prefix": "cc-refactor",
-    "body": [
-      "refactor($1): $2",
-      "",
-      "$3"
-    ],
-    "description": "Template for refactoring"
+    "body": ["refactor($1): $2", "", "$3"],
+    "description": "Template for refactoring",
   },
   "Conventional Commit - chore": {
     "prefix": "cc-chore",
-    "body": [
-      "chore($1): $2",
-      "",
-      "$3"
-    ],
-    "description": "Template for maintenance tasks"
+    "body": ["chore($1): $2", "", "$3"],
+    "description": "Template for maintenance tasks",
   },
   "Conventional Commit - breaking change": {
     "prefix": "cc-breaking",
-    "body": [
-      "$1($2): $3",
-      "",
-      "BREAKING CHANGE: $4",
-      "",
-      "$5"
-    ],
-    "description": "Template for breaking change"
-  }
+    "body": ["$1($2): $3", "", "BREAKING CHANGE: $4", "", "$5"],
+    "description": "Template for breaking change",
+  },
 }

package/modules/git/docs/CONVENTIONAL-COMMITS.md

@@ -6,9 +6,9 @@
 
 Install the recommended extensions that will appear automatically:
 
-* **Conventional Commits**: Assistant to help you create commits following the standard
-* **GitLens**: Advanced Git visualization
-* **Git Graph**: Graphical history view
+- **Conventional Commits**: Assistant to help you create commits following the standard
+- **GitLens**: Advanced Git visualization
+- **Git Graph**: Graphical history view
 
 ### 2. Ways to Make Commits
 
@@ -35,10 +35,10 @@ git commit
 
 #### Option 4: Via VS Code Snippets
 
-* Type `cc-feat` + Tab for a new feature
-* Type `cc-fix` + Tab for a bug fix
-* Type `cc-docs` + Tab for documentation
-* And so on...
+- Type `cc-feat` + Tab for a new feature
+- Type `cc-fix` + Tab for a bug fix
+- Type `cc-docs` + Tab for documentation
+- And so on...
 
 ### 3. Available Commit Types
 
@@ -91,9 +91,9 @@ an object with data instead of a direct array.
 
 The project is set up with:
 
-* ✅ **Husky**: Git hooks
-* ✅ **CommitLint**: Commit message validation
-* ✅ **Lint-staged**: Linting only modified files
+- ✅ **Husky**: Git hooks
+- ✅ **CommitLint**: Commit message validation
+- ✅ **Lint-staged**: Linting only modified files
 
 ### 7. Useful Commands
 
@@ -115,10 +115,10 @@ npm run release
 
 Settings are located in `.vscode/settings.json`:
 
-* Message validation enabled
-* Predefined scopes for the project
-* Character limit configured
-* Integrated terminal setup
+- Message validation enabled
+- Predefined scopes for the project
+- Character limit configured
+- Integrated terminal setup
 
 ## Key Tips