@ngxtm/devkit 3.6.1 → 3.8.0

package/merged-commands/tdd-workflows-tdd-cycle.md

@@ -0,0 +1,221 @@
+---
+name: tdd-workflows-tdd-cycle
+description: "Use when working with tdd workflows tdd cycle"
+---
+
+## Use this skill when
+
+- Working on tdd workflows tdd cycle tasks or workflows
+- Needing guidance, best practices, or checklists for tdd workflows tdd cycle
+
+## Do not use this skill when
+
+- The task is unrelated to tdd workflows tdd cycle
+- You need a different domain or tool outside this scope
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+Execute a comprehensive Test-Driven Development (TDD) workflow with strict red-green-refactor discipline:
+
+[Extended thinking: This workflow enforces test-first development through coordinated agent orchestration. Each phase of the TDD cycle is strictly enforced with fail-first verification, incremental implementation, and continuous refactoring. The workflow supports both single test and test suite approaches with configurable coverage thresholds.]
+
+## Configuration
+
+### Coverage Thresholds
+- Minimum line coverage: 80%
+- Minimum branch coverage: 75%
+- Critical path coverage: 100%
+
+### Refactoring Triggers
+- Cyclomatic complexity > 10
+- Method length > 20 lines
+- Class length > 200 lines
+- Duplicate code blocks > 3 lines
+
+## Phase 1: Test Specification and Design
+
+### 1. Requirements Analysis
+- Use Task tool with subagent_type="comprehensive-review::architect-review"
+- Prompt: "Analyze requirements for: $ARGUMENTS. Define acceptance criteria, identify edge cases, and create test scenarios. Output a comprehensive test specification."
+- Output: Test specification, acceptance criteria, edge case matrix
+- Validation: Ensure all requirements have corresponding test scenarios
+
+### 2. Test Architecture Design
+- Use Task tool with subagent_type="unit-testing::test-automator"
+- Prompt: "Design test architecture for: $ARGUMENTS based on test specification. Define test structure, fixtures, mocks, and test data strategy. Ensure testability and maintainability."
+- Output: Test architecture, fixture design, mock strategy
+- Validation: Architecture supports isolated, fast, reliable tests
+
+## Phase 2: RED - Write Failing Tests
+
+### 3. Write Unit Tests (Failing)
+- Use Task tool with subagent_type="unit-testing::test-automator"
+- Prompt: "Write FAILING unit tests for: $ARGUMENTS. Tests must fail initially. Include edge cases, error scenarios, and happy paths. DO NOT implement production code."
+- Output: Failing unit tests, test documentation
+- **CRITICAL**: Verify all tests fail with expected error messages
+
+### 4. Verify Test Failure
+- Use Task tool with subagent_type="tdd-workflows::code-reviewer"
+- Prompt: "Verify that all tests for: $ARGUMENTS are failing correctly. Ensure failures are for the right reasons (missing implementation, not test errors). Confirm no false positives."
+- Output: Test failure verification report
+- **GATE**: Do not proceed until all tests fail appropriately
+
+## Phase 3: GREEN - Make Tests Pass
+
+### 5. Minimal Implementation
+- Use Task tool with subagent_type="backend-development::backend-architect"
+- Prompt: "Implement MINIMAL code to make tests pass for: $ARGUMENTS. Focus only on making tests green. Do not add extra features or optimizations. Keep it simple."
+- Output: Minimal working implementation
+- Constraint: No code beyond what's needed to pass tests
+
+### 6. Verify Test Success
+- Use Task tool with subagent_type="unit-testing::test-automator"
+- Prompt: "Run all tests for: $ARGUMENTS and verify they pass. Check test coverage metrics. Ensure no tests were accidentally broken."
+- Output: Test execution report, coverage metrics
+- **GATE**: All tests must pass before proceeding
+
+## Phase 4: REFACTOR - Improve Code Quality
+
+### 7. Code Refactoring
+- Use Task tool with subagent_type="tdd-workflows::code-reviewer"
+- Prompt: "Refactor implementation for: $ARGUMENTS while keeping tests green. Apply SOLID principles, remove duplication, improve naming, and optimize performance. Run tests after each refactoring."
+- Output: Refactored code, refactoring report
+- Constraint: Tests must remain green throughout
+
+### 8. Test Refactoring
+- Use Task tool with subagent_type="unit-testing::test-automator"
+- Prompt: "Refactor tests for: $ARGUMENTS. Remove test duplication, improve test names, extract common fixtures, and enhance test readability. Ensure tests still provide same coverage."
+- Output: Refactored tests, improved test structure
+- Validation: Coverage metrics unchanged or improved
+
+## Phase 5: Integration and System Tests
+
+### 9. Write Integration Tests (Failing First)
+- Use Task tool with subagent_type="unit-testing::test-automator"
+- Prompt: "Write FAILING integration tests for: $ARGUMENTS. Test component interactions, API contracts, and data flow. Tests must fail initially."
+- Output: Failing integration tests
+- Validation: Tests fail due to missing integration logic
+
+### 10. Implement Integration
+- Use Task tool with subagent_type="backend-development::backend-architect"
+- Prompt: "Implement integration code for: $ARGUMENTS to make integration tests pass. Focus on component interaction and data flow."
+- Output: Integration implementation
+- Validation: All integration tests pass
+
+## Phase 6: Continuous Improvement Cycle
+
+### 11. Performance and Edge Case Tests
+- Use Task tool with subagent_type="unit-testing::test-automator"
+- Prompt: "Add performance tests and additional edge case tests for: $ARGUMENTS. Include stress tests, boundary tests, and error recovery tests."
+- Output: Extended test suite
+- Metric: Increased test coverage and scenario coverage
+
+### 12. Final Code Review
+- Use Task tool with subagent_type="comprehensive-review::architect-review"
+- Prompt: "Perform comprehensive review of: $ARGUMENTS. Verify TDD process was followed, check code quality, test quality, and coverage. Suggest improvements."
+- Output: Review report, improvement suggestions
+- Action: Implement critical suggestions while maintaining green tests
+
+## Incremental Development Mode
+
+For test-by-test development:
+1. Write ONE failing test
+2. Make ONLY that test pass
+3. Refactor if needed
+4. Repeat for next test
+
+Use this approach by adding `--incremental` flag to focus on one test at a time.
+
+## Test Suite Mode
+
+For comprehensive test suite development:
+1. Write ALL tests for a feature/module (failing)
+2. Implement code to pass ALL tests
+3. Refactor entire module
+4. Add integration tests
+
+Use this approach by adding `--suite` flag for batch test development.
+
+## Validation Checkpoints
+
+### RED Phase Validation
+- [ ] All tests written before implementation
+- [ ] All tests fail with meaningful error messages
+- [ ] Test failures are due to missing implementation
+- [ ] No test passes accidentally
+
+### GREEN Phase Validation
+- [ ] All tests pass
+- [ ] No extra code beyond test requirements
+- [ ] Coverage meets minimum thresholds
+- [ ] No test was modified to make it pass
+
+### REFACTOR Phase Validation
+- [ ] All tests still pass after refactoring
+- [ ] Code complexity reduced
+- [ ] Duplication eliminated
+- [ ] Performance improved or maintained
+- [ ] Test readability improved
+
+## Coverage Reports
+
+Generate coverage reports after each phase:
+- Line coverage
+- Branch coverage
+- Function coverage
+- Statement coverage
+
+## Failure Recovery
+
+If TDD discipline is broken:
+1. **STOP** immediately
+2. Identify which phase was violated
+3. Rollback to last valid state
+4. Resume from correct phase
+5. Document lesson learned
+
+## TDD Metrics Tracking
+
+Track and report:
+- Time in each phase (Red/Green/Refactor)
+- Number of test-implementation cycles
+- Coverage progression
+- Refactoring frequency
+- Defect escape rate
+
+## Anti-Patterns to Avoid
+
+- Writing implementation before tests
+- Writing tests that already pass
+- Skipping the refactor phase
+- Writing multiple features without tests
+- Modifying tests to make them pass
+- Ignoring failing tests
+- Writing tests after implementation
+
+## Success Criteria
+
+- 100% of code written test-first
+- All tests pass continuously
+- Coverage exceeds thresholds
+- Code complexity within limits
+- Zero defects in covered code
+- Clear test documentation
+- Fast test execution (< 5 seconds for unit tests)
+
+## Notes
+
+- Enforce strict RED-GREEN-REFACTOR discipline
+- Each phase must be completed before moving to next
+- Tests are the specification
+- If a test is hard to write, the design needs improvement
+- Refactoring is NOT optional
+- Keep test execution fast
+- Tests should be independent and isolated
+
+TDD implementation for: $ARGUMENTS

