context-first-cli 2.1.4 → 2.1.6

package/dist/templates/commands/en/engineer/pr.md

@@ -10,32 +10,55 @@ Before creating PRs, make sure that:
 - All tests are passing
 - Documentation is up to date
 
+## 🛑 CRITICAL: WHERE TO WORK
+
+**⚠️ ATTENTION: If you need to make last-minute adjustments, ALL CODE MUST BE CREATED INSIDE THE WORKTREE!**
+
+**✅ CORRECT** - Work inside the worktree:
+```
+<orchestrator>/.sessions/<ISSUE-ID>/<repo-name>/src/file.ts  ✅
+<orchestrator>/.sessions/<ISSUE-ID>/<repo-name>/README.md  ✅
+<orchestrator>/.sessions/<ISSUE-ID>/<repo-name>/CHANGELOG.md  ✅
+```
+
+**❌ WRONG** - NEVER create code outside the worktree:
+```
+<orchestrator>/.sessions/file.ts  ❌
+<orchestrator>/.sessions/<ISSUE-ID>/file.ts  ❌
+{base_path}/<repo-name>/file.ts  ❌ (main repository!)
+```
+
+**ABSOLUTE RULE**:
+- 🛑 **Any code adjustment** (docs, changelog, fixes) **MUST be in** `<orchestrator>/.sessions/<ISSUE-ID>/<repo-name>/`
+- 🛑 **NEVER modify** the main repository in `{base_path}/<repo-name>/`
+- ✅ **Work ONLY** inside the specific repository’s worktree
+
 ## 🎯 PR Creation Process
 
 ### 1. Identify Modified Repositories
 
 For each repository in the workspace, check:
 ```bash
-cd <repositório>
+cd <repository>
 git status
-git log origin/main..HEAD  # View unpushed commits
+git log origin/main..HEAD  # See unpushed commits
 ```
 
 ### 2. Push Branches
 
 For each modified repository:
 ```bash
-cd <repositório>
+cd <repository>
 git push origin <branch-name>
 ```
 
 ### 3. Create Pull Requests
 
-For each repository, create a PR using GitHub CLI or the web interface:
+For each repository, create a PR using GitHub CLI or web interface:
 
 **Using GitHub CLI**:
 ```bash
-cd <repositório>
+cd <repository>
 gh pr create --title "[ISSUE-ID] Feature Title" \
   --body "$(cat ../.sessions/<ISSUE-ID>/pr-description.md)" \
   --base main
@@ -50,7 +73,7 @@ gh pr create --title "[ISSUE-ID] Feature Title" \
 
 ## 📝 Changes
 
-### Repository: <nome-do-repo>
+### Repository: <repo-name>
 
 - [Change 1]
 - [Change 2]
@@ -84,22 +107,22 @@ gh pr create --title "[ISSUE-ID] Feature Title" \
 
 ## 🔍 Notes for Reviewers
 
-- [Point of attention 1]
-- [Point of attention 2]
+- [Attention point 1]
+- [Attention point 2]
 ```
 
 ### 4. Link PRs
 
 If there are multiple PRs (one per repository):
-- Add cross-links between the PRs
-- Document the recommended merge order
+- Add cross-links between PRs
+- Document recommended merge order
 - Indicate dependencies between PRs
 
 ### 5. Update Issue in Task Manager
 
-If the task manager is configured:
+If a task manager is configured:
 - Move the issue to "In Review" or "PR Open"
-- Add PR links in the issue
+- Add PR links to the issue
 - Add a comment summarizing the changes
 
 ### 6. Session Documentation
@@ -126,7 +149,7 @@ Update `./.sessions/<ISSUE-ID>/pr.md`:
 1. <repo-1> - [Justification]
 2. <repo-2> - [Justification]
 
-## Merge Notes
+## Notes for Merge
 
 - [Important note 1]
 - [Important note 2]
@@ -146,7 +169,7 @@ Before requesting review:
 
 Notify the team about the PRs:
 - Mention relevant reviewers
-- Highlight critical changes or breaking changes
+- Highlight critical or breaking changes
 - Indicate urgency if applicable
 
 ---
@@ -161,7 +184,7 @@ Notify the team about the PRs:
 
 ## 🎯 Next Steps
 
