@haposoft/cafekit 0.13.4 → 0.14.1

package/src/claude/skills/impact-analysis/SKILL.md

@@ -1,276 +0,0 @@
----
-name: hapo:impact-analysis
-description: "Analyze code change impacts and generate test scenarios. Use after code changes, before commit, or when checking for regressions. Automatically detects affected files, dependencies, and edge cases."
-user-invocable: true
-when_to_use: "Invoke after code changes to map regression impact and test scenarios."
-category: dev-tools
-keywords: [impact, regression, dependencies, testing]
-argument-hint: "[files] OR auto"
-metadata:
-  author: haposoft
-  version: "1.0.0"
----
-# Impact Analysis - Impact Analysis & Test Guidance
-
-Analyze the impact of code changes and provide detailed test guidance to prevent regression bugs.
-
-## Arguments
-
-- **Default (no args)**: Analyze most recent git diff
-- **`auto`**: Automatically detect changes and analyze
-- **`{files}`**: Analyze specific files (comma-separated)
-
-## When to Use
-
-✅ **Should use:**
-- After code changes, before commit
-- Before creating Pull Request
-- After fixing bugs (ensure no new bugs introduced)
-- When refactoring code (verify functionality not broken)
-- When adding new features (find integration points)
-
-❌ **Not needed:**
-- Only documentation changes
-- Only comment changes
-- Config changes that don't affect logic
-
-## Quick Start
-
-```bash
-# Analyze most recent changes
-/impact-analysis
-
-# Auto-detect and analyze
-/impact-analysis auto
-
-# Analyze specific files
-/impact-analysis src/api/auth.ts,src/components/Login.tsx
-```
-
-## Workflow
-
-### 0. Auto-Detect Project Type (NEW)
-
-Load `references/project-detection.md` to:
-- Automatically detect project type (React Native, Next.js, Node.js API, etc.)
-- Load appropriate profile with patterns and edge cases
-- Check for custom config file (`impact-analysis.config.js`)
-- Merge custom config with default profile
-
-### 1. Detect Changes
-
-Load `references/change-detection.md` to:
-- Detect changed files (git diff)
-- Classify changes (backend/frontend/database)
-- Assess risk level
-
-### 2. Inspect Dependencies
-
-Load `references/dependency-scouting.md` to:
-- Find files that import/use modified code
-- Detect reverse dependencies
-- Identify integration points
-
-**Advanced**: Load `references/industry-techniques.md` to:
-- Use Call Graph Analysis (Technique #2)
-- Use Dependency Graph tools
-- Apply AST-based analysis (Technique #3) for semantic changes
-
-### 3. Identify Edge Cases
-
-Load `references/edge-case-identification.md` to:
-- Analyze data flow
-- Find boundary conditions
-- Identify error scenarios
-- Detect race conditions
-
-**Advanced**: Load `references/industry-techniques.md` to:
-- Use Static Analysis (Technique #4) for data/control flow
-- Use Type Analysis for type compatibility
-- Apply Test-Based Analysis (Technique #6) for coverage mapping
-
-### 4. Generate Test Scenarios
-
-Load `references/test-scenario-generation.md` to:
-- Create happy path scenarios
-- Create error handling scenarios
-- Create integration test scenarios
-- Create regression test checklist
-
-### 5. Create Report
-
-Load `references/report-template.md` to:
-- Consolidate findings
-- Assess risk
-- Provide recommendations
-- Create actionable checklist
-
-## Output
-
-```markdown
-# Impact Analysis Report
-
-## 📋 Summary
-- Changed: 3 files
-- Affected: 12 components
-- Risk: Medium
-- Test Time: ~30 mins
-
-## 🔍 Changes
-{detailed analysis}
-
-## 🔗 Dependencies
-{affected files}
-
-## ⚠️ Edge Cases
-{identified issues}
-
-## 🧪 Test Scenarios
-{detailed scenarios}
-
-## ✅ Checklist
-{actionable items}
-```
-
-## Integration
-
-### With Code Review
-
-```
-1. Make changes
-2. /impact-analysis
-3. Review findings
-4. /review (includes impact report)
-```
-
-### With Testing
-
-```
-1. /impact-analysis
-2. Get test scenarios
-3. /test (execute scenarios)
-4. Verify all pass
-```
-
-## References
-
-### Core References
-- `references/project-detection.md` - Auto-detect project type & load profile
-- `references/change-detection.md` - Git diff analysis
-- `references/dependency-scouting.md` - Finding affected files
-- `references/edge-case-identification.md` - Edge case patterns
-- `references/test-scenario-generation.md` - Test templates
-- `references/report-template.md` - Output format
-
-### Advanced References
-- `references/industry-techniques.md` - 9 techniques from industry & research
-- `references/practical-techniques-guide.md` - Detailed implementation guide
-- `references/react-native-customization.md` - React Native specific guide
-
-### Scripts
-- `scripts/README.md` - Helper scripts documentation
-- `scripts/ast-analyze.js` - AST-based analysis
-- `scripts/find-dependencies.sh` - Dependency analysis
-- `scripts/calculate-risk.js` - Risk scoring
-- `scripts/run-analysis.sh` - Master script
-
-## Advanced Techniques
-
-This skill supports advanced analysis techniques from industry:
-
-### Available Scripts
-
-Located in `scripts/` directory:
-
-1. **ast-analyze.js** - AST-based semantic analysis
-   - Detect function signature changes
-   - Identify breaking changes
-   - Compare before/after versions
-
-2. **find-dependencies.sh** - Comprehensive dependency analysis
-   - Find all affected files
-   - Map API consumers
-   - Identify integration points
-
-3. **calculate-risk.js** - Automated risk scoring
-   - Multi-factor risk assessment
-   - Actionable recommendations
-   - JSON output for CI/CD
-
-4. **run-analysis.sh** - Master script
-   - Run all techniques
-   - Generate comprehensive report
-   - Markdown output
-
-### Usage
-
-```bash
-# Quick risk check
-node scripts/calculate-risk.js
-
-# Full analysis
-./scripts/run-analysis.sh
-
-# Specific files
-./scripts/run-analysis.sh --files "file1.ts,file2.ts"
-```
-
-See `scripts/README.md` for detailed documentation.
-
-## Best Practices
-
-1. **Run early** - Analyze immediately after coding, don't wait until commit
-2. **Focus on risk** - Prioritize high-risk changes
-3. **Automate** - Integrate into automated workflow (pre-commit, CI/CD)
-4. **Document** - Save findings for future reference
-5. **Verify** - Always run tests after generating scenarios
-6. **Use scripts** - Leverage advanced techniques for deep analysis
-
-## Examples
-
-### Example 1: API Change
-
-```bash
-# Changed: src/api/users.ts (added new field)
-/impact-analysis
-
-# Output:
-# - Affected: 5 frontend components using user data
-# - Edge cases: Null handling, backward compatibility
-# - Test: Verify old clients still work
-```
-
-### Example 2: Database Migration
-
-```bash
-# Changed: prisma/schema.prisma (renamed column)
-/impact-analysis
-
-# Output:
-# - Affected: 15 queries using old column name
-# - Edge cases: Migration rollback, data integrity
-# - Test: Verify all queries updated
-```
-
-### Example 3: Component Refactor
-
-```bash
-# Changed: components/Button.tsx (props interface)
-/impact-analysis
-
-# Output:
-# - Affected: 23 components using Button
-# - Edge cases: TypeScript errors, missing props
-# - Test: Visual regression, interaction tests
-```
-
-## Troubleshooting
-
-**Q: Cannot detect changes?**
-A: Check git status, ensure there are staged/committed changes
-
-**Q: Too many affected files?**
-A: Use `--scope` to limit scope
-
-**Q: Test scenarios not sufficient?**
-A: Load `edge-case-identification.md` and review manually

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

@@ -1,270 +0,0 @@
-# Change Detection - Detecting Changes
-
-Methods for detecting and classifying code changes for impact analysis.
-
-## Git Commands
-
-### 1. Detect Recent Changes
-
-```bash
-# Uncommitted changes
-git diff --name-only
-
-# Staged changes
-git diff --cached --name-only
-
-# Changes in last commit
-git diff --name-only HEAD~1
-
-# Changes compared to another branch
-git diff --name-only main...HEAD
-
-# View detailed changes
-git diff HEAD~1
-
-# View statistics
-git diff --stat HEAD~1
-```
-
-### 2. Get Change Details
-
-```bash
-# Lines changed
-git diff --numstat HEAD~1
-
-# Files and change count
-git diff --shortstat HEAD~1
-
-# Only view added/deleted files
-git diff --diff-filter=AD --name-only HEAD~1
-```
-
-### 3. Historical Analysis
-
-```bash
-# View file history
-git log --oneline -10 {file}
-
-# See who modified which line
-git blame {file}
-
-# View changes in specific commit
-git show {commit-hash}
-```
-
-## Change Classification
-
-### Backend Changes
-
-**Indicators:**
-- Files: `*.ts`, `*.js`, `*.py`, `*.go` in `src/api/`, `src/services/`, `src/controllers/`
-- Patterns: API routes, database queries, business logic
-
-**Risk Level:**
-- **High**: Authentication, authorization, payment, data validation
-- **Medium**: CRUD operations, utility functions
-- **Low**: Logging, comments, formatting
-
-**Check:**
-```bash
-# API endpoints changed
-grep -r "router\." {changed-files}
-grep -r "app\.(get|post|put|delete)" {changed-files}
-
-# Database queries
-grep -r "prisma\." {changed-files}
-grep -r "SELECT\|INSERT\|UPDATE\|DELETE" {changed-files}
-```
-
-### Frontend Changes
-
-**Indicators:**
-- Files: `*.tsx`, `*.jsx`, `*.vue`, `*.svelte` in `src/components/`, `src/pages/`
-- Patterns: Components, hooks, state management
-
-**Risk Level:**
-- **High**: Authentication UI, payment forms, data entry
-- **Medium**: Display components, navigation
-- **Low**: Styling, text changes
-
-**Check:**
-```bash
-# Component props changed
-grep -r "interface.*Props" {changed-files}
-
-# State management
-grep -r "useState\|useEffect\|useContext" {changed-files}
-
-# API calls
-grep -r "fetch\|axios\|api\." {changed-files}
-```
-
-### Database Changes
-
-**Indicators:**
-- Files: `*.prisma`, `*.sql`, `migrations/*.sql`
-- Patterns: Schema changes, migrations
-
-**Risk Level:**
-- **Critical**: Column deletion, type changes, constraint changes
-- **High**: New required columns, index changes
-- **Medium**: New optional columns, new tables
-- **Low**: Comments, formatting
-
-**Check:**
-```bash
-# Schema changes
-git diff schema.prisma
-
-# Migration files
-ls -la migrations/ | tail -5
-
-# Find affected queries
-grep -r "{table_name}" src/
-```
-
-### Configuration Changes
-
-**Indicators:**
-- Files: `.env`, `config/*.ts`, `package.json`, `tsconfig.json`
-- Patterns: Environment variables, dependencies, build config
-
-**Risk Level:**
-- **Critical**: Database URL, API keys, auth secrets
-- **High**: Dependencies version, build settings
-- **Medium**: Feature flags, timeouts
-- **Low**: Comments, formatting
-
-**Check:**
-```bash
-# Env changes
-git diff .env.example
-
-# Dependency changes
-git diff package.json | grep -A5 -B5 "dependencies"
-
-# Config changes
-git diff config/
-```
-
-## Change Metrics
-
-### Lines of Code (LOC)
-
-```bash
-# Total LOC changed
-git diff --stat HEAD~1 | tail -1
-
-# Per file
-git diff --numstat HEAD~1
-```
-
-**Risk Assessment:**
-- **< 50 LOC**: Low risk
-- **50-200 LOC**: Medium risk
-- **> 200 LOC**: High risk (consider splitting)
-
-### File Count
-
-```bash
-# Count changed files
-git diff --name-only HEAD~1 | wc -l
-```
-
-**Risk Assessment:**
-- **1-3 files**: Low risk
-- **4-10 files**: Medium risk
-- **> 10 files**: High risk (wide impact)
-
-### Change Type
-
-```bash
-# Added lines
-git diff HEAD~1 | grep "^+" | wc -l
-
-# Deleted lines
-git diff HEAD~1 | grep "^-" | wc -l
-```
-
-**Risk Assessment:**
-- **More additions**: New feature (test new paths)
-- **More deletions**: Refactor (test existing paths)
-- **Balanced**: Modification (test both)
-
-## Automated Detection Script
-
-```bash
-#!/bin/bash
-# detect-changes.sh
-
-echo "=== Change Detection ==="
-
-# Get changed files
-CHANGED_FILES=$(git diff --name-only HEAD~1)
-FILE_COUNT=$(echo "$CHANGED_FILES" | wc -l)
-
-echo "Files changed: $FILE_COUNT"
-echo ""
-
-# Classify by type
-BACKEND=$(echo "$CHANGED_FILES" | grep -E "src/(api|services|controllers)" | wc -l)
-FRONTEND=$(echo "$CHANGED_FILES" | grep -E "src/(components|pages)" | wc -l)
-DATABASE=$(echo "$CHANGED_FILES" | grep -E "prisma|migrations" | wc -l)
-CONFIG=$(echo "$CHANGED_FILES" | grep -E "\.env|config|package\.json" | wc -l)
-
-echo "Backend: $BACKEND files"
-echo "Frontend: $FRONTEND files"
-echo "Database: $DATABASE files"
-echo "Config: $CONFIG files"
-echo ""
-
-# Get LOC stats
-git diff --stat HEAD~1 | tail -1
-
-# Risk assessment
-if [ $FILE_COUNT -gt 10 ] || [ $DATABASE -gt 0 ]; then
-    echo "Risk: HIGH"
-elif [ $FILE_COUNT -gt 3 ]; then
-    echo "Risk: MEDIUM"
-else
-    echo "Risk: LOW"
-fi
-```
-
-## Output Format
-
-```json
-{
-  "summary": {
-    "totalFiles": 5,
-    "linesAdded": 120,
-    "linesDeleted": 45,
-    "riskLevel": "medium"
-  },
-  "changes": [
-    {
-      "file": "src/api/auth.ts",
-      "type": "backend",
-      "category": "authentication",
-      "linesChanged": 67,
-      "risk": "high",
-      "reason": "Authentication logic modified"
-    },
-    {
-      "file": "src/components/Login.tsx",
-      "type": "frontend",
-      "category": "ui",
-      "linesChanged": 34,
-      "risk": "medium",
-      "reason": "Login form updated"
-    }
-  ]
-}
-```
-
-## Integration Points
-
-After detection, pass to:
-1. **Dependency Scouting** - Find affected files
-2. **Edge Case Identification** - Analyze risks
-3. **Test Scenario Generation** - Create tests