package/merged-commands/tdd-workflows-tdd-green.md

@@ -0,0 +1,73 @@
+---
+name: tdd-workflows-tdd-green
+description: Implement the minimal code needed to make failing tests pass in the TDD green phase.
+---
+
+# Green Phase: Simple function
+def product_list(request):
+    products = Product.objects.all()
+    return JsonResponse({'products': list(products.values())})
+
+# Refactor: Class-based view
+class ProductListView(View):
+    def get(self, request):
+        products = Product.objects.all()
+        return JsonResponse({'products': list(products.values())})
+
+# Refactor: Generic view
+class ProductListView(ListView):
+    model = Product
+    context_object_name = 'products'
+```
+
+### Express Patterns
+
+**Inline → Middleware → Service Layer:**
+```javascript
+// Green Phase: Inline logic
+app.post('/api/users', (req, res) => {
+  const user = { id: Date.now(), ...req.body };
+  users.push(user);
+  res.json(user);
+});
+
+// Refactor: Extract middleware
+app.post('/api/users', validateUser, (req, res) => {
+  const user = userService.create(req.body);
+  res.json(user);
+});
+
+// Refactor: Full layering
+app.post('/api/users',
+  validateUser,
+  asyncHandler(userController.create)
+);
+```
+
+## Use this skill when
+
+- Moving from red to green in a TDD cycle
+- Implementing minimal behavior to satisfy tests
+- You want to keep implementation intentionally simple
+
+## Do not use this skill when
+
+- You are refactoring for design or performance
+- Tests are already passing and you need new requirements
+- You need a full architectural redesign
+
+## Instructions
+
+1. Review failing tests and identify the smallest fix.
+2. Implement the minimal change to pass the next test.
+3. Run tests after each change to confirm progress.
+4. Record shortcuts or debt for the refactor phase.
+
+## Safety
+
+- Avoid bypassing tests to make them pass.
+- Keep changes scoped to the failing behavior only.
+
+## Resources
+
+- `resources/implementation-playbook.md` for detailed patterns and examples.

package/merged-commands/tdd-workflows-tdd-red.md

@@ -0,0 +1,164 @@
+---
+name: tdd-workflows-tdd-red
+description: Generate failing tests for the TDD red phase to define expected behavior and edge cases.
+---
+
+Write comprehensive failing tests following TDD red phase principles.
+
+[Extended thinking: Generates failing tests that properly define expected behavior using test-automator agent.]
+
+## Use this skill when
+
+- Starting the TDD red phase for new behavior
+- You need failing tests that capture expected behavior
+- You want edge case coverage before implementation
+
+## Do not use this skill when
+
+- You are in the green or refactor phase
+- You only need performance benchmarks
+- Tests must run against production systems
+
+## Instructions
+
+1. Identify behaviors, constraints, and edge cases.
+2. Generate failing tests that define expected outcomes.
+3. Ensure failures are due to missing behavior, not setup errors.
+4. Document how to run tests and verify failures.
+
+## Safety
+
+- Keep test data isolated and avoid production environments.
+- Avoid flaky external dependencies in the red phase.
+
+## Role
+
+Generate failing tests using Task tool with subagent_type="unit-testing::test-automator".
+
+## Prompt Template
+
+"Generate comprehensive FAILING tests for: $ARGUMENTS
+
+## Core Requirements
+
+1. **Test Structure**
+   - Framework-appropriate setup (Jest/pytest/JUnit/Go/RSpec)
+   - Arrange-Act-Assert pattern
+   - should_X_when_Y naming convention
+   - Isolated fixtures with no interdependencies
+
+2. **Behavior Coverage**
+   - Happy path scenarios
+   - Edge cases (empty, null, boundary values)
+   - Error handling and exceptions
+   - Concurrent access (if applicable)
+
+3. **Failure Verification**
+   - Tests MUST fail when run
+   - Failures for RIGHT reasons (not syntax/import errors)
+   - Meaningful diagnostic error messages
+   - No cascading failures
+
+4. **Test Categories**
+   - Unit: Isolated component behavior
+   - Integration: Component interaction
+   - Contract: API/interface contracts
+   - Property: Mathematical invariants
+
+## Framework Patterns
+
+**JavaScript/TypeScript (Jest/Vitest)**
+- Mock dependencies with `vi.fn()` or `jest.fn()`
+- Use `@testing-library` for React components
+- Property tests with `fast-check`
+
+**Python (pytest)**
+- Fixtures with appropriate scopes
+- Parametrize for multiple test cases
+- Hypothesis for property-based tests
+
+**Go**
+- Table-driven tests with subtests
+- `t.Parallel()` for parallel execution
+- Use `testify/assert` for cleaner assertions
+
+**Ruby (RSpec)**
+- `let` for lazy loading, `let!` for eager
+- Contexts for different scenarios
+- Shared examples for common behavior
+
+## Quality Checklist
+
+- Readable test names documenting intent
+- One behavior per test
+- No implementation leakage
+- Meaningful test data (not 'foo'/'bar')
+- Tests serve as living documentation
+
+## Anti-Patterns to Avoid
+
+- Tests passing immediately
+- Testing implementation vs behavior
+- Complex setup code
+- Multiple responsibilities per test
+- Brittle tests tied to specifics
+
+## Edge Case Categories
+
+- **Null/Empty**: undefined, null, empty string/array/object
+- **Boundaries**: min/max values, single element, capacity limits
+- **Special Cases**: Unicode, whitespace, special characters
+- **State**: Invalid transitions, concurrent modifications
+- **Errors**: Network failures, timeouts, permissions
+
+## Output Requirements
+
+- Complete test files with imports
+- Documentation of test purpose
+- Commands to run and verify failures
+- Metrics: test count, coverage areas
+- Next steps for green phase"
+
+## Validation
+
+After generation:
+1. Run tests - confirm they fail
+2. Verify helpful failure messages
+3. Check test independence
+4. Ensure comprehensive coverage
+
+## Example (Minimal)
+
+```typescript
+// auth.service.test.ts
+describe('AuthService', () => {
+  let authService: AuthService;
+  let mockUserRepo: jest.Mocked<UserRepository>;
+
+  beforeEach(() => {
+    mockUserRepo = { findByEmail: jest.fn() } as any;
+    authService = new AuthService(mockUserRepo);
+  });
+
+  it('should_return_token_when_valid_credentials', async () => {
+    const user = { id: '1', email: 'test@example.com', passwordHash: 'hashed' };
+    mockUserRepo.findByEmail.mockResolvedValue(user);
+
+    const result = await authService.authenticate('test@example.com', 'pass');
+
+    expect(result.success).toBe(true);
+    expect(result.token).toBeDefined();
+  });
+
+  it('should_fail_when_user_not_found', async () => {
+    mockUserRepo.findByEmail.mockResolvedValue(null);
+
+    const result = await authService.authenticate('none@example.com', 'pass');
+
+    expect(result.success).toBe(false);
+    expect(result.error).toBe('INVALID_CREDENTIALS');
+  });
+});
+```
+
+Test requirements: $ARGUMENTS

package/merged-commands/tdd-workflows-tdd-refactor.md

@@ -0,0 +1,187 @@
+---
+name: tdd-workflows-tdd-refactor
+description: "Use when working with tdd workflows tdd refactor"
+---
+
+## Use this skill when
+
+- Working on tdd workflows tdd refactor tasks or workflows
+- Needing guidance, best practices, or checklists for tdd workflows tdd refactor
+
+## Do not use this skill when
+
+- The task is unrelated to tdd workflows tdd refactor
+- You need a different domain or tool outside this scope
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+Refactor code with confidence using comprehensive test safety net:
+
+[Extended thinking: This tool uses the tdd-orchestrator agent (opus model) for sophisticated refactoring while maintaining all tests green. It applies design patterns, improves code quality, and optimizes performance with the safety of comprehensive test coverage.]
+
+## Usage
+
+Use Task tool with subagent_type="tdd-orchestrator" to perform safe refactoring.
+
+Prompt: "Refactor this code while keeping all tests green: $ARGUMENTS. Apply TDD refactor phase:
+
+## Core Process
+
+**1. Pre-Assessment**
+- Run tests to establish green baseline
+- Analyze code smells and test coverage
+- Document current performance metrics
+- Create incremental refactoring plan
+
+**2. Code Smell Detection**
+- Duplicated code → Extract methods/classes
+- Long methods → Decompose into focused functions
+- Large classes → Split responsibilities
+- Long parameter lists → Parameter objects
+- Feature Envy → Move methods to appropriate classes
+- Primitive Obsession → Value objects
+- Switch statements → Polymorphism
+- Dead code → Remove
+
+**3. Design Patterns**
+- Apply Creational (Factory, Builder, Singleton)
+- Apply Structural (Adapter, Facade, Decorator)
+- Apply Behavioral (Strategy, Observer, Command)
+- Apply Domain (Repository, Service, Value Objects)
+- Use patterns only where they add clear value
+
+**4. SOLID Principles**
+- Single Responsibility: One reason to change
+- Open/Closed: Open for extension, closed for modification
+- Liskov Substitution: Subtypes substitutable
+- Interface Segregation: Small, focused interfaces
+- Dependency Inversion: Depend on abstractions
+
+**5. Refactoring Techniques**
+- Extract Method/Variable/Interface
+- Inline unnecessary indirection
+- Rename for clarity
+- Move Method/Field to appropriate classes
+- Replace Magic Numbers with constants
+- Encapsulate fields
+- Replace Conditional with Polymorphism
+- Introduce Null Object
+
+**6. Performance Optimization**
+- Profile to identify bottlenecks
+- Optimize algorithms and data structures
+- Implement caching where beneficial
+- Reduce database queries (N+1 elimination)
+- Lazy loading and pagination
+- Always measure before and after
+
+**7. Incremental Steps**
+- Make small, atomic changes
+- Run tests after each modification
+- Commit after each successful refactoring
+- Keep refactoring separate from behavior changes
+- Use scaffolding when needed
+
+**8. Architecture Evolution**
+- Layer separation and dependency management
+- Module boundaries and interface definition
+- Event-driven patterns for decoupling
+- Database access pattern optimization
+
+**9. Safety Verification**
+- Run full test suite after each change
+- Performance regression testing
+- Mutation testing for test effectiveness
+- Rollback plan for major changes
+
+**10. Advanced Patterns**
+- Strangler Fig: Gradual legacy replacement
+- Branch by Abstraction: Large-scale changes
+- Parallel Change: Expand-contract pattern
+- Mikado Method: Dependency graph navigation
+
+## Output Requirements
+
+- Refactored code with improvements applied
+- Test results (all green)
+- Before/after metrics comparison
+- Applied refactoring techniques list
+- Performance improvement measurements
+- Remaining technical debt assessment
+
+## Safety Checklist
+
+Before committing:
+- ✓ All tests pass (100% green)
+- ✓ No functionality regression
+- ✓ Performance metrics acceptable
+- ✓ Code coverage maintained/improved
+- ✓ Documentation updated
+
+## Recovery Protocol
+
+If tests fail:
+- Immediately revert last change
+- Identify breaking refactoring
+- Apply smaller incremental changes
+- Use version control for safe experimentation
+
+## Example: Extract Method Pattern
+
+**Before:**
+```typescript
+class OrderProcessor {
+  processOrder(order: Order): ProcessResult {
+    // Validation
+    if (!order.customerId || order.items.length === 0) {
+      return { success: false, error: "Invalid order" };
+    }
+
+    // Calculate totals
+    let subtotal = 0;
+    for (const item of order.items) {
+      subtotal += item.price * item.quantity;
+    }
+    let total = subtotal + (subtotal * 0.08) + (subtotal > 100 ? 0 : 15);
+
+    // Process payment...
+    // Update inventory...
+    // Send confirmation...
+  }
+}
+```
+
+**After:**
+```typescript
+class OrderProcessor {
+  async processOrder(order: Order): Promise<ProcessResult> {
+    const validation = this.validateOrder(order);
+    if (!validation.isValid) return ProcessResult.failure(validation.error);
+
+    const orderTotal = OrderTotal.calculate(order);
+    const inventoryCheck = await this.inventoryService.checkAvailability(order.items);
+    if (!inventoryCheck.available) return ProcessResult.failure(inventoryCheck.reason);
+
+    await this.paymentService.processPayment(order.paymentMethod, orderTotal.total);
+    await this.inventoryService.reserveItems(order.items);
+    await this.notificationService.sendOrderConfirmation(order, orderTotal);
+
+    return ProcessResult.success(order.id, orderTotal.total);
+  }
+
+  private validateOrder(order: Order): ValidationResult {
+    if (!order.customerId) return ValidationResult.invalid("Customer ID required");
+    if (order.items.length === 0) return ValidationResult.invalid("Order must contain items");
+    return ValidationResult.valid();
+  }
+}
+```
+
+**Applied:** Extract Method, Value Objects, Dependency Injection, Async patterns
+
+Code to refactor: $ARGUMENTS"

package/merged-commands/team-collaboration-issue.md

@@ -0,0 +1,37 @@
+---
+name: team-collaboration-issue
+description: "You are a GitHub issue resolution expert specializing in systematic bug investigation, feature implementation, and collaborative development workflows. Your expertise spans issue triage, root cause an"
+---
+
+# GitHub Issue Resolution Expert
+
+You are a GitHub issue resolution expert specializing in systematic bug investigation, feature implementation, and collaborative development workflows. Your expertise spans issue triage, root cause analysis, test-driven development, and pull request management. You excel at transforming vague bug reports into actionable fixes and feature requests into production-ready code.
+
+## Use this skill when
+
+- Working on github issue resolution expert tasks or workflows
+- Needing guidance, best practices, or checklists for github issue resolution expert
+
+## Do not use this skill when
+
+- The task is unrelated to github issue resolution expert
+- You need a different domain or tool outside this scope
+
+## Context
+
+The user needs comprehensive GitHub issue resolution that goes beyond simple fixes. Focus on thorough investigation, proper branch management, systematic implementation with testing, and professional pull request creation that follows modern CI/CD practices.
+
+## Requirements
+
+GitHub Issue ID or URL: $ARGUMENTS
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+## Resources
+
+- `resources/implementation-playbook.md` for detailed patterns and examples.