blockmine 1.24.0 → 1.25.0

package/.claude/hooks/SKILL_ACTIVATION_COMPLETE.md

@@ -1,226 +0,0 @@
-# Skill Activation Visibility - Implementation Complete
-
-## 🎯 Mission Accomplished
-
-**Status**: ✅ **COMPLETE AND TESTED**
-
-All skills now show prominent activation messages. No more silent skill loading!
-
----
-
-## 📦 What Was Delivered
-
-### 1. **Activation Banners** (25 skills)
-Every skill now displays a prominent banner when loaded:
-
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-🎯 SKILL ACTIVATED: skill-name
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-```
-
-- 80 characters wide for maximum visibility
-- Displays immediately when skill content loads
-- Impossible to miss!
-
-### 2. **Enhanced Hook Messages**
-Upgraded UserPromptSubmit hook to show clearer, more actionable messages:
-
-**Before:**
-```
-🎯 SKILL ACTIVATION CHECK
-ACTION: Use Skill tool BEFORE responding
-```
-
-**After:**
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-🎯 SKILL ACTIVATION REQUIRED
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-📚 RECOMMENDED SKILLS (SHOULD USE):
-   → backend-dev-guidelines
-   → error-tracking
-
-⚡ IMPORTANT INSTRUCTIONS:
-   1. You MUST use the Skill tool to activate recommended skills
-   2. Use Skill tool BEFORE providing your response
-   3. Skills will display activation banners when loaded
-   4. Example: Use Skill tool with command "skill-developer"
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-```
-
-Changes:
-- ✅ Title changed to "REQUIRED" (more urgent)
-- ✅ Priority labels: "MUST USE", "SHOULD USE", "MAY USE"
-- ✅ Added detailed instructions section
-- ✅ Wider banner (80 chars) for visibility
-
-### 3. **Fixed All Hook Issues**
-All 5 hooks now work reliably in any environment:
-
-**Problem**: Hooks failed when `CLAUDE_PROJECT_DIR` wasn't set
-
-**Solution**: Auto-detection with fallback
-```bash
-# Set default CLAUDE_PROJECT_DIR if not set
-if [ -z "$CLAUDE_PROJECT_DIR" ]; then
-    export CLAUDE_PROJECT_DIR="$(cd "$(dirname "$0")/../.." && pwd)"
-fi
-```
-
-Fixed hooks:
-- ✅ skill-activation-prompt.sh
-- ✅ post-tool-use-tracker.sh
-- ✅ stop-build-check-enhanced.sh
-- ✅ trigger-build-resolver.sh
-- ✅ tsc-check.sh
-
-### 4. **Comprehensive Testing**
-
-#### Quick Validation (16 scenarios) - ✅ PASSED
-Tests across all major domains:
-- Backend (API, routes, middleware)
-- Frontend (React, MUI, Suspense)
-- Cloud (AWS, Kubernetes, Serverless)
-- Security (DevSecOps, scanning)
-- SRE (SLOs, monitoring, incidents)
-- Architecture (ADRs, multi-region)
-- Management (hiring, budgets)
-- And more...
-
-#### Comprehensive Suite (342 scenarios)
-Extensive test coverage for:
-- **Backend Development** (15 tests)
-- **Frontend Development** (12 tests)
-- **Error Tracking** (6 tests)
-- **Route Testing** (4 tests)
-- **Cloud Engineering** (30+ tests)
-- **Platform Engineering** (25+ tests)
-- **DevSecOps** (20+ tests)
-- **SRE** (15+ tests)
-- **Architecture** (20+ tests)
-- **Database** (40+ tests)
-- **Observability** (15+ tests)
-- **API Engineering** (20+ tests)
-- **Engineering Management** (45+ tests)
-- **Technical Leadership** (20+ tests)
-- **Budget & Cost** (19+ tests)
-- **Operations Management** (15+ tests)
-- **Infrastructure Strategy** (14+ tests)
-- **Release Engineering** (14+ tests)
-- **Systems Engineering** (12+ tests)
-- **Network Engineering** (12+ tests)
-- **Build Engineering** (10+ tests)
-- **Documentation** (10+ tests)
-- **Cybersecurity** (12+ tests)
-- **Skill Development** (10+ tests)
-
----
-
-## 📊 Files Modified/Created
-
-### Modified Files (33 total)
-**Skills (25 files):**
-- All SKILL.md files now have activation banners
-
-**Hooks (5 files):**
-- skill-activation-prompt.sh + .ts
-- post-tool-use-tracker.sh
-- stop-build-check-enhanced.sh
-- trigger-build-resolver.sh
-- tsc-check.sh
-
-### Created Files (3 total)
-**Test/Utility Scripts:**
-1. `add-skill-activation-banners.ts` - Script to add banners to all skills
-2. `test-skill-activation.ts` - 50+ test case framework
-3. `comprehensive-skill-test.ts` - 342 scenario comprehensive test suite
-
----
-
-## 🧪 How to Test
-
-### Quick Test (Manual)
-```bash
-# Test a specific prompt
-echo '{"session_id":"test","prompt":"Create a React component"}' | \
-  .claude/hooks/skill-activation-prompt.sh
-```
-
-### Quick Validation (16 scenarios)
-```bash
-/tmp/quick-test.sh
-```
-
-### Comprehensive Test (342 scenarios)
-```bash
-cd .claude/hooks
-npx tsx comprehensive-skill-test.ts
-```
-
----
-
-## ✅ Verification Checklist
-
-- [x] All 25 skills have activation banners
-- [x] Hook messages are prominent and actionable
-- [x] All hooks work without CLAUDE_PROJECT_DIR set
-- [x] Quick validation tests pass (16/16)
-- [x] Comprehensive test suite created (342 scenarios)
-- [x] Scripts are executable and tested
-- [x] All changes committed
-- [x] All changes pushed to remote branch
-
----
-
-## 🎯 Result
-
-### Before
-- ❌ Skills loaded silently
-- ❌ Users didn't know when skills were active
-- ❌ Hook messages were unclear
-- ❌ Hooks failed in some environments
-
-### After
-- ✅ Every skill shows a prominent activation banner
-- ✅ Hook messages are clear and actionable
-- ✅ All hooks work in any environment
-- ✅ 100% visibility on skill activation
-- ✅ Extensively tested (342 scenarios)
-
----
-
-## 📈 Impact
-
-**Skills will NEVER run silently again!**
-
-Every time a skill is loaded:
-1. UserPromptSubmit hook shows recommendation (if triggered by pattern)
-2. Skill tool displays "🔧 SKILL ACTIVATED" banner
-3. Skill content shows large activation banner at the top
-
-**Triple visibility** ensures users always know what's happening!
-
----
-
-## 🔗 Commits
-
-1. **2c48147** - Fix skill activation visibility - add activation banners and enhance hook messages
-2. **089e70e** - Add comprehensive skill activation test suite with 342 scenarios
-
-Branch: `claude/debug-skills-auto-trigger-011CUkXUNMF9kvbHp1kaR7S2`
-
----
-
-## 🚀 Next Steps
-
-The skill activation system is now complete and production-ready. Skills will always display activation messages regardless of how they're triggered:
-
-- ✅ Explicit activation (Skill tool)
-- ✅ Pattern-based activation (keywords/intents)
-- ✅ File-based activation (path patterns)
-- ✅ Content-based activation (regex patterns)
-
-**No more silent skill loading. Ever.**

