@codemieai/code 0.0.58 → 0.2.0

package/dist/agents/plugins/claude/plugin/claude-templates/templates/guides/testing/testing-patterns.md.template

@@ -1,315 +0,0 @@
----
-# Testing Patterns
-
-<!--
-GENERATION INSTRUCTIONS:
-1. Identify test framework from dependencies/config
-2. Scan test directory structure and naming patterns
-3. Extract fixture/factory patterns from setup files
-4. Find mocking patterns in existing tests
-5. Locate test database configuration
-6. Extract commands from package.json/Makefile/scripts
-7. Output: 150-300 lines max
--->
-
-**Project**: [Extract from config]
-**Framework**: [Detect: Jest | Pytest | Mocha | Vitest | RSpec | etc.]
-**Coverage Tool**: [Detect: coverage.py | nyc | c8 | etc.]
-**Test Location**: `[Detect tests/ or __tests__/ or spec/]`
-
----
-
-## Test Organization
-
-<!-- Scan actual test directory structure -->
-
-```
-[test_root]/
-├── [unit/]                 [Detected structure]
-│   └── [pattern]/
-├── [integration/]          [If exists]
-│   └── [pattern]/
-├── [e2e/]                  [If exists]
-├── [fixtures/factories/]   [Test data location]
-└── [setup files]           [conftest.py, setup.ts, etc.]
-```
-
-### Naming Conventions
-
-| Element | Pattern | Example |
-|---------|---------|---------|
-| Test files | `[detected pattern]` | `[actual example]` |
-| Test functions | `[detected pattern]` | `[actual example]` |
-| Fixture files | `[detected pattern]` | `[actual example]` |
-
----
-
-## Running Tests
-
-<!-- Extract exact commands from scripts -->
-
-| Action | Command |
-|--------|---------|
-| All tests | `[exact command]` |
-| Unit only | `[command or N/A]` |
-| Integration only | `[command or N/A]` |
-| Single file | `[command pattern]` |
-| Single test | `[command pattern]` |
-| Watch mode | `[command or N/A]` |
-| With coverage | `[command]` |
-| Verbose/debug | `[command with flags]` |
-
----
-
-## Unit Test Pattern
-
-<!-- Extract canonical unit test example -->
-
-```[lang]
-// Source: [file:lines]
-[Extract representative unit test showing framework syntax]
-```
-
-### Structure
-
-```[lang]
-// Standard test structure in this codebase:
-[describe/test block] {
-    // Arrange - setup test data
-    // Act - call function under test
-    // Assert - verify result
-}
-```
-
----
-
-## Fixtures / Test Data
-
-<!-- Find fixture or factory patterns -->
-
-### Setup Pattern
-
-```[lang]
-// Source: [file:lines]
-[Extract fixture/factory definition]
-```
-
-### Using Fixtures
-
-```[lang]
-// Source: [file:lines]
-[Extract fixture usage in test]
-```
-
-### Common Fixtures
-
-| Fixture | Purpose | Location |
-|---------|---------|----------|
-| `[fixture name]` | [What it provides] | `[file:line]` |
-| `[fixture name]` | [What it provides] | `[file:line]` |
-| `[fixture name]` | [What it provides] | `[file:line]` |
-
----
-
-## Mocking
-
-<!-- Extract mocking patterns used -->
-
-### Mock Syntax
-
-```[lang]
-// Source: [file:lines]
-[Extract mocking example - service, module, or function mock]
-```
-
-### What to Mock
-
-| Layer | Mock In Unit Tests | Mock In Integration |
-|-------|-------------------|---------------------|
-| External APIs | ✅ Always | ✅ Usually |
-| Database | ✅ Usually | ❌ Use test DB |
-| Other services | ✅ Yes | Depends |
-| File system | ✅ Yes | Depends |
-| Time/Date | ✅ When needed | When needed |
-
-### Mock Patterns in This Codebase
-
-| What | How | Source |
-|------|-----|--------|
-| `[Service/Module]` | `[mock syntax]` | `[file:line]` |
-| `[External API]` | `[mock syntax]` | `[file:line]` |
-| `[Database/Repository]` | `[mock syntax]` | `[file:line]` |
-
----
-
-## Database Testing
-
-<!-- Find test database configuration -->
-
-### Setup
-
-**Test DB**: `[separate DB / transactions / in-memory / mocked]`
-
-```[lang]
-// Source: [file:lines]
-[Extract test DB setup/connection]
-```
-
-### Isolation Pattern
-
-```[lang]
-// Source: [file:lines]
-[Extract transaction rollback or cleanup pattern]
-```
-
-### Seeding Test Data
-
-```[lang]
-// Source: [file:lines]
-[Extract test data seeding pattern]
-```
-
----
-
-## API / Endpoint Testing
-
-<!-- If web app, find HTTP testing patterns -->
-
-### Test Client Setup
-
-```[lang]
-// Source: [file:lines]
-[Extract test client/supertest/httpx setup]
-```
-
-### Request Pattern
-
-```[lang]
-// Source: [file:lines]
-[Extract API test example]
-```
-
----
-
-## Async Testing
-
-<!-- If async code exists, find testing pattern -->
-
-```[lang]
-// Source: [file:lines]
-[Extract async test example]
-```
-
-**Pattern**: `[async/await | done callback | returns promise]`
-
----
-
-## Parameterized Tests
-
-<!-- Find data-driven test patterns -->
-
-```[lang]
-// Source: [file:lines]
-[Extract parameterized/table-driven test]
-```
-
----
-
-## Coverage
-
-<!-- Extract coverage configuration -->
-
-### Configuration
-
-**Config file**: `[jest.config / .coveragerc / nyc config]`
-
-| Setting | Value |
-|---------|-------|
-| Threshold | `[percentage or N/A]` |
-| Include | `[paths/patterns]` |
-| Exclude | `[paths/patterns]` |
-
-### Generate Report
-
-```bash
-# Generate coverage report
-[coverage command]
-
-# View HTML report (if available)
-[open coverage/index.html or equivalent]
-```
-
----
-
-## Test Environment
-
-<!-- Find environment setup for tests -->
-
-### Environment Variables
-
-```[lang]
-// Source: [file:lines] or [.env.test]
-[Extract test environment config]
-```
-
-### Setup/Teardown
-
-```[lang]
-// Source: [file:lines]
-[Extract global setup/teardown if exists]
-```
-
----
-
-## Writing New Tests
-
-### Checklist
-
-1. Create test file: `[path pattern]`
-2. Import test utilities: `[common imports]`
-3. Setup fixtures needed
-4. Follow naming: `[test naming pattern]`
-5. Run to verify: `[run single test command]`
-
-### Template
-
-```[lang]
-// Starter template for new test file
-[Extract or construct minimal test file template]
-```
-
----
-
-## Common Patterns
-
-| Pattern | When to Use | Example |
-|---------|-------------|---------|
-| `[beforeEach/setUp]` | Reset state per test | `[file:line]` |
-| `[afterAll/teardown]` | Cleanup resources | `[file:line]` |
-| `[test.skip/xtest]` | Temporarily disable | - |
-| `[test.only/fit]` | Run single test (debug) | - |
-
----
-
-## Troubleshooting
-
-| Issue | Solution |
-|-------|----------|
-| Tests interfering | Check isolation, add cleanup |
-| Async timeout | Increase timeout or check await |
-| Mock not working | Verify mock path matches import |
-| DB state issues | Check transaction rollback |
-
----
-
-## Quick Reference
-
-| Need | Location |
-|------|----------|
-| Test config | `[config file path]` |
-| Fixtures | `[fixtures path]` |
-| Factories | `[factories path]` |
-| Test utilities | `[helpers/utils path]` |
-| Coverage config | `[config path]` |
-
----

