npm - @cregis-dev/cckit - Versions diffs - 0.4.1 → 0.6.1 - Mend

@cregis-dev/cckit 0.4.1 → 0.6.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (795) hide show

package/templates/ecc/commands/eval.md DELETED Viewed

@@ -1,120 +0,0 @@
-# Eval Command
-Manage eval-driven development workflow.
-## Usage
-`/eval [define|check|report|list] [feature-name]`
-## Define Evals
-`/eval define feature-name`
-Create a new eval definition:
-1. Create `.claude/evals/feature-name.md` with template:
-```markdown
-## EVAL: feature-name
-Created: $(date)
-### Capability Evals
-- [ ] [Description of capability 1]
-- [ ] [Description of capability 2]
-### Regression Evals
-- [ ] [Existing behavior 1 still works]
-- [ ] [Existing behavior 2 still works]
-### Success Criteria
-- pass@3 > 90% for capability evals
-- pass^3 = 100% for regression evals
-```
-2. Prompt user to fill in specific criteria
-## Check Evals
-`/eval check feature-name`
-Run evals for a feature:
-1. Read eval definition from `.claude/evals/feature-name.md`
-2. For each capability eval:
-   - Attempt to verify criterion
-   - Record PASS/FAIL
-   - Log attempt in `.claude/evals/feature-name.log`
-3. For each regression eval:
-   - Run relevant tests
-   - Compare against baseline
-   - Record PASS/FAIL
-4. Report current status:
-```
-EVAL CHECK: feature-name
-========================
-Capability: X/Y passing
-Regression: X/Y passing
-Status: IN PROGRESS / READY
-```
-## Report Evals
-`/eval report feature-name`
-Generate comprehensive eval report:
-```
-EVAL REPORT: feature-name
-=========================
-Generated: $(date)
-CAPABILITY EVALS
-----------------
-[eval-1]: PASS (pass@1)
-[eval-2]: PASS (pass@2) - required retry
-[eval-3]: FAIL - see notes
-REGRESSION EVALS
-----------------
-[test-1]: PASS
-[test-2]: PASS
-[test-3]: PASS
-METRICS
--------
-Capability pass@1: 67%
-Capability pass@3: 100%
-Regression pass^3: 100%
-NOTES
------
-[Any issues, edge cases, or observations]
-RECOMMENDATION
---------------
-[SHIP / NEEDS WORK / BLOCKED]
-```
-## List Evals
-`/eval list`
-Show all eval definitions:
-```
-EVAL DEFINITIONS
-================
-feature-auth      [3/5 passing] IN PROGRESS
-feature-search    [5/5 passing] READY
-feature-export    [0/4 passing] NOT STARTED
-```
-## Arguments
-$ARGUMENTS:
-- `define <name>` - Create new eval definition
-- `check <name>` - Run and check evals
-- `report <name>` - Generate full report
-- `list` - Show all evals
-- `clean` - Remove old eval logs (keeps last 10 runs)

package/templates/ecc/commands/evolve.md DELETED Viewed

