claudecode-omc 5.5.2 → 5.6.1

package/bundled/upstream/ecc/commands/evolve.md

@@ -0,0 +1,178 @@
+---
+name: evolve
+description: Analyze instincts and suggest or generate evolved structures
+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 --generate         # Also generate files under evolved/{skills,commands,agents}
+```
+
+## 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. Detect current project context
+2. Read project + global instincts (project takes precedence on ID conflicts)
+3. Group instincts by trigger/domain patterns
+4. Identify:
+   - Skill candidates (trigger clusters with 2+ instincts)
+   - Command candidates (high-confidence workflow instincts)
+   - Agent candidates (larger, high-confidence clusters)
+5. Show promotion candidates (project -> global) when applicable
+6. If `--generate` is passed, write files to:
+   - Project scope: `~/.claude/homunculus/projects/<project-id>/evolved/`
+   - Global fallback: `~/.claude/homunculus/evolved/`
+
+## Output Format
+
+```
+============================================================
+  EVOLVE ANALYSIS - 12 instincts
+  Project: my-app (a1b2c3d4e5f6)
+  Project-scoped: 8 | Global: 4
+============================================================
+
+High confidence instincts (>=80%): 5
+
+## SKILL CANDIDATES
+1. Cluster: "adding tests"
+   Instincts: 3
+   Avg confidence: 82%
+   Domains: testing
+   Scopes: project
+
+## COMMAND CANDIDATES (2)
+  /adding-tests
+    From: test-first-workflow [project]
+    Confidence: 84%
+
+## AGENT CANDIDATES (1)
+  adding-tests-agent
+    Covers 3 instincts
+    Avg confidence: 82%
+```
+
+## Flags
+
+- `--generate`: Generate evolved files in addition to analysis output
+
+## 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/bundled/upstream/ecc/commands/feature-dev.md

@@ -0,0 +1,49 @@
+---
+description: Guided feature development with codebase understanding and architecture focus
+---
+
+A structured feature-development workflow that emphasizes understanding existing code before writing new code.
+
+## Phases
+
+### 1. Discovery
+
+- read the feature request carefully
+- identify requirements, constraints, and acceptance criteria
+- ask clarifying questions if the request is ambiguous
+
+### 2. Codebase Exploration
+
+- use `code-explorer` to analyze the relevant existing code
+- trace execution paths and architecture layers
+- understand integration points and conventions
+
+### 3. Clarifying Questions
+
+- present findings from exploration
+- ask targeted design and edge-case questions
+- wait for user response before proceeding
+
+### 4. Architecture Design
+
+- use `code-architect` to design the feature
+- provide the implementation blueprint
+- wait for approval before implementing
+
+### 5. Implementation
+
+- implement the feature following the approved design
+- prefer TDD where appropriate
+- keep commits small and focused
+
+### 6. Quality Review
+
+- use `code-reviewer` to review the implementation
+- address critical and important issues
+- verify test coverage
+
+### 7. Summary
+
+- summarize what was built
+- list follow-up items or limitations
+- provide testing instructions

package/bundled/upstream/ecc/commands/flutter-build.md

@@ -0,0 +1,164 @@
+---
+description: Fix Dart analyzer errors and Flutter build failures incrementally. Invokes the dart-build-resolver agent for minimal, surgical fixes.
+---
+
+# Flutter Build and Fix
+
+This command invokes the **dart-build-resolver** agent to incrementally fix Dart/Flutter build errors with minimal changes.
+
+## What This Command Does
+
+1. **Run Diagnostics**: Execute `flutter analyze`, `flutter pub get`
+2. **Parse Errors**: Group by file and sort by severity
+3. **Fix Incrementally**: One error at a time
+4. **Verify Each Fix**: Re-run analysis after each change
+5. **Report Summary**: Show what was fixed and what remains
+
+## When to Use
+
+Use `/flutter-build` when:
+- `flutter analyze` reports errors
+- `flutter build` fails for any platform
+- `dart pub get` / `flutter pub get` fails with version conflicts
+- `build_runner` fails to generate code
+- After pulling changes that break the build
+
+## Diagnostic Commands Run
+
+```bash
+# Analysis
+flutter analyze 2>&1
+
+# Dependencies
+flutter pub get 2>&1
+
+# Code generation (if project uses build_runner)
+dart run build_runner build --delete-conflicting-outputs 2>&1
+
+# Platform builds
+flutter build apk 2>&1
+flutter build web 2>&1
+```
+
+## Example Session
+
+````text
+User: /flutter-build
+
+Agent:
+# Flutter Build Resolution
+
+## Initial Diagnostics
+
+```
+$ flutter analyze
+Analyzing project...
+
+  error • lib/features/user/data/user_repository_impl.dart:34:16 •
+    A value of type 'String?' can't be assigned to a variable of type 'String'. •
+    invalid_assignment
+
+  error • lib/features/cart/presentation/cart_page.dart:58:5 •
+    The method 'add' isn't defined for the type 'List<Item>'.
+    Try correcting the name to the name of an existing method, or defining a method named 'add'. •
+    undefined_method
+
+2 errors found.
+```
+
+## Fix 1: Null Safety
+
+File: lib/features/user/data/user_repository_impl.dart:34
+Error: A value of type 'String?' can't be assigned to type 'String'
+
+Changed:
+```dart
+final id = response.id;
+```
+To:
+```dart
+final id = response.id ?? '';
+```
+
+```
+$ flutter analyze
+1 error found.
+```
+
+## Fix 2: Immutable List
+
+File: lib/features/cart/presentation/cart_page.dart:58
+Error: The method 'add' isn't defined for the type 'List<Item>'
+Cause: State holds an unmodifiable list; mutation goes through Cubit
+
+Changed:
+```dart
+state.items.add(item);
+```
+To:
+```dart
+context.read<CartCubit>().addItem(item);
+// Note: Cubit exposes named methods (addItem, removeItem);
+// .add(event) is the BLoC event API — don't mix them.
+```
+
+```
+$ flutter analyze
+No issues found!
+```
+
+## Final Verification
+
+```
+$ flutter test
+All tests passed.
+```
+
+## Summary
+
+| Metric | Count |
+|--------|-------|
+| Analysis errors fixed | 2 |
+| Files modified | 2 |
+| Remaining issues | 0 |
+
+Build Status: PASS ✓
+````
+
+## Common Errors Fixed
+
+| Error | Typical Fix |
+|-------|-------------|
+| `A value of type 'X?' can't be assigned to 'X'` | Add `?? default` or null guard |
+| `The name 'X' isn't defined` | Add import or fix typo |
+| `Non-nullable instance field must be initialized` | Add initializer or `late` |
+| `Version solving failed` | Adjust version constraints in pubspec.yaml |
+| `Missing concrete implementation of 'X'` | Implement missing interface method |
+| `build_runner: Part of X expected` | Delete stale `.g.dart` and rebuild |
+
+## Fix Strategy
+
+1. **Analysis errors first** — code must be error-free
+2. **Warning triage second** — fix warnings that could cause runtime bugs
+3. **pub conflicts third** — fix dependency resolution
+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
+- Package upgrade conflicts need user decision
+
+## Related Commands
+
+- `/flutter-test` — Run tests after build succeeds
+- `/flutter-review` — Review code quality
+- `/verify` — Full verification loop
+
+## Related
+
+- Agent: `agents/dart-build-resolver.md`
+- Skill: `skills/flutter-dart-code-review/`