package/dist/agents/plugins/claude/plugin/commands/codemie-commit.md

@@ -1,31 +0,0 @@
----
-allowed-tools: Bash(git add:*), Bash(git commit:*), Bash(git checkout:*)
-description: Create a git commit (not on main branch)
----
-
-## Context
-
-- Current branch: !`git branch --show-current`
-- Current git status: !`git status`
-- Current git diff (staged and unstaged changes): !`git diff HEAD`
-- Recent commits: !`git log --oneline -5`
-
-## Your task
-
-Based on the above changes, create a single git commit.
-
-**IMPORTANT**: If the current branch is `main` or `master`:
-1. Analyze the changes to determine the type (feat, fix, refactor, etc.)
-2. Suggest a branch name in format `<type>/<short-description>` (e.g., `feat/add-auth-header-support`, `fix/proxy-timeout-issue`)
-3. Ask user to confirm the branch name or provide an alternative
-4. After confirmation, create the branch with `git checkout -b <branch-name>` and proceed with the commit
-
-If on a feature branch:
-1. Stage all relevant changes
-2. Create a commit message following commitlint rules:
-   - Format: `<type>(<scope>): <subject>` or `<type>: <subject>`
-   - Types: feat, fix, docs, style, refactor, perf, test, chore, ci, revert
-   - Scopes (optional): cli, agents, providers, config, proxy, workflows, ci, analytics, utils, deps, tests
-   - Subject: max 100 characters, lowercase start, no period at end
-
-You have the capability to call multiple tools in a single response. Stage and create the commit using a single message. Do not use any other tools or do anything else. Do not send any other text or messages besides these tool calls.