-1. Await PR review
+1. Await PR reviews
 2. Respond to comments and make adjustments
 3. After approval, merge in the recommended order
 4. Run `context-cli feature:end <ISSUE-ID>` to clean the workspace

package/dist/templates/commands/en/engineer/pre-pr.md

@@ -4,7 +4,7 @@ This command validates that everything is ready to create Pull Requests.
 
 ## 📋 Prerequisites
 
-- Complete implementation (all `/plan` tasks executed)
+- Complete implementation (all tasks from `/plan` executed)
 - All commits made
 - Clean and organized workspace
 
@@ -12,6 +12,29 @@ This command validates that everything is ready to create Pull Requests.
 
 Ensure that the implementation is complete, tested, and ready for review before creating the PRs.
 
+## 🛑 CRITICAL: WHERE TO WORK
+
+**⚠️ ATTENTION: ALL CODE (tests, fixes, adjustments) MUST BE CREATED INSIDE THE WORKTREE!**
+
+**✅ CORRECT** - Work inside the worktree:
+```
+<orchestrator>/.sessions/<ISSUE-ID>/<repo-name>/src/file.ts  ✅
+<orchestrator>/.sessions/<ISSUE-ID>/<repo-name>/tests/test.ts  ✅
+<orchestrator>/.sessions/<ISSUE-ID>/<repo-name>/.eslintrc.js  ✅
+```
+
+**❌ WRONG** - NEVER create code outside the worktree:
+```
+<orchestrator>/.sessions/test.ts  ❌
+<orchestrator>/.sessions/<ISSUE-ID>/test.ts  ❌
+{base_path}/<repo-name>/test.ts  ❌ (main repository!)
+```
+
+**ABSOLUTE RULE**:
+- 🛑 **ALL code** (tests, fixes, configurations) **MUST be in** `<orchestrator>/.sessions/<ISSUE-ID>/<repo-name>/`
+- 🛑 **NEVER modify** the main repository at `{base_path}/<repo-name>/`
+- ✅ **Work ONLY** inside the specific repository’s worktree
+
 ## ✅ Validation Checklist
 
 ### 1. Implementation Completeness
@@ -19,10 +42,10 @@ Ensure that the implementation is complete, tested, and ready for review before
 ```markdown
 ## Completeness Check
 
-- [ ] All plan tasks have been executed
+- [ ] All tasks from the plan have been executed
 - [ ] All functional requirements from the PRD have been implemented
 - [ ] All acceptance criteria have been met
-- [ ] No functionality is left half-done
+- [ ] No functionality is half-done
 ```
 
 ### 2. Code Quality
@@ -163,7 +186,7 @@ Checklist:
 
 - [ ] Branches are up to date with the base branch (main/develop)
 - [ ] No merge conflicts
-- [ ] Changes between repositories are synchronized
+- [ ] Changes across repositories are synchronized
 - [ ] Dependencies between repos have been tested
 ```
 
@@ -184,7 +207,7 @@ Checklist:
 ## Performance
 
 - [ ] No obvious performance regressions
-- [ ] Costly queries/operations have been optimized
+- [ ] Expensive queries/operations have been optimized
 - [ ] No memory leaks introduced
 - [ ] PRD performance requirements have been met
 ```
@@ -234,16 +257,16 @@ Create `./.sessions/<ISSUE-ID>/pr-description.md`:
 3. [Expected result]
 
 ## 🔍 Notes for Reviewers
-- [Attention point 1]
-- [Attention point 2]
+- [Point of attention 1]
+- [Point of attention 2]
 ```
 
 ## 🚨 Issues Found
 
 If any validation fails:
 1. 🛑 **STOP** the PR creation process
-2. 📝 **DOCUMENT** the issue
-3. 🔧 **FIX** the issue
+2. 📝 **DOCUMENT** the problem
+3. 🔧 **FIX** the problem
 4. 🔄 **RUN** `/pre-pr` again
 
 ## 📊 Validation Report
@@ -253,11 +276,11 @@ Create `./.sessions/<ISSUE-ID>/pre-pr-report.md`:
 ```markdown
 # Pre-PR Validation Report
 