@@ -1,193 +0,0 @@
----
-name: evolve
-description: Cluster related instincts into skills, commands, or agents
-command: true
----
-# Evolve Command
-## Implementation
-Run the instinct CLI using the plugin root path:
-```bash
-python3 "${CLAUDE_PLUGIN_ROOT}/skills/continuous-learning-v2/scripts/instinct-cli.py" evolve [--generate]
-```
-Or if `CLAUDE_PLUGIN_ROOT` is not set (manual installation):
-```bash
-python3 ~/.claude/skills/continuous-learning-v2/scripts/instinct-cli.py evolve [--generate]
-```
-Analyzes instincts and clusters related ones into higher-level structures:
-- **Commands**: When instincts describe user-invoked actions
-- **Skills**: When instincts describe auto-triggered behaviors
-- **Agents**: When instincts describe complex, multi-step processes
-## Usage
-```
-/evolve                    # Analyze all instincts and suggest evolutions
-/evolve --domain testing   # Only evolve instincts in testing domain
-/evolve --dry-run          # Show what would be created without creating
-/evolve --threshold 5      # Require 5+ related instincts to cluster
-```
-## Evolution Rules
-### → Command (User-Invoked)
-When instincts describe actions a user would explicitly request:
-- Multiple instincts about "when user asks to..."
-- Instincts with triggers like "when creating a new X"
-- Instincts that follow a repeatable sequence
-Example:
-- `new-table-step1`: "when adding a database table, create migration"
-- `new-table-step2`: "when adding a database table, update schema"
-- `new-table-step3`: "when adding a database table, regenerate types"
-→ Creates: **new-table** command
-### → Skill (Auto-Triggered)
-When instincts describe behaviors that should happen automatically:
-- Pattern-matching triggers
-- Error handling responses
-- Code style enforcement
-Example:
-- `prefer-functional`: "when writing functions, prefer functional style"
-- `use-immutable`: "when modifying state, use immutable patterns"
-- `avoid-classes`: "when designing modules, avoid class-based design"
-→ Creates: `functional-patterns` skill
-### → Agent (Needs Depth/Isolation)
-When instincts describe complex, multi-step processes that benefit from isolation:
-- Debugging workflows
-- Refactoring sequences
-- Research tasks
-Example:
-- `debug-step1`: "when debugging, first check logs"
-- `debug-step2`: "when debugging, isolate the failing component"
-- `debug-step3`: "when debugging, create minimal reproduction"
-- `debug-step4`: "when debugging, verify fix with test"
-→ Creates: **debugger** agent
-## What to Do
-1. Read all instincts from `~/.claude/homunculus/instincts/`
-2. Group instincts by:
-   - Domain similarity
-   - Trigger pattern overlap
-   - Action sequence relationship
-3. For each cluster of 3+ related instincts:
-   - Determine evolution type (command/skill/agent)
-   - Generate the appropriate file
-   - Save to `~/.claude/homunculus/evolved/{commands,skills,agents}/`
-4. Link evolved structure back to source instincts
-## Output Format
-```
-🧬 Evolve Analysis
-==================
-Found 3 clusters ready for evolution:
-## Cluster 1: Database Migration Workflow
-Instincts: new-table-migration, update-schema, regenerate-types
-Type: Command
-Confidence: 85% (based on 12 observations)
-Would create: /new-table command
-Files:
-  - ~/.claude/homunculus/evolved/commands/new-table.md
-## Cluster 2: Functional Code Style
-Instincts: prefer-functional, use-immutable, avoid-classes, pure-functions
-Type: Skill
-Confidence: 78% (based on 8 observations)
-Would create: functional-patterns skill
-Files:
-  - ~/.claude/homunculus/evolved/skills/functional-patterns.md
-## Cluster 3: Debugging Process
-Instincts: debug-check-logs, debug-isolate, debug-reproduce, debug-verify
-Type: Agent
-Confidence: 72% (based on 6 observations)
-Would create: debugger agent
-Files:
-  - ~/.claude/homunculus/evolved/agents/debugger.md
----
-Run `/evolve --execute` to create these files.
-```
-## Flags
-- `--execute`: Actually create the evolved structures (default is preview)
-- `--dry-run`: Preview without creating
-- `--domain <name>`: Only evolve instincts in specified domain
-- `--threshold <n>`: Minimum instincts required to form cluster (default: 3)
-- `--type <command|skill|agent>`: Only create specified type
-## Generated File Format
-### Command
-```markdown
----
-name: new-table
-description: Create a new database table with migration, schema update, and type generation
-command: /new-table
-evolved_from:
-  - new-table-migration
-  - update-schema
-  - regenerate-types
----
-# New Table Command
-[Generated content based on clustered instincts]
-## Steps
-1. ...
-2. ...
-```
-### Skill
-```markdown
----
-name: functional-patterns
-description: Enforce functional programming patterns
-evolved_from:
-  - prefer-functional
-  - use-immutable
-  - avoid-classes
----
-# Functional Patterns Skill
-[Generated content based on clustered instincts]
-```
-### Agent
-```markdown
----
-name: debugger
-description: Systematic debugging agent
-model: sonnet
-evolved_from:
-  - debug-check-logs
-  - debug-isolate
-  - debug-reproduce
----
-# Debugger Agent
-[Generated content based on clustered instincts]
-```

