opencode-agile-agent 1.0.1 → 1.0.3

package/templates/.opencode/workflows/review.md

@@ -1,135 +0,0 @@
----
-description: Code review workflow for validating implementations. Use when reviewing code quality and standards compliance.
----
-
-# /review Workflow
-
-Comprehensive code review against project standards and best practices.
-
-## When to Use
-
-- After completing implementation
-- Before merging PRs
-- Quality assurance
-- Standards compliance check
-
-## Workflow Steps
-
-### Step 1: Identify Scope
-
-```
-What to review:
-- Recent changes
-- Specific files
-- Full codebase
-- Specific concerns (security, performance, etc.)
-```
-
-### Step 2: Run Automated Checks
-
-```
-Automated quality gates:
-- [ ] Linting passes
-- [ ] TypeScript compiles
-- [ ] Tests pass
-- [ ] No security vulnerabilities
-```
-
-### Step 3: Manual Review
-
-```
-Code quality review:
-- [ ] Code follows project conventions
-- [ ] No anti-patterns detected
-- [ ] Proper error handling
-- [ ] Appropriate abstractions
-- [ ] Clear naming
-- [ ] Adequate comments
-```
-
-### Step 4: Domain-Specific Review
-
-```
-Based on code type:
-- Frontend: Accessibility, performance, responsive
-- Backend: Security, error handling, validation
-- Database: Indexes, query efficiency, migrations
-```
-
-### Step 5: Generate Report
-
-```
-Review summary:
-- Overall assessment
-- Issues found (critical, major, minor)
-- Recommendations
-- Approval status
-```
-
-## Review Checklist
-
-### General
-- [ ] Code is readable and maintainable
-- [ ] Functions have single responsibility
-- [ ] No code duplication
-- [ ] Proper error handling
-- [ ] Appropriate logging
-
-### Security
-- [ ] No hardcoded secrets
-- [ ] Input validation present
-- [ ] Proper authentication checks
-- [ ] SQL injection prevention
-- [ ] XSS prevention
-
-### Performance
-- [ ] No N+1 queries
-- [ ] Appropriate caching
-- [ ] No memory leaks
-- [ ] Efficient algorithms
-
-### Testing
-- [ ] Adequate test coverage
-- [ ] Tests are meaningful
-- [ ] Edge cases covered
-
-## Example
-
-```
-User: /review recent changes
-
-Agent: I'll review the recent changes.
-
-**Scope:** Last 5 commits (auth feature)
-
-**Automated Checks:**
-- [x] Lint: Pass
-- [x] TypeScript: Pass
-- [x] Tests: 12/12 Pass
-- [x] Security: No vulnerabilities
-
-**Code Review:**
-
-✅ Good:
-- Clear function naming
-- Proper error handling
-- Tests for edge cases
-
-⚠️ Issues Found:
-
-[MAJOR] auth.service.ts:45
-- Password comparison not timing-safe
-- Recommendation: Use bcrypt.compare()
-
-[MINOR] login.tsx:23
-- Missing loading state during submission
-- Recommendation: Add isSubmitting state
-
-**Verdict: CHANGES REQUESTED**
-
-Please address the timing-safe comparison issue before merging.
-```
-
----
-
-**Review catches what automation misses.**

package/templates/.opencode/workflows/status.md