-**Date**: [date/time]
+**Date**: [date/time]  
 **Issue**: [ISSUE-ID]
 
 ## Overall Status
-✅ Ready for PR / ⚠️ Pending / ❌ Blocked
+✅ Ready for PR / ⚠️ Pending Issues / ❌ Blocked
 
 ## Validated Repositories
 - **<repo-1>**: ✅ OK
@@ -268,9 +291,9 @@ Create `./.sessions/<ISSUE-ID>/pre-pr-report.md`:
 - **Integration Tests**: Y/Y passing
 - **Coverage**: Z%
 
-## Pending Items (if any)
-- [Pending item 1]
-- [Pending item 2]
+## Pending Issues (if any)
+- [Pending issue 1]
+- [Pending issue 2]
 
 ## Next Steps
 - [x] All validations passed
@@ -295,4 +318,4 @@ If all validations passed:
 /pr
 ```
 
-This command will create the Pull Requests for all modified repositories.
+This command will create Pull Requests for all modified repositories.

package/dist/templates/commands/en/engineer/work.md

@@ -36,16 +36,40 @@ Before executing, make sure that:
 - ❌ NEVER checkout branches in the main repositories
 - ❌ NEVER navigate to `{base_path}/{repo-id}/`
 
+## 🛑 CRITICAL: WHERE TO CREATE CODE
+
+**⚠️ ATTENTION: ALL CODE MUST BE CREATED INSIDE THE REPOSITORY WORKTREE!**
+
+**✅ CORRECT** - Create code inside the worktree:
+```
+<orchestrator>/.sessions/<ISSUE-ID>/<repo-name>/src/file.ts  ✅
+<orchestrator>/.sessions/<ISSUE-ID>/<repo-name>/tests/test.ts  ✅
+<orchestrator>/.sessions/<ISSUE-ID>/<repo-name>/package.json  ✅
+```
+
+**❌ WRONG** - NEVER create code directly in .sessions:
+```
+<orchestrator>/.sessions/src/file.ts  ❌
+<orchestrator>/.sessions/<ISSUE-ID>/src/file.ts  ❌
+<orchestrator>/.sessions/<ISSUE-ID>/file.ts  ❌
+```
+
+**ABSOLUTE RULE**:
+- 🛑 **EVERY code file** (`.ts`, `.js`, `.py`, `.java`, etc.) **MUST be inside** `<orchestrator>/.sessions/<ISSUE-ID>/<repo-name>/`
+- 🛑 **NEVER create code** directly in `<orchestrator>/.sessions/` or `<orchestrator>/.sessions/<ISSUE-ID>/`
+- ✅ **Only valid place**: Inside the specific repository worktree
+
 ## ⚠️ IMPORTANT: Immutable Files
 
 **This command must READ but NOT MODIFY:**
 - ✅ **READ** `.sessions/<ISSUE-ID>/context.md` (immutable)
 - ✅ **READ** `.sessions/<ISSUE-ID>/architecture.md` (immutable)
 - ✅ **UPDATE** `.sessions/<ISSUE-ID>/plan.md` (mark progress)
-- ✅ **IMPLEMENT** code in the workspace repositories
-- ✅ **MAKE COMMITS** in the workspace repositories
+- ✅ **IMPLEMENT** code **INSIDE THE WORKTREE**: `.sessions/<ISSUE-ID>/<repo-name>/`
+- ✅ **MAKE COMMITS** in the worktrees: `.sessions/<ISSUE-ID>/<repo-name>/`
 - ❌ **DO NOT modify `context.md` or `architecture.md`**
-- ❌ **DO NOT checkout branches in the main repositories (outside workspace)**
+- ❌ **DO NOT checkout branches in the main repositories (outside the workspace)**
+- 🛑 **NEVER create code directly in `.sessions/` or `.sessions/<ISSUE-ID>/`**
 
 ## 📚 Load MetaSpecs
 
@@ -53,8 +77,8 @@ Before executing, make sure that:
 1. Read `context-manifest.json` from the orchestrator
 2. Find the repository with `"role": "metaspecs"`
 3. Read `ai.properties.md` to get the `base_path`
-4. The metaspecs are located at: `{base_path}/{metaspecs-repo-id}/`
-5. Read the relevant `index.md` files during implementation to:
+4. The metaspecs are at: `{base_path}/{metaspecs-repo-id}/`
+5. Read relevant `index.md` files during implementation to:
    - Follow coding standards
    - Respect defined architecture
    - Use correct conventions
@@ -71,7 +95,7 @@ Implement a specific unit of work from the plan, which may involve:
 
 **⚠️ IMPORTANT: PROGRESS CONTROL**
 
-This command executes work in **incremental phases**. After completing each **MAIN PHASE** (e.g., Phase 1 → Phase 2):
+This command executes the work in **incremental phases**. After completing each **MAIN PHASE** (e.g., Phase 1 → Phase 2):
 
 1. 🛑 **STOP** execution
 2. 📊 **PRESENT** a summary of what was done
@@ -84,7 +108,7 @@ This command executes work in **incremental phases**. After completing each **MA
 - ✅ **PAUSE** between main phases (Phase 1 → Phase 2 → Phase 3)
 - ❌ **DO NOT pause** between subphases (Phase 1.1 → Phase 1.2 → Phase 1.3)
 
-**DO NOT implement everything at once**. Work main phase by main phase, waiting for developer confirmation.
+**DO NOT implement everything at once**. Work main phase by main phase, awaiting developer confirmation.
 
 ---
 
@@ -92,7 +116,7 @@ This command executes work in **incremental phases**. After completing each **MA
 
 Based on the technical plan (`./.sessions/<ISSUE-ID>/plan.md`), identify:
 - Which specific task will be implemented now
-- In which workspace repository(ies)
+- In which repository(ies) of the workspace
 - Which files will be created/modified
 - Dependencies with other tasks
 
@@ -100,7 +124,7 @@ Based on the technical plan (`./.sessions/<ISSUE-ID>/plan.md`), identify:
 
 
 
-**IMPORTANT**: Work ONLY inside the workspace at `.sessions/<ISSUE-ID>/`
+**IMPORTANT**: Work ONLY inside the workspace in `.sessions/<ISSUE-ID>/`
 
 For each repository in the workspace:
 
@@ -133,7 +157,7 @@ Before committing:
 
 ### 4. Commit
 
-For each modified repository **inside the workspace**:
+For each repository modified **inside the workspace**:
 
 ```bash
 # Navigate to the worktree inside the workspace