package/templates/ecc/commands/go-build.md DELETED Viewed

@@ -1,183 +0,0 @@
----
-description: Fix Go build errors, go vet warnings, and linter issues incrementally. Invokes the go-build-resolver agent for minimal, surgical fixes.
----
-# Go Build and Fix
-This command invokes the **go-build-resolver** agent to incrementally fix Go build errors with minimal changes.
-## What This Command Does
-1. **Run Diagnostics**: Execute `go build`, `go vet`, `staticcheck`
-2. **Parse Errors**: Group by file and sort by severity
-3. **Fix Incrementally**: One error at a time
-4. **Verify Each Fix**: Re-run build after each change
-5. **Report Summary**: Show what was fixed and what remains
-## When to Use
-Use `/go-build` when:
-- `go build ./...` fails with errors
-- `go vet ./...` reports issues
-- `golangci-lint run` shows warnings
-- Module dependencies are broken
-- After pulling changes that break the build
-## Diagnostic Commands Run
-```bash
-# Primary build check
-go build ./...
-# Static analysis
-go vet ./...
-# Extended linting (if available)
-staticcheck ./...
-golangci-lint run
-# Module issues
-go mod verify
-go mod tidy -v
-```
-## Example Session
-```text
-User: /go-build
-Agent:
-# Go Build Resolution
-## Initial Diagnostics
-```bash
-$ go build ./...
-internal/service/user.go:25:15: undefined: UserRepository
-internal/handler/api.go:42:9: cannot use x (type string) as type int
-internal/handler/api.go:58:2: missing return at end of function
-```
-Errors found: 3
-## Fix 1: Undefined Identifier
-File: internal/service/user.go:25
-Error: undefined: UserRepository
-Cause: Missing import
-```go
-// Added import
-import "project/internal/repository"
-// Changed
-var repo UserRepository
-// To
-var repo repository.UserRepository
-```
-```bash
-$ go build ./...
-# 2 errors remaining
-```
-## Fix 2: Type Mismatch
-File: internal/handler/api.go:42
-Error: cannot use x (type string) as type int
-```go
-// Changed
-count := params.Get("count")
-// To
-countStr := params.Get("count")
-count, _ := strconv.Atoi(countStr)
-```
-```bash
-$ go build ./...
-# 1 error remaining
-```
-## Fix 3: Missing Return
-File: internal/handler/api.go:58
-Error: missing return at end of function
-```go
-func GetUser(id string) (*User, error) {
-    if id == "" {
-        return nil, ErrInvalidID
-    }
-    user := findUser(id)
-    // Added missing return
-    return user, nil
-}
-```
-```bash
-$ go build ./...
-# Build successful!
-```
-## Final Verification
-```bash
-$ go vet ./...
-# No issues
-$ go test ./...
-ok      project/internal/service   0.015s
-ok      project/internal/handler   0.023s
-```
-## Summary
-| Metric | Count |
-|--------|-------|
-| Build errors fixed | 3 |
-| Vet warnings fixed | 0 |
-| Files modified | 2 |
-| Remaining issues | 0 |
-Build Status: ✅ SUCCESS
-```
-## Common Errors Fixed
-| Error | Typical Fix |
-|-------|-------------|
-| `undefined: X` | Add import or fix typo |
-| `cannot use X as Y` | Type conversion or fix assignment |
-| `missing return` | Add return statement |
-| `X does not implement Y` | Add missing method |
-| `import cycle` | Restructure packages |
-| `declared but not used` | Remove or use variable |
-| `cannot find package` | `go get` or `go mod tidy` |
-## Fix Strategy
-1. **Build errors first** - Code must compile
-2. **Vet warnings second** - Fix suspicious constructs
-3. **Lint warnings third** - Style and best practices
-4. **One fix at a time** - Verify each change
-5. **Minimal changes** - Don't refactor, just fix
-## Stop Conditions
-The agent will stop and report if:
-- Same error persists after 3 attempts
-- Fix introduces more errors
-- Requires architectural changes
-- Missing external dependencies
-## Related Commands
-- `/go-test` - Run tests after build succeeds
-- `/go-review` - Review code quality
-- `/verify` - Full verification loop
-## Related
-- Agent: `agents/go-build-resolver.md`
-- Skill: `skills/golang-patterns/`