@@ -1,102 +0,0 @@
----
-description: Check project status, health, and metrics. Use for quick project overview.
----
-
-# /status Workflow
-
-Get a quick overview of project status, health, and key metrics.
-
-## When to Use
-
-- Starting a work session
-- Quick project health check
-- Before/after changes
-- Daily standup preparation
-
-## Workflow Steps
-
-### Step 1: Analyze Codebase
-
-```
-Gather information:
-- Project structure
-- Technology stack
-- File counts
-- Code statistics
-```
-
-### Step 2: Check Quality
-
-```
-Run quality checks:
-- Linting status
-- Type check status
-- Test status
-- Build status
-```
-
-### Step 3: Check Dependencies
-
-```
-Review dependencies:
-- Outdated packages
-- Security vulnerabilities
-- Unused dependencies
-```
-
-### Step 4: Generate Report
-
-```
-Create status summary:
-- Project health score
-- Key metrics
-- Recommendations
-```
-
-## Example Output
-
-```markdown
-# Project Status
-
-## Overview
-- **Type**: Next.js Application
-- **Framework**: React 18
-- **Language**: TypeScript
-
-## Statistics
-- Files: 245
-- Lines of code: ~15,000
-- Components: 42
-- Pages: 12
-- API Routes: 8
-
-## Quality Checks
-| Check | Status |
-|-------|--------|
-| Lint | ✅ Pass |
-| TypeScript | ✅ Pass |
-| Tests | ✅ 156/156 |
-| Build | ✅ Success |
-
-## Dependencies
-- **Total**: 48
-- **Outdated**: 3
-- **Vulnerabilities**: 0
-
-## Test Coverage
-- Statements: 82%
-- Branches: 78%
-- Functions: 85%
-- Lines: 81%
-
-## Recommendations
-1. Update 3 outdated packages
-2. Improve branch coverage to 80%+
-3. Consider adding E2E tests
-
-## Health Score: 85/100
-```
-
----
-
-**Know your project's health at a glance.**

package/templates/.opencode/workflows/test.md

@@ -1,146 +0,0 @@
----
-description: Run and generate tests for the codebase. Use when adding test coverage or running test suites.
----
-
-# /test Workflow
-
-Generate, run, and manage tests for your codebase.
-
-## When to Use
-
-- Running test suites
-- Adding test coverage
-- Fixing failing tests
-- Setting up testing infrastructure
-
-## Workflow Steps
-
-### Step 1: Identify Test Scope
-
-```
-What to test:
-- Specific files or functions?
-- Full test suite?
-- Integration tests?
-- E2E tests?
-```
-
-### Step 2: Run Tests
-
-```bash
-# Unit tests
-npm test
-
-# With coverage
-npm run test:coverage
-
-# Watch mode
-npm run test:watch
-
-# E2E tests
-npm run test:e2e
-```
-
-### Step 3: Analyze Results
-
-```
-Review results:
-- Which tests passed?
-- Which tests failed?
-- What's the coverage?
-- Are there flaky tests?
-```
-
-### Step 4: Fix or Add Tests
-
-```
-For failing tests:
-1. Identify the cause
-2. Fix the code or test
-3. Verify fix
-
-For missing coverage:
-1. Identify uncovered code
-2. Write appropriate tests
-3. Verify coverage improvement
-```
-
-## Test Types
-
-### Unit Tests
-
-```typescript
-describe('calculateTotal', () => {
-  it('should sum item prices', () => {
-    const items = [{ price: 10 }, { price: 20 }];
-    expect(calculateTotal(items)).toBe(30);
-  });
-
-  it('should handle empty array', () => {
-    expect(calculateTotal([])).toBe(0);
-  });
-});
-```
-
-### Integration Tests
-
-```typescript
-describe('POST /api/users', () => {
-  it('should create user', async () => {
-    const response = await request(app)
-      .post('/api/users')
-      .send({ name: 'Test', email: 'test@example.com' });
-    
-    expect(response.status).toBe(201);
-    expect(response.body.name).toBe('Test');
-  });
-});
-```
-
-## Example
-
-```
-User: /test checkout flow
-
-Agent: I'll help you test the checkout flow.
-
-**Test Scope:**
-- Unit tests for calculation functions
-- Integration tests for API endpoints
-- E2E test for full checkout flow
-
-**Running Tests:**
-
-[Unit Tests] calculateTotal
-  ✅ should sum item prices
-  ✅ should apply discounts
-  ✅ should handle empty cart
-
-[Unit Tests] validatePayment
-  ✅ should validate card number
-  ✅ should reject invalid cards
-
-[Integration Tests] POST /api/checkout
-  ✅ should process payment
-  ❌ should send confirmation email
-
-**Failed Test:**
-- should send confirmation email
-- Error: Email service not mocked
-- Fix: Add mock for email service
-
-**Coverage:**
-- Statements: 82%
-- Branches: 78%
-- Functions: 85%
-- Lines: 81%
-
-**Next Steps:**
-1. Fix failing email test
-2. Add E2E test for full flow
-3. Improve branch coverage
-```
-
----
-
-**Tests enable confident refactoring.**