package/dist/templates/commands/es/engineer/pr.md

@@ -5,18 +5,41 @@ Este comando crea Pull Requests para todos los repositorios modificados en el wo
 ## 📋 Requisitos previos
 
 Antes de crear PRs, asegúrate de que:
-- Has ejecutado `/pre-pr` y todas las validaciones pasaron
+- Ejecutaste `/pre-pr` y todas las validaciones pasaron
 - Todos los commits fueron realizados
 - Todas las pruebas están pasando
 - La documentación está actualizada
 
+## 🛑 CRÍTICO: DÓNDE TRABAJAR
+
+**⚠️ ATENCIÓN: Si necesitas hacer ajustes de última hora, ¡TODO EL CÓDIGO DEBE SER CREADO DENTRO DEL WORKTREE!**
+
+**✅ CORRECTO** - Trabajar dentro del worktree:
+```
+<orchestrator>/.sessions/<ISSUE-ID>/<repo-name>/src/file.ts  ✅
+<orchestrator>/.sessions/<ISSUE-ID>/<repo-name>/README.md  ✅
+<orchestrator>/.sessions/<ISSUE-ID>/<repo-name>/CHANGELOG.md  ✅
+```
+
+**❌ INCORRECTO** - NUNCA crear código fuera del worktree:
+```
+<orchestrator>/.sessions/file.ts  ❌
+<orchestrator>/.sessions/<ISSUE-ID>/file.ts  ❌
+{base_path}/<repo-name>/file.ts  ❌ (¡repositorio principal!)
+```
+
+**REGLA ABSOLUTA**:
+- 🛑 **Cualquier ajuste de código** (docs, changelog, fixes) **DEBE estar en** `<orchestrator>/.sessions/<ISSUE-ID>/<repo-name>/`
+- 🛑 **NUNCA modifiques** el repositorio principal en `{base_path}/<repo-name>/`
+- ✅ **Trabaja SÓLO** dentro del worktree del repositorio específico
+
 ## 🎯 Proceso de Creación de PRs
 
 ### 1. Identificar Repositorios Modificados
 
 Para cada repositorio en el workspace, verifica:
 ```bash
-cd <repositório>
+cd <repositorio>
 git status
 git log origin/main..HEAD  # Ver commits no pushados
 ```