package/templates/ecc/commands/go-review.md DELETED Viewed

@@ -1,148 +0,0 @@
----
-description: Comprehensive Go code review for idiomatic patterns, concurrency safety, error handling, and security. Invokes the go-reviewer agent.
----
-# Go Code Review
-This command invokes the **go-reviewer** agent for comprehensive Go-specific code review.
-## What This Command Does
-1. **Identify Go Changes**: Find modified `.go` files via `git diff`
-2. **Run Static Analysis**: Execute `go vet`, `staticcheck`, and `golangci-lint`
-3. **Security Scan**: Check for SQL injection, command injection, race conditions
-4. **Concurrency Review**: Analyze goroutine safety, channel usage, mutex patterns
-5. **Idiomatic Go Check**: Verify code follows Go conventions and best practices
-6. **Generate Report**: Categorize issues by severity
-## When to Use
-Use `/go-review` when:
-- After writing or modifying Go code
-- Before committing Go changes
-- Reviewing pull requests with Go code
-- Onboarding to a new Go codebase
-- Learning idiomatic Go patterns
-## Review Categories
-### CRITICAL (Must Fix)
-- SQL/Command injection vulnerabilities
-- Race conditions without synchronization
-- Goroutine leaks
-- Hardcoded credentials
-- Unsafe pointer usage
-- Ignored errors in critical paths
-### HIGH (Should Fix)
-- Missing error wrapping with context
-- Panic instead of error returns
-- Context not propagated
-- Unbuffered channels causing deadlocks
-- Interface not satisfied errors
-- Missing mutex protection
-### MEDIUM (Consider)
-- Non-idiomatic code patterns
-- Missing godoc comments on exports
-- Inefficient string concatenation
-- Slice not preallocated
-- Table-driven tests not used
-## Automated Checks Run
-```bash
-# Static analysis
-go vet ./...
-# Advanced checks (if installed)
-staticcheck ./...
-golangci-lint run
-# Race detection
-go build -race ./...
-# Security vulnerabilities
-govulncheck ./...
-```
-## Example Usage
-```text
-User: /go-review
-Agent:
-# Go Code Review Report
-## Files Reviewed
-- internal/handler/user.go (modified)
-- internal/service/auth.go (modified)
-## Static Analysis Results
-✓ go vet: No issues
-✓ staticcheck: No issues
-## Issues Found
-[CRITICAL] Race Condition
-File: internal/service/auth.go:45
-Issue: Shared map accessed without synchronization
-```go
-var cache = map[string]*Session{}  // Concurrent access!
-func GetSession(id string) *Session {
-    return cache[id]  // Race condition
-}
-```
-Fix: Use sync.RWMutex or sync.Map
-```go
-var (
-    cache   = map[string]*Session{}
-    cacheMu sync.RWMutex
-)
-func GetSession(id string) *Session {
-    cacheMu.RLock()
-    defer cacheMu.RUnlock()
-    return cache[id]
-}
-```
-[HIGH] Missing Error Context
-File: internal/handler/user.go:28
-Issue: Error returned without context
-```go
-return err  // No context
-```
-Fix: Wrap with context
-```go
-return fmt.Errorf("get user %s: %w", userID, err)
-```
-## Summary
-- CRITICAL: 1
-- HIGH: 1
-- MEDIUM: 0
-Recommendation: ❌ Block merge until CRITICAL issue is fixed
-```
-## Approval Criteria
-| Status | Condition |
-|--------|-----------|
-| ✅ Approve | No CRITICAL or HIGH issues |
-| ⚠️ Warning | Only MEDIUM issues (merge with caution) |
-| ❌ Block | CRITICAL or HIGH issues found |
-## Integration with Other Commands
-- Use `/go-test` first to ensure tests pass
-- Use `/go-build` if build errors occur
-- Use `/go-review` before committing
-- Use `/code-review` for non-Go specific concerns
-## Related
-- Agent: `agents/go-reviewer.md`
-- Skills: `skills/golang-patterns/`, `skills/golang-testing/`