package/bundled/upstream/ecc/commands/flutter-review.md

@@ -0,0 +1,116 @@
+---
+description: Review Flutter/Dart code for idiomatic patterns, widget best practices, state management, performance, accessibility, and security. Invokes the flutter-reviewer agent.
+---
+
+# Flutter Code Review
+
+This command invokes the **flutter-reviewer** agent to review Flutter/Dart code changes.
+
+## What This Command Does
+
+1. **Gather Context**: Review `git diff --staged` and `git diff`
+2. **Inspect Project**: Check `pubspec.yaml`, `analysis_options.yaml`, state management solution
+3. **Security Pre-scan**: Check for hardcoded secrets and critical security issues
+4. **Full Review**: Apply the complete review checklist
+5. **Report Findings**: Output issues grouped by severity with fix guidance
+
+## Prerequisites
+
+Before running `/flutter-review`, ensure:
+1. **Build passes** — run `/flutter-build` first; a review on broken code is incomplete
+2. **Tests pass** — run `/flutter-test` to confirm no regressions
+3. **No merge conflicts** — resolve all conflicts so the diff reflects only intentional changes
+4. **`flutter analyze` is clean** — fix analyzer warnings before review
+
+## When to Use
+
+Use `/flutter-review` when:
+- Before submitting a PR with Flutter/Dart changes (after build and tests pass)
+- After implementing a new feature to catch issues early
+- When reviewing someone else's Flutter code
+- To audit a widget, state management component, or service class
+- Before a production release
+
+## Review Areas
+
+| Area | Severity |
+|------|----------|
+| Hardcoded secrets, cleartext HTTP | CRITICAL |
+| Architecture violations, state management anti-patterns | CRITICAL |
+| Widget rebuild issues, resource leaks | HIGH |
+| Missing `dispose()`, `BuildContext` after await | HIGH |
+| Dart null safety, missing error/loading states | HIGH |
+| Const propagation, widget composition | HIGH |
+| Performance: expensive work in `build()` | HIGH |
+| Accessibility, semantic labels | MEDIUM |
+| Missing tests for state transitions | HIGH |
+| Hardcoded strings (l10n) | MEDIUM |
+| Pub dependency hygiene | LOW |
+
+## Example Session
+
+````text
+User: /flutter-review
+
+Agent:
+# Flutter Code Review
+
+## Context
+
+Changed files:
+- lib/features/auth/presentation/login_page.dart
+- lib/features/auth/data/auth_repository_impl.dart
+
+State management: Riverpod (detected from pubspec.yaml)
+Architecture: feature-first
+
+## Security Pre-scan
+
+✓ No hardcoded secrets detected
+✓ No cleartext HTTP calls
+
+## Review Findings
+
+[HIGH] BuildContext used after async gap without mounted check
+File: lib/features/auth/presentation/login_page.dart:67
+Issue: `context.go('/home')` called after `await auth.login(...)` with no `mounted` check.
+Fix: Add `if (!context.mounted) return;` before any navigation after awaits (Flutter 3.7+).
+
+[HIGH] AsyncValue error state not handled
+File: lib/features/auth/presentation/login_page.dart:42
+Issue: `ref.watch(authProvider)` switches on loading/data but has no `error` branch.
+Fix: Add error case to the switch expression or `when()` call to show a user-facing error message.
+
+[MEDIUM] Hardcoded string not localized
+File: lib/features/auth/presentation/login_page.dart:89
+Issue: `Text('Login')` — user-visible string not using localization system.
+Fix: Use the project's l10n accessor: `Text(context.l10n.loginButton)`.
+
+## Review Summary
+
+| Severity | Count | Status |
+|----------|-------|--------|
+| CRITICAL | 0     | pass   |
+| HIGH     | 2     | block  |
+| MEDIUM   | 1     | info   |
+| LOW      | 0     | note   |
+
+Verdict: BLOCK — HIGH issues must be fixed before merge.
+````
+
+## Approval Criteria
+
+- **Approve**: No CRITICAL or HIGH issues
+- **Block**: Any CRITICAL or HIGH issues must be fixed before merge
+
+## Related Commands
+
+- `/flutter-build` — Fix build errors first
+- `/flutter-test` — Run tests before reviewing
+- `/code-review` — General code review (language-agnostic)
+
+## Related
+
+- Agent: `agents/flutter-reviewer.md`
+- Skill: `skills/flutter-dart-code-review/`
+- Rules: `rules/dart/`