@@ -25,7 +48,7 @@ git log origin/main..HEAD  # Ver commits no pushados
 
 Para cada repositorio modificado:
 ```bash
-cd <repositório>
+cd <repositorio>
 git push origin <branch-name>
 ```
 
@@ -35,7 +58,7 @@ Para cada repositorio, crea un PR usando el GitHub CLI o la interfaz web:
 
 **Usando GitHub CLI**:
 ```bash
-cd <repositório>
+cd <repositorio>
 gh pr create --title "[ISSUE-ID] Título de la Feature" \
   --body "$(cat ../.sessions/<ISSUE-ID>/pr-description.md)" \
   --base main
@@ -50,7 +73,7 @@ gh pr create --title "[ISSUE-ID] Título de la Feature" \
 
 ## 📝 Cambios
 
-### Repositorio: <nome-do-repo>
+### Repositorio: <nombre-del-repo>
 
 - [Cambio 1]
 - [Cambio 2]
@@ -70,17 +93,17 @@ gh pr create --title "[ISSUE-ID] Título de la Feature" \
 - [ ] Pruebas de integración pasando
 - [ ] Documentación actualizada
 - [ ] Sin breaking changes (o documentados)
-- [ ] Revisado por pares (después de crear el PR)
+- [ ] Revisado por pares (tras creación del PR)
 
-## 🧪 Cómo Testear
+## 🧪 Cómo Probar
 
 1. [Paso 1]
 2. [Paso 2]
 3. [Resultado esperado]
 
-## 📸 Screenshots/Demos
+## 📸 Capturas/Demos
 
-[Si aplica, añade capturas de pantalla o enlaces a demos]
+[Si aplica, añade capturas o enlaces a demos]
 
 ## 🔍 Notas para Revisores
 
@@ -112,12 +135,12 @@ Actualiza `./.sessions/<ISSUE-ID>/pr.md`:
 ## PRs Creados
 
 ### <repo-1>
-- **Link**: <URL del PR>
+- **Enlace**: <URL del PR>
 - **Estado**: Abierto
 - **Commits**: X commits
 
 ### <repo-2>
-- **Link**: <URL del PR>
+- **Enlace**: <URL del PR>
 - **Estado**: Abierto
 - **Commits**: Y commits
 
@@ -163,5 +186,5 @@ Notifica al equipo sobre los PRs:
 
 1. Esperar revisión de los PRs
 2. Responder comentarios y hacer ajustes
-3. Tras la aprobación, hacer merge en el orden recomendado
+3. Tras aprobación, hacer merge en el orden recomendado
 4. Ejecutar `context-cli feature:end <ISSUE-ID>` para limpiar el workspace

package/dist/templates/commands/es/engineer/pre-pr.md

@@ -12,6 +12,29 @@ Este comando valida que todo está listo para crear Pull Requests.
 
 Garantizar que la implementación está completa, probada y lista para revisión antes de crear los PRs.
 
+## 🛑 CRÍTICO: DÓNDE TRABAJAR
+
+**⚠️ ATENCIÓN: TODO CÓDIGO (tests, fixes, ajustes) DEBE SER CREADO DENTRO DEL WORKTREE!**
+
+**✅ CORRECTO** - Trabajar dentro del worktree:
+```
+<orchestrator>/.sessions/<ISSUE-ID>/<repo-name>/src/file.ts  ✅
+<orchestrator>/.sessions/<ISSUE-ID>/<repo-name>/tests/test.ts  ✅
+<orchestrator>/.sessions/<ISSUE-ID>/<repo-name>/.eslintrc.js  ✅
+```
+
+**❌ INCORRECTO** - NUNCA crear código fuera del worktree:
+```
+<orchestrator>/.sessions/test.ts  ❌
+<orchestrator>/.sessions/<ISSUE-ID>/test.ts  ❌
+{base_path}/<repo-name>/test.ts  ❌ (¡repositorio principal!)
+```
+
+**REGLA ABSOLUTA**:
+- 🛑 **TODO código** (tests, fixes, configuraciones) **DEBE estar en** `<orchestrator>/.sessions/<ISSUE-ID>/<repo-name>/`
+- 🛑 **NUNCA modifiques** el repositorio principal en `{base_path}/<repo-name>/`
+- ✅ **Trabaja SOLO** dentro del worktree del repositorio específico
+
 ## ✅ Checklist de Validación
 
 ### 1. Completitud de la Implementación
@@ -79,14 +102,14 @@ Checklist:
 - [ ] Sin warnings críticos
 ```
 