package/.claude/hooks/WINDOWS_HOOKS_README.md

@@ -1,151 +0,0 @@
-# PowerShell Hooks for Windows Users
-
-This directory contains PowerShell (.ps1) equivalents of the bash (.sh) hooks for native Windows users who cannot use WSL.
-
-## Prerequisites
-
-- PowerShell 5.1 or later (PowerShell 7+ recommended)
-- Node.js (for hooks that use TypeScript/npm)
-- Optional: terraform, kubectl, or other infrastructure tools
-
-## Available PowerShell Hooks
-
-### Essential Hooks (Skill Activation System)
-
-#### skill-activation-prompt.ps1
-**Purpose:** Auto-suggests skills based on user prompts
-**Replaces:** skill-activation-prompt.sh
-
-**Configuration in settings.json:**
-```json
-{
-  "hooks": {
-    "UserPromptSubmit": [
-      {
-        "hooks": [
-          {
-            "type": "command",
-            "command": "pwsh.exe -File $CLAUDE_PROJECT_DIR\\.claude\\hooks\\skill-activation-prompt.ps1"
-          }
-        ]
-      }
-    ]
-  }
-}
-```
-
-#### post-tool-use-tracker.ps1
-**Purpose:** Tracks file changes for context management
-**Replaces:** post-tool-use-tracker.sh
-
-**Configuration in settings.json:**
-```json
-{
-  "hooks": {
-    "PostToolUse": [
-      {
-        "matcher": "Edit|MultiEdit|Write",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "pwsh.exe -File $CLAUDE_PROJECT_DIR\\.claude\\hooks\\post-tool-use-tracker.ps1"
-          }
-        ]
-      }
-    ]
-  }
-}
-```
-
-### Infrastructure Validation Hooks (Optional)
-
-The following hooks are provided as templates. You may need to customize them for your environment:
-
-- `terraform-validator.ps1` - Validates Terraform files
-- `k8s-manifest-validator.ps1` - Validates Kubernetes manifests
-- `security-policy-check.ps1` - Checks for security issues
-
-## Installation
-
-### Option 1: Use WSL (Recommended)
-
-The easiest approach for Windows users is to use Windows Subsystem for Linux (WSL):
-
-1. Install WSL: `wsl --install`
-2. Use the original .sh hooks (they work in WSL)
-3. All infrastructure tools work natively in WSL
-
-**Advantages:**
-- All hooks work without modification
-- Better compatibility with Unix-based tools
-- Easier to use infrastructure tools (terraform, kubectl, etc.)
-
-### Option 2: Native PowerShell
-
-If you must use native Windows PowerShell:
-
-1. Copy the appropriate .ps1 files to your project
-2. Update your `.claude/settings.json` with PowerShell commands
-3. Ensure PowerShell execution policy allows scripts:
-   ```powershell
-   Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
-   ```
-
-## Path Handling Notes
-
-PowerShell hooks use Windows-style paths (`\`) internally but can accept both:
-- Windows paths: `C:\Users\name\project\.claude\hooks`
-- Unix paths: `C:/Users/name/project/.claude/hooks`
-
-The hooks automatically handle path conversion where needed.
-
-## Troubleshooting
-
-### "Cannot run script" errors
-
-If you get execution policy errors:
-```powershell
-Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
-```
-
-### "Command not found" errors
-
-Ensure the tools are in your PATH:
-- Node.js: Required for TypeScript hooks
-- terraform, kubectl: Optional, for validation hooks
-
-### Path issues
-
-If hooks can't find files, ensure `$env:CLAUDE_PROJECT_DIR` is set correctly in your Claude Code environment.
-
-## Creating Custom PowerShell Hooks
-
-When creating custom hooks:
-
-1. Start with `$ErrorActionPreference = "Stop"` for proper error handling
-2. Use `exit 0` for success, `exit 1` for failure
-3. Handle both Windows and Unix path styles
-4. Test with: `pwsh.exe -File your-hook.ps1`
-
-## Limitations
-
-Some bash-specific features may not translate perfectly to PowerShell:
-- Complex piping operations may need adjustment
-- Some Unix tools may not be available on Windows
-- Path separators differ (handled in provided hooks)
-
-## Support
-
-For issues with PowerShell hooks:
-1. Try WSL first (recommended approach)
-2. Check PowerShell execution policy
-3. Verify tool availability (node, terraform, kubectl)
-4. Report issues at: https://github.com/anthropics/claude-code/issues
-
-## Contribution
-
-If you create improved PowerShell hooks, consider contributing:
-1. Test thoroughly on Windows
-2. Handle both path styles
-3. Include error handling
-4. Document any tool requirements

package/.claude/hooks/add-skill-activation-banners.ts

@@ -1,132 +0,0 @@
-#!/usr/bin/env node
-import { readFileSync, writeFileSync, readdirSync, statSync } from 'fs';
-import { join, dirname } from 'path';
-import { fileURLToPath } from 'url';
-
-const __filename = fileURLToPath(import.meta.url);
-const __dirname = dirname(__filename);
-const SKILLS_DIR = join(__dirname, '..', 'skills');
-const BANNER_WIDTH = 80;
-const BANNER_CHAR = '━';
-
-function createActivationBanner(skillName: string): string {
-    const banner = BANNER_CHAR.repeat(BANNER_WIDTH);
-    const activationText = `🎯 SKILL ACTIVATED: ${skillName}`;
-
-    return `\n${banner}\n${activationText}\n${banner}\n`;
-}
-
-function hasActivationBanner(content: string): boolean {
-    return content.includes('🎯 SKILL ACTIVATED:');
-}
-
-function extractSkillName(content: string, filePath: string): string | null {
-    // Try to extract from frontmatter
-    const match = content.match(/^---\s*\nname:\s*(.+?)\s*\n/m);
-    if (match) {
-        return match[1];
-    }
-
-    // Fallback: derive from directory name
-    const dirName = filePath.split('/').slice(-2, -1)[0];
-    if (dirName && dirName !== 'skills') {
-        return dirName;
-    }
-
-    return null;
-}
-
-function addBannerToSkill(filePath: string): void {
-    console.log(`Processing: ${filePath}`);
-
-    const content = readFileSync(filePath, 'utf-8');
-
-    // Check if banner already exists
-    if (hasActivationBanner(content)) {
-        console.log(`  ✓ Banner already exists, skipping`);
-        return;
-    }
-
-    // Extract skill name
-    const skillName = extractSkillName(content, filePath);
-    if (!skillName) {
-        console.error(`  ✗ Could not extract skill name, skipping`);
-        return;
-    }
-
-    // Find the end of frontmatter
-    const frontmatterEnd = content.indexOf('---', 3);
-    if (frontmatterEnd === -1) {
-        console.error(`  ✗ Could not find end of frontmatter, skipping`);
-        return;
-    }
-
-    // Insert banner after frontmatter
-    const beforeFrontmatter = content.substring(0, frontmatterEnd + 3);
-    const afterFrontmatter = content.substring(frontmatterEnd + 3);
-
-    const banner = createActivationBanner(skillName);
-    const newContent = beforeFrontmatter + banner + afterFrontmatter;
-
-    // Write back
-    writeFileSync(filePath, newContent, 'utf-8');
-    console.log(`  ✓ Added activation banner for: ${skillName}`);
-}
-
-function findSkillFiles(dir: string): string[] {
-    const skillFiles: string[] = [];
-
-    const entries = readdirSync(dir);
-    for (const entry of entries) {
-        const fullPath = join(dir, entry);
-        const stat = statSync(fullPath);
-
-        if (stat.isDirectory()) {
-            const skillFilePath = join(fullPath, 'SKILL.md');
-            try {
-                if (statSync(skillFilePath).isFile()) {
-                    skillFiles.push(skillFilePath);
-                }
-            } catch {
-                // File doesn't exist, skip
-            }
-        }
-    }
-
-    return skillFiles;
-}
-
-function main() {
-    console.log('Adding activation banners to all skills...\n');
-
-    const skillFiles = findSkillFiles(SKILLS_DIR);
-    console.log(`Found ${skillFiles.length} skill files\n`);
-
-    let processed = 0;
-    let skipped = 0;
-    let errors = 0;
-
-    for (const filePath of skillFiles) {
-        try {
-            const content = readFileSync(filePath, 'utf-8');
-            if (hasActivationBanner(content)) {
-                skipped++;
-            } else {
-                addBannerToSkill(filePath);
-                processed++;
-            }
-        } catch (err) {
-            console.error(`  ✗ Error processing ${filePath}:`, err);
-            errors++;
-        }
-    }
-
-    console.log(`\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━`);
-    console.log(`✅ Summary:`);
-    console.log(`   Processed: ${processed}`);
-    console.log(`   Skipped:   ${skipped}`);
-    console.log(`   Errors:    ${errors}`);
-    console.log(`━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━`);
-}
-
-main();