@haposoft/cafekit 0.3.7 → 0.3.12

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@haposoft/cafekit",
-  "version": "0.3.7",
+  "version": "0.3.12",
   "description": "Spec-Driven Development workflow for AI coding assistants. Supports Claude Code and Antigravity with spec-first and code-test-review workflows.",
   "author": "Haposoft <nghialt@haposoft.com>",
   "license": "MIT",
@@ -37,4 +37,4 @@
   "engines": {
     "node": ">=18.0.0"
   }
-}
+}

package/src/antigravity/workflows/impact-analysis.md

@@ -1,12 +1,12 @@
 ---
-description: Phân tích tác động của code changes lên tính năng và hành động người dùng
+description: Analyze code change impacts on features and user actions
 allowed-tools: Read, Glob, Grep, Bash, WebSearch
 argument-hint: <feature-name> [--from <branch>]
 ---
 
-# /impact-analysis - Phân Tích Tác Động Tính Năng
+# /impact-analysis - Feature Impact Analysis
 
-Sử dụng workflow này sau khi hoàn thành feature (sau `/code`) hoặc trước khi commit.
+Use this workflow after completing a feature (after `/code`) or before committing.
 
 <background_information>
 - **Mission**: Comprehensive impact analysis for completed features to prevent regression bugs
@@ -16,8 +16,8 @@ Sử dụng workflow này sau khi hoàn thành feature (sau `/code`) hoặc trư
   - Test scenarios generated for all critical paths
   - Regression risks assessed with mitigation recommendations
   - Cross-referenced with spec artifacts when available
-- **Timing**: After implementing all tasks for a feature, before running `/test`
-- **Helper Scripts**: Optionally use advanced analysis scripts from `.claude/skills/impact-analysis/scripts/` for automated dependency analysis, AST-based semantic analysis, and risk scoring
+- **Timing**: After implementing all tasks for a feature, before running tests
+- **Helper Scripts**: Optionally use advanced analysis scripts from `.agent/skills/impact-analysis/scripts/` for automated dependency analysis, AST-based semantic analysis, and risk scoring
 </background_information>
 
 <instructions>
@@ -26,11 +26,11 @@ Analyze the impact of code changes for feature **$ARGUMENTS** to identify affect
 
 ## Helper Scripts (Optional Enhancement)
 
-If available in `.claude/skills/impact-analysis/scripts/`, these scripts provide advanced automated analysis:
+If available in `.agent/skills/impact-analysis/scripts/`, these scripts provide advanced automated analysis:
 
 **1. Dependency Analysis**:
 ```bash
-.claude/skills/impact-analysis/scripts/find-dependencies.sh <file>
+.agent/skills/impact-analysis/scripts/find-dependencies.sh <file>
 ```
 - Finds all files importing/using the changed file
 - Identifies API consumers and component usage
@@ -38,7 +38,7 @@ If available in `.claude/skills/impact-analysis/scripts/`, these scripts provide
 
 **2. AST-Based Analysis** (for TypeScript/JavaScript):
 ```bash
-node .claude/skills/impact-analysis/scripts/ast-analyze.js <file>
+node .agent/skills/impact-analysis/scripts/ast-analyze.js <file>
 ```
 - Detects function signature changes
 - Identifies breaking changes
@@ -46,7 +46,7 @@ node .claude/skills/impact-analysis/scripts/ast-analyze.js <file>
 
 **3. Risk Calculation**:
 ```bash
-node .claude/skills/impact-analysis/scripts/calculate-risk.js
+node .agent/skills/impact-analysis/scripts/calculate-risk.js
 ```
 - Calculates risk score (0-25)
 - Determines risk level (CRITICAL/HIGH/MEDIUM/LOW)
@@ -54,7 +54,7 @@ node .claude/skills/impact-analysis/scripts/calculate-risk.js
 
 **4. Complete Analysis**:
 ```bash
-.claude/skills/impact-analysis/scripts/run-analysis.sh
+.agent/skills/impact-analysis/scripts/run-analysis.sh
 ```
 - Runs all techniques
 - Generates comprehensive markdown report