-### 3. Pruebas
+### 3. Tests
 
 Para cada repositorio:
 
 ```bash
 cd <repositorio>
 
-# Ejecutar pruebas unitarias (ejemplos por stack):
+# Ejecutar tests unitarios (ejemplos por stack):
 # Node.js: npm run test:unit / jest / vitest
 # Python: pytest tests/unit / python -m unittest
 # Java: mvn test / gradle test
@@ -96,7 +119,7 @@ cd <repositorio>
 # PHP: ./vendor/bin/phpunit --testsuite=unit
 # C#: dotnet test --filter Category=Unit
 
-# Ejecutar pruebas de integración (ejemplos por stack):
+# Ejecutar tests de integración (ejemplos por stack):
 # Node.js: npm run test:integration
 # Python: pytest tests/integration
 # Java: mvn verify / gradle integrationTest
@@ -117,19 +140,19 @@ cd <repositorio>
 
 Checklist:
 ```markdown
-## Pruebas
+## Tests
 
 ### <repo-1>
-- [ ] Todas las pruebas unitarias pasando
-- [ ] Todas las pruebas de integración pasando
-- [ ] Cobertura de pruebas adecuada (>= X%)
-- [ ] Nuevas pruebas añadidas para nuevas funcionalidades
+- [ ] Todos los tests unitarios pasan
+- [ ] Todos los tests de integración pasan
+- [ ] Cobertura de tests adecuada (>= X%)
+- [ ] Nuevos tests añadidos para nuevas funcionalidades
 
 ### <repo-2>
-- [ ] Todas las pruebas unitarias pasando
-- [ ] Todas las pruebas de integración pasando
-- [ ] Cobertura de pruebas adecuada (>= X%)
-- [ ] Nuevas pruebas añadidas para nuevas funcionalidades
+- [ ] Todos los tests unitarios pasan
+- [ ] Todos los tests de integración pasan
+- [ ] Cobertura de tests adecuada (>= X%)
+- [ ] Nuevos tests añadidos para nuevas funcionalidades
 ```
 
 ### 4. Documentación
@@ -141,7 +164,7 @@ Checklist:
 - [ ] Comentarios de código adecuados
 - [ ] Documentación de APIs actualizada (si hay cambios)
 - [ ] Changelog actualizado
-- [ ] Documentación técnica actualizada en las metaspecs (si aplica)
+- [ ] Documentación técnica actualizada en metaspecs (si aplica)
 ```
 
 ### 5. Commits
@@ -150,9 +173,9 @@ Checklist:
 ## Commits
 
 - [ ] Todos los commits tienen mensajes claros y descriptivos
-- [ ] Los commits siguen el estándar del proyecto (conventional commits, etc.)
+- [ ] Commits siguen el estándar del proyecto (conventional commits, etc.)
 - [ ] No hay commits con mensajes genéricos ("fix", "update", etc.)
-- [ ] Los commits están organizados lógicamente
+- [ ] Commits están organizados lógicamente
 - [ ] No hay commits de debug o temporales
 ```
 
@@ -161,7 +184,7 @@ Checklist:
 ```markdown
 ## Sincronización
 
-- [ ] Las branches están actualizadas con la branch base (main/develop)
+- [ ] Branches están actualizadas con la branch base (main/develop)
 - [ ] No hay conflictos de merge
 - [ ] Cambios entre repositorios están sincronizados
 - [ ] Dependencias entre repos fueron probadas
@@ -172,7 +195,7 @@ Checklist:
 ```markdown
 ## Seguridad
 
-- [ ] No hay credenciales ni secrets en el código
+- [ ] No hay credenciales o secretos en el código
 - [ ] No hay datos sensibles en logs
 - [ ] Dependencias de seguridad fueron verificadas
 - [ ] No hay vulnerabilidades conocidas introducidas
@@ -183,7 +206,7 @@ Checklist:
 ```markdown
 ## Performance
 
-- [ ] No hay regresiones de performance evidentes
+- [ ] No hay regresiones de performance obvias
 - [ ] Queries/operaciones costosas fueron optimizadas
 - [ ] No hay memory leaks introducidos
 - [ ] Requisitos de performance del PRD fueron cumplidos
@@ -191,7 +214,7 @@ Checklist:
 
 ## 🔍 Validación Cruzada
 
-Si se modificaron múltiples repositorios:
+Si múltiples repositorios fueron modificados:
 
 ```markdown
 ## Validación Cruzada
@@ -199,12 +222,12 @@ Si se modificaron múltiples repositorios:
 - [ ] Probé la integración entre los repositorios localmente
 - [ ] APIs/contratos entre repos están consistentes
 - [ ] No hay breaking changes no documentados
-- [ ] El orden de deploy/merge está claro
+- [ ] Orden de deploy/merge está claro
 ```
 
 ## 📄 Preparación de la Descripción del PR
 
-Cree `./.sessions/<ISSUE-ID>/pr-description.md`:
+Crea `./.sessions/<ISSUE-ID>/pr-description.md`:
 
 ```markdown
 ## 🎯 Objetivo
@@ -215,15 +238,15 @@ Cree `./.sessions/<ISSUE-ID>/pr-description.md`:
 - [Cambio 2]
 - [Cambio 3]
 
-## 🔗 Enlaces
+## 🔗 Links
 - **Issue**: [ISSUE-ID]
 - **PRD**: [link o ruta]
 - **Plan Técnico**: [link o ruta]
 
 ## ✅ Checklist
 - [x] Código implementado y probado
-- [x] Pruebas unitarias añadidas/actualizadas
-- [x] Pruebas de integración pasando
+- [x] Tests unitarios añadidos/actualizados
+- [x] Tests de integración pasando
 - [x] Documentación actualizada
 - [x] Linting y formateo OK
 - [x] Build sin errores
@@ -241,17 +264,17 @@ Cree `./.sessions/<ISSUE-ID>/pr-description.md`:
 ## 🚨 Problemas Encontrados
 
 Si alguna validación falla:
-1. 🛑 **PARE** el proceso de creación de PR
-2. 📝 **DOCUMENTE** el problema
-3. 🔧 **CORRIJA** el problema
-4. 🔄 **EJECUTE** `/pre-pr` nuevamente
+1. 🛑 **DETÉN** el proceso de creación de PR
+2. 📝 **DOCUMENTA** el problema
+3. 🔧 **CORRIGE** el problema
+4. 🔄 **EJECUTA** `/pre-pr` nuevamente
 
-## 📊 Informe de Validación
+## 📊 Reporte de Validación
 
-Cree `./.sessions/<ISSUE-ID>/pre-pr-report.md`:
+Crea `./.sessions/<ISSUE-ID>/pre-pr-report.md`:
 
 ```markdown
-# Informe de Validación Pre-PR
+# Reporte de Validación Pre-PR
 
 **Fecha**: [fecha/hora]
 **Issue**: [ISSUE-ID]
@@ -263,12 +286,12 @@ Cree `./.sessions/<ISSUE-ID>/pre-pr-report.md`:
 - **<repo-1>**: ✅ OK
 - **<repo-2>**: ✅ OK
 
-## Resumen de Pruebas
-- **Pruebas Unitarias**: X/X pasando
-- **Pruebas de Integración**: Y/Y pasando
+## Resumen de Tests
+- **Tests Unitarios**: X/X pasando
+- **Tests de Integración**: Y/Y pasando
 - **Cobertura**: Z%
 
-## Pendientes (si las hay)
+## Pendientes (si hay)
 - [Pendiente 1]
 - [Pendiente 2]