package/bundled/upstream/ecc/commands/flutter-test.md

@@ -0,0 +1,144 @@
+---
+description: Run Flutter/Dart tests, report failures, and incrementally fix test issues. Covers unit, widget, golden, and integration tests.
+---
+
+# Flutter Test
+
+This command runs the Flutter test suite and reports results. When failures occur, it diagnoses and fixes issues incrementally.
+
+## What This Command Does
+
+1. **Run Tests**: Execute `flutter test` (or scope to changed files)
+2. **Parse Failures**: Identify failing tests by type and cause
+3. **Fix Incrementally**: One failure at a time where possible
+4. **Verify**: Re-run after each fix
+5. **Report**: Show coverage summary and remaining failures
+
+## When to Use
+
+Use `/flutter-test` when:
+- After implementing a feature to verify nothing broke
+- After running `/flutter-build` to ensure tests pass
+- To check test coverage on new code
+- When a specific test file is failing
+- Before submitting a PR
+
+## Commands Run
+
+```bash
+# Run all tests
+flutter test 2>&1
+
+# Run with coverage
+flutter test --coverage 2>&1
+
+# Run specific test file
+flutter test test/unit/domain/usecases/get_user_test.dart 2>&1
+
+# Run tests matching a name pattern
+flutter test --name "CartBloc" 2>&1
+
+# Run integration tests (requires device/emulator)
+flutter test integration_test/ 2>&1
+
+# Update golden files when intentional visual changes are made
+flutter test --update-goldens 2>&1
+```
+
+## Example Session
+
+````text
+User: /flutter-test
+
+Agent:
+# Flutter Test Run
+
+## Test Execution
+
+```
+$ flutter test
+00:05 +42 -2: Some tests failed.
+
+FAILED: test/unit/data/user_repository_test.dart
+  UserRepository getById
+    returns null when user not found
+    Expected: null
+    Actual: User(id: 'test-id', name: 'Test User')
+
+FAILED: test/widget/cart_page_test.dart
+  CartPage
+    shows empty state when cart is empty
+    Expected: exactly one widget with text 'Your cart is empty'
+    Found: no widget with text 'Your cart is empty'
+```
+
+## Fix 1: Repository Test
+
+File: test/unit/data/user_repository_test.dart
+Failure: `getById` returns a user when it should return null for missing ID
+
+Root cause: Test setup adds a user with ID 'test-id' but queries with 'missing-id'.
+Fix: Updated test to query with 'missing-id' — setup was correct, query was wrong.
+
+```
+$ flutter test test/unit/data/user_repository_test.dart
+1 test passed.
+```
+
+## Fix 2: Widget Test
+
+File: test/widget/cart_page_test.dart
+Failure: Empty state text widget not found
+
+Root cause: Empty state message was renamed from 'Your cart is empty' to 'Cart is empty' in the widget.
+Fix: Updated test string to match current widget copy.
+
+```
+$ flutter test test/widget/cart_page_test.dart
+1 test passed.
+```
+
+## Final Run
+
+```
+$ flutter test --coverage
+All 44 tests passed.
+Coverage: 84.2% (target: 80%)
+```
+
+## Summary
+
+| Metric | Value |
+|--------|-------|
+| Total tests | 44 |
+| Passed | 44 |
+| Failed | 0 |
+| Coverage | 84.2% |
+
+Test Status: PASS ✓
+````
+
+## Common Test Failures
+
+| Failure | Typical Fix |
+|---------|-------------|
+| `Expected: <X> Actual: <Y>` | Update assertion or fix implementation |
+| `Widget not found` | Fix finder selector or update test after widget rename |
+| `Golden file not found` | Run `flutter test --update-goldens` to generate |
+| `Golden mismatch` | Inspect diff; run `--update-goldens` if change was intentional |
+| `MissingPluginException` | Mock platform channel in test setup |
+| `LateInitializationError` | Initialize `late` fields in `setUp()` |
+| `pumpAndSettle timed out` | Replace with explicit `pump(Duration)` calls |
+
+## Related Commands
+
+- `/flutter-build` — Fix build errors before running tests
+- `/flutter-review` — Review code after tests pass
+- `/tdd` — Test-driven development workflow
+
+## Related
+
+- Agent: `agents/flutter-reviewer.md`
+- Agent: `agents/dart-build-resolver.md`
+- Skill: `skills/flutter-dart-code-review/`
+- Rules: `rules/dart/testing.md`