@@ -160,8 +160,7 @@ Scan file contents for keywords to detect additional features:
 
 If helper script available, run comprehensive analysis:
 ```bash
-# Run dependency analysis script for each changed file
-.claude/skills/impact-analysis/scripts/find-dependencies.sh <file>
+.agent/skills/impact-analysis/scripts/find-dependencies.sh <file>
 ```
 
 **Manual Dependency Analysis** (fallback):
@@ -200,11 +199,8 @@ For each changed file, find:
 
 **Option 1: Use Helper Scripts** (if available):
 ```bash
-# Run AST analysis for TypeScript/JavaScript files
-node .claude/skills/impact-analysis/scripts/ast-analyze.js <file>
-
-# Run risk calculation
-node .claude/skills/impact-analysis/scripts/calculate-risk.js
+node .agent/skills/impact-analysis/scripts/ast-analyze.js <file>
+node .agent/skills/impact-analysis/scripts/calculate-risk.js
 ```
 
 **Option 2: Manual Detection** (fallback):
@@ -328,8 +324,7 @@ For each affected feature and user action, generate:
 **Automated Risk Assessment** (if helper script available):
 
 ```bash
-# Run comprehensive risk calculation
-node .claude/skills/impact-analysis/scripts/calculate-risk.js
+node .agent/skills/impact-analysis/scripts/calculate-risk.js
 
 # Output includes:
 # - Risk score (0-25)

package/src/common/skills/impact-analysis/references/change-detection.md

@@ -1,54 +1,54 @@
-# Change Detection - Phát Hiện Thay Đổi
+# Change Detection - Detecting Changes
 
-Phương pháp phát hiện và phân loại code changes để phân tích tác động.
+Methods for detecting and classifying code changes for impact analysis.
 
 ## Git Commands
 
 ### 1. Detect Recent Changes
 
 ```bash
-# Changes chưa commit
+# Uncommitted changes
 git diff --name-only
 
-# Changes đã staged
+# Staged changes
 git diff --cached --name-only
 
-# Changes trong commit gần nhất
+# Changes in last commit
 git diff --name-only HEAD~1
 
-# Changes so với branch khác
+# Changes compared to another branch
 git diff --name-only main...HEAD
 
-# Xem chi tiết thay đổi
+# View detailed changes
 git diff HEAD~1
 
-# Xem thống kê
+# View statistics
 git diff --stat HEAD~1
 ```
 
 ### 2. Get Change Details
 
 ```bash
-# Số dòng thay đổi
+# Lines changed
 git diff --numstat HEAD~1
 
-# Files và số lượng changes
+# Files and change count
 git diff --shortstat HEAD~1
 
-# Chỉ xem added/deleted files
+# Only view added/deleted files
 git diff --diff-filter=AD --name-only HEAD~1
 ```
 
 ### 3. Historical Analysis
 
 ```bash
-# Xem lịch sử file
+# View file history
 git log --oneline -10 {file}
 
-# Xem ai sửa dòng nào
+# See who modified which line
 git blame {file}
 
-# Xem changes của commit cụ thể
+# View changes in specific commit
 git show {commit-hash}
 ```
 
@@ -57,7 +57,7 @@ git show {commit-hash}
 ### Backend Changes
 
 **Indicators:**
-- Files: `*.ts`, `*.js`, `*.py`, `*.go` trong `src/api/`, `src/services/`, `src/controllers/`
+- Files: `*.ts`, `*.js`, `*.py`, `*.go` in `src/api/`, `src/services/`, `src/controllers/`
 - Patterns: API routes, database queries, business logic
 
 **Risk Level:**
@@ -79,7 +79,7 @@ grep -r "SELECT\|INSERT\|UPDATE\|DELETE" {changed-files}
 ### Frontend Changes
 
 **Indicators:**
-- Files: `*.tsx`, `*.jsx`, `*.vue`, `*.svelte` trong `src/components/`, `src/pages/`
+- Files: `*.tsx`, `*.jsx`, `*.vue`, `*.svelte` in `src/components/`, `src/pages/`
 - Patterns: Components, hooks, state management
 
 **Risk Level:**

package/src/common/skills/impact-analysis/references/dependency-scouting.md

@@ -1,12 +1,12 @@
-# Dependency Scouting - Tìm Files Bị Ảnh Hưởng
+# Dependency Scouting - Finding Affected Files
 
-Phương pháp tìm kiếm và phân tích dependencies để xác định phạm vi tác động.
+Methods for finding and analyzing dependencies to determine impact scope.
 
 ## Scouting Strategies
 
 ### 1. Import Analysis (Direct Dependencies)
 
-Tìm files import code đã sửa:
+Find files that import the modified code:
 
 ```bash
 # JavaScript/TypeScript
@@ -35,7 +35,7 @@ grep -r "from.*utils/auth" src/
 
 ### 2. Function/Class Usage (Reverse Dependencies)
 
-Tìm nơi sử dụng functions/classes:
+Find where functions/classes are used:
 
 ```bash
 # Function calls
@@ -60,7 +60,7 @@ grep -r "validateEmail(" src/
 
 ### 3. API Endpoint Consumers
 
-Nếu sửa backend API, tìm frontend calls:
+If backend API is modified, find frontend calls:
 
 ```bash
 # Fetch/Axios calls
@@ -84,7 +84,7 @@ grep -r "api/users" src/
 
 ### 4. Database Dependencies
 
-Nếu sửa database schema:
+If database schema is modified:
 
 ```bash
 # Table usage
@@ -109,7 +109,7 @@ grep -r "prisma.user.findMany" src/
 
 ### 5. Type/Interface Dependencies
 
-Tìm nơi sử dụng types:
+Find where types are used:
 
 ```bash
 # TypeScript interfaces
@@ -134,7 +134,7 @@ grep -r "as User" src/
 
 ## Using /ck:scout for Parallel Scouting
 
-Khi có nhiều files thay đổi, sử dụng `/ck:scout` để parallel search:
+When multiple files change, use `/ck:scout` for parallel search:
 
 ```
 /ck:scout Scout dependencies for changes.

package/src/common/skills/impact-analysis/references/edge-case-identification.md

@@ -1,6 +1,6 @@
-# Edge Case Identification - Xác Định Edge Cases
+# Edge Case Identification - Identifying Edge Cases
 
-Phương pháp phát hiện và phân tích edge cases để tránh bugs tiềm ẩn.
+Methods for detecting and analyzing edge cases to avoid potential bugs.
 
 ## Edge Case Categories
 
@@ -23,10 +23,10 @@ function getUser(id: string) {
 ```
 
 **Check:**
-- [ ] Có check null/undefined trước khi access?
-- [ ] Optional chaining (`?.`) được sử dụng?
-- [ ] Nullish coalescing (`??`) cho default values?
-- [ ] Type guards cho union types?
+- [ ] Check null/undefined before access?
+- [ ] Optional chaining (`?.`) used?
+- [ ] Nullish coalescing (`??`) for default values?
+- [ ] Type guards for union types?
 
 #### Empty Collections
 
@@ -39,9 +39,9 @@ const firstUser = users.length > 0 ? users[0].name : null;
 ```
 
 **Check:**
-- [ ] Array.length check trước khi access index?
-- [ ] Empty array handling trong map/filter/reduce?
-- [ ] Object.keys() check trước khi iterate?
+- [ ] Array.length check before accessing index?
+- [ ] Empty array handling in map/filter/reduce?
+- [ ] Object.keys() check before iterating?
 
 #### Type Coercion
 
@@ -54,8 +54,8 @@ if (value !== null && value !== undefined) { }
 ```
 
 **Check:**
-- [ ] Strict equality (`===`) thay vì loose (`==`)?
-- [ ] Explicit type checks cho boolean logic?
+- [ ] Strict equality (`===`) instead of loose (`==`)?
+- [ ] Explicit type checks for boolean logic?
 - [ ] Number validation (isNaN, isFinite)?
 
 ### 2. Boundary Conditions

package/src/common/skills/impact-analysis/references/industry-techniques.md

@@ -1,10 +1,10 @@
 # Industry Techniques - Code Change Impact Analysis
 
-Tổng hợp các kỹ thuật và công cụ phân tích tác động code changes từ industry và research.
+Compilation of techniques and tools for analyzing code change impacts from industry and research.
 
-## 📚 Nguồn Tham Khảo
+## 📚 References
 
-Dựa trên research và industry best practices từ:
+Based on research and industry best practices from:
 - Academic papers (ACM, ResearchGate, arXiv)
 - Static analysis tools (NDepend, CppDepend, SonarQube)
 - Software engineering practices
@@ -12,22 +12,22 @@ Dựa trên research và industry best practices từ:
 
 ---
 
-## 🎯 Các Phương Pháp Chính
+## 🎯 Main Methods
 
 ### 1. Traceability-Based Impact Analysis
 
-**Khái niệm:**
-Sử dụng links giữa requirements, specifications, design elements, và tests để xác định phạm vi thay đổi.
+**Concept:**
+Use links between requirements, specifications, design elements, and tests to determine scope of changes.
 
-**Cách hoạt động:**
+**How it works:**
 ```
 Requirement → Design → Code → Tests
      ↓           ↓        ↓       ↓
   Change    → Impact → Affected → Test Cases
 ```
 
-**Ứng dụng trong Impact Analysis:**
-- Map code changes về requirements
+**Application in Impact Analysis:**
+- Map code changes to requirements
 - Identify affected user stories
 - Generate test scenarios từ requirements
 
@@ -53,10 +53,10 @@ Requirement → Design → Code → Tests
 
 ### 2. Dependency-Based Impact Analysis
 
-**Khái niệm:**
-Phân tích dependencies (imports, function calls, class usage) để tìm affected files.
+**Concept:**
+Analyze dependencies (imports, function calls, class usage) to find affected files.
 
-**Cách hoạt động:**
+**How it works:**
 
 #### A. Call Graph Analysis
 ```
@@ -92,7 +92,7 @@ Module B imports Module C
 - **Madge** (JavaScript): Circular dependency detection
 - **jdeps** (Java): Package dependencies
 
-**Ứng dụng:**
+**Application:**
 ```bash
 # Find all files importing authService
 grep -r "from.*authService" src/
@@ -108,10 +108,10 @@ madge --image graph.png src/
 
 ### 3. AST-Based Impact Analysis
 
-**Khái niệm:**
-Sử dụng Abstract Syntax Tree để phân tích code structure và detect changes ở semantic level.
+**Concept:**
+Use Abstract Syntax Tree to analyze code structure and detect changes at semantic level.
 
-**Cách hoạt động:**
+**How it works:**
 ```
 Source Code → Parser → AST → Analysis → Impact Report
 ```
@@ -147,9 +147,9 @@ function login(email, password, rememberMe) {
 - **Python ast module**: Python AST analysis
 - **Roslyn** (.NET): C# AST analysis
 
-**Ứng dụng:**
+**Application:**
 ```javascript
-// Detect function signature changes
+# Detect function signature changes
 const ast = parse(sourceCode);
 ast.body.forEach(node => {
   if (node.type === 'FunctionDeclaration') {
@@ -163,8 +163,8 @@ ast.body.forEach(node => {
 
 ### 4. Static Analysis-Based Impact
 
-**Khái niệm:**
-Analyze code without executing để detect issues, dependencies, và potential impacts.
+**Concept:**
+Analyze code without executing to detect issues, dependencies, and potential impacts.
 
 **Techniques:**
 
@@ -244,10 +244,10 @@ interface User {
 
 ### 5. Model-Based Impact Analysis
 
-**Khái niệm:**
-Sử dụng models (UML, architecture diagrams) để predict impact trước khi code.
+**Concept:**
+Use models (UML, architecture diagrams) to predict impact before coding.
 
-**Cách hoạt động:**
+**How it works:**
 ```
 Architecture Model → Component Dependencies → Impact Prediction
 ```
@@ -272,10 +272,10 @@ Architecture Model → Component Dependencies → Impact Prediction
 
 ### 6. Test-Based Impact Analysis
 
-**Khái niệm:**
-Sử dụng test coverage để identify affected tests và features.
+**Concept:**
+Use test coverage to identify affected tests and features.
 
-**Cách hoạt động:**
+**How it works:**
 ```
 Code Change → Test Coverage Map → Affected Tests → Affected Features
 ```
@@ -299,7 +299,7 @@ Code Change → Test Coverage Map → Affected Tests → Affected Features
 - **JaCoCo**: Java code coverage
 - **Istanbul**: JavaScript coverage
 
-**Ứng dụng:**
+**Application:**
 ```bash
 # Run tests with coverage
 npm test -- --coverage
@@ -315,10 +315,10 @@ jest --coverage --coverageReporters=html
 
 ### 7. Behavior-Driven Impact Analysis
 
-**Khái niệm:**
-Map code changes về user behaviors và scenarios (BDD approach).
+**Concept:**
+Map code changes to user behaviors and scenarios (BDD approach).
 
-**Cách hoạt động:**
+**How it works:**
 ```
 Code Change → Feature Mapping → User Scenarios → Test Scenarios
 ```
@@ -367,8 +367,8 @@ describe('Biometric Login', () => {
 
 ### 8. Feature Mapping Techniques
 
-**Khái niệm:**
-Map code files về features và user actions.
+**Concept:**
+Map code files to features and user actions.
 
 **Techniques:**
 
@@ -423,10 +423,10 @@ export function login(email: string, password: string) {
 
 ### 9. Machine Learning-Based Impact Analysis
 
-**Khái niệm:**
-Sử dụng ML models để predict impact dựa trên historical data.
+**Concept:**
+Use ML models to predict impact based on historical data.
 
-**Cách hoạt động:**
+**How it works:**
 ```
 Historical Changes + Outcomes → ML Model → Predict Impact
 ```
@@ -547,7 +547,7 @@ Code Change → Feature Impact → User Action Impact → Test Scenarios
 
 ### 4. Prioritize by Risk
 
-Sử dụng risk scoring:
+Use risk scoring:
 
 ```javascript
 const riskScore = 

package/src/common/skills/impact-analysis/references/practical-techniques-guide.md

@@ -14,8 +14,8 @@ Document này cung cấp:
 
 ## 🎯 Technique #1: Dependency Analysis (MUST HAVE)
 
-### Mục Đích
-Tìm tất cả files bị ảnh hưởng bởi code changes.
+### Purpose
+Find all files affected by code changes.
 
 ### Tools & Commands
 
@@ -23,7 +23,7 @@ Tìm tất cả files bị ảnh hưởng bởi code changes.
 
 **1. Find Direct Imports**
 ```bash
-# Tìm files import module đã sửa
+# Find files importing modified module
 grep -r "from.*authService" src/ --include="*.ts" --include="*.tsx"
 grep -r "import.*authService" src/ --include="*.ts" --include="*.tsx"
 
@@ -33,7 +33,7 @@ rg "from.*authService" src/ -t ts -t tsx
 
 **2. Find Function Calls**
 ```bash
-# Tìm files gọi function đã sửa
+# Find files calling modified function
 grep -r "login\(" src/ --include="*.ts" --include="*.tsx"
 
 # Exclude test files
@@ -57,7 +57,7 @@ madge src/services/authService.ts
 
 **4. Find API Consumers**
 ```bash
-# Tìm frontend components gọi API
+# Find frontend components calling API
 grep -r "fetch.*\/api\/auth" src/
 grep -r "axios.*\/api\/auth" src/
 grep -r "\/api\/auth" src/ --include="*.ts" --include="*.tsx"
@@ -67,7 +67,7 @@ grep -r "\/api\/auth" src/ --include="*.ts" --include="*.tsx"
 
 **Find Component Usage**
 ```bash
-# Tìm components sử dụng component đã sửa
+# Find components using modified component
 grep -r "<LoginButton" src/ --include="*.tsx"
 grep -r "LoginButton" src/ --include="*.tsx" | grep "import"
 ```
@@ -111,8 +111,8 @@ grep -r "login(" . --include="*.py"
 
 ## 🎯 Technique #2: AST-Based Analysis (NICE TO HAVE)
 
-### Mục Đích
-Phát hiện semantic changes (function signature, type changes, breaking changes).
+### Purpose
+Detect semantic changes (function signature, type changes, breaking changes).
 
 ### Tools & Setup
 
@@ -222,8 +222,8 @@ diff /tmp/before.json /tmp/after.json
 
 ## 🎯 Technique #3: Static Analysis (NICE TO HAVE)
 
-### Mục Đích
-Phát hiện code quality issues, security issues, và potential bugs.
+### Purpose
+Detect code quality issues, security issues, and potential bugs.
 
 ### Tools
 
@@ -284,8 +284,8 @@ sonar-scanner \
 
 ## 🎯 Technique #4: Test Coverage Analysis (SHOULD HAVE)
 
-### Mục Đích
-Tìm tests bị ảnh hưởng và identify untested code.
+### Purpose
+Find affected tests and identify untested code.
 
 ### Tools & Commands
 
@@ -370,8 +370,8 @@ pytest --collect-only | grep auth_service
 
 ## 🎯 Technique #5: Feature Mapping (MUST HAVE)
 
-### Mục Đích
-Map code changes về features và user actions.
+### Purpose
+Map code changes to features and user actions.
 
 ### Implementation
 
@@ -478,8 +478,8 @@ function mapFeatures(changedFiles) {
 
 ## 🎯 Technique #6: Risk Scoring (SHOULD HAVE)
 
-### Mục Đích
-Đánh giá mức độ risk của changes.
+### Purpose
+Assess risk level of changes.
 
 ### Algorithm
 

package/src/common/skills/impact-analysis/references/project-detection.md

@@ -1,6 +1,6 @@
 # Project Detection - Auto-Adapt Impact Analysis
 
-Hệ thống tự động detect và adapt Impact Analysis cho nhiều loại projects.
+System to automatically detect and adapt Impact Analysis for different project types.
 
 ## Project Type Detection
 

package/src/common/skills/impact-analysis/references/report-template.md

@@ -1,6 +1,6 @@
-# Report Template - Mẫu Báo Cáo Impact Analysis
+# Report Template - Impact Analysis Report Template
 
-Template chuẩn cho báo cáo phân tích tác động và hướng dẫn test.
+Standard template for impact analysis reports and test guidance.
 
 ## Full Report Template
 

package/src/common/skills/impact-analysis/scripts/README.md

@@ -1,15 +1,15 @@
 # Impact Analysis Scripts
 
-Helper scripts để thực hiện advanced impact analysis techniques.
+Helper scripts for performing advanced impact analysis techniques.
 
 ## 📋 Overview
 
-Các scripts này implement industry techniques từ `references/industry-techniques.md`:
+These scripts implement industry techniques from `references/industry-techniques.md`:
 
 1. **ast-analyze.js** - AST-based analysis (Technique #3)
 2. **find-dependencies.sh** - Dependency analysis (Technique #2)
 3. **calculate-risk.js** - Risk scoring (Technique #6)
-4. **run-analysis.sh** - Master script chạy tất cả
+4. **run-analysis.sh** - Master script that runs all
 
 ## 🚀 Quick Start