@codedir/mimir-code 0.1.0 → 0.1.1

package/scripts/templates/commands/perf.yml

@@ -1,56 +0,0 @@
-# Performance Analysis Command
-# Analyzes code for performance issues and optimizations
-# Usage: /perf [file-or-function]
-
-name: perf
-description: Analyze code for performance issues and optimizations
-usage: /perf [file-or-function]
-aliases: [performance, optimize]
-prompt: |
-  Analyze the specified code for performance issues and optimization opportunities:
-
-  **Algorithmic Complexity:**
-  - Identify O(n²) or worse algorithms
-  - Suggest more efficient data structures
-  - Spot unnecessary iterations
-  - Recommend parallelization opportunities
-
-  **Resource Usage:**
-  - Memory leaks and excessive allocations
-  - File handle/connection leaks
-  - Large object creation in hot paths
-  - Unnecessary cloning/copying
-
-  **I/O Operations:**
-  - N+1 query problems (database)
-  - Missing pagination/batching
-  - Synchronous I/O in async contexts
-  - Missing caching layers
-
-  **Frontend-Specific:**
-  - Unnecessary re-renders (React/Vue)
-  - Large bundle sizes
-  - Missing lazy loading
-  - Unoptimized images/assets
-  - Blocking JavaScript
-
-  **Backend-Specific:**
-  - Missing database indexes
-  - Inefficient ORM queries
-  - Missing connection pooling
-  - Blocking event loop (Node.js)
-
-  **Target:**
-  $ARGUMENTS
-
-  **Output:**
-  1. Performance hotspots ranked by impact
-  2. For each issue:
-     - Current implementation
-     - Optimized version
-     - Expected improvement (with reasoning)
-     - Complexity analysis (before/after)
-  3. Quick wins vs long-term refactors
-
-  If no target specified, analyze the current working directory.
-  Focus on high-impact optimizations. Include benchmark suggestions.

package/scripts/templates/commands/refactor.yml

@@ -1,52 +0,0 @@
-# Code Refactoring Command
-# Suggests refactoring improvements for better code quality
-# Usage: /refactor [file-or-pattern]
-
-name: refactor
-description: Suggest refactoring improvements for code quality
-usage: /refactor [file-or-pattern]
-aliases: [ref, improve]
-prompt: |
-  Analyze the specified code and suggest refactoring improvements. Focus on:
-
-  **Code Smells:**
-  - Long methods/functions (>50 lines)
-  - Large classes (>300 lines)
-  - Duplicate code (DRY violations)
-  - Dead code and unused variables
-  - Magic numbers and hardcoded values
-  - Deeply nested conditionals (>3 levels)
-  - Feature envy (accessing other objects' data excessively)
-
-  **Design Patterns:**
-  - Missing abstractions or interfaces
-  - Inappropriate coupling (tight coupling where loose is better)
-  - Single Responsibility Principle violations
-  - Open/Closed Principle violations
-  - Dependency injection opportunities
-
-  **Performance:**
-  - Inefficient algorithms (O(n²) where O(n log n) possible)
-  - Unnecessary computations in loops
-  - Memory leaks or excessive allocations
-  - Missing caching opportunities
-
-  **Readability:**
-  - Poor naming (unclear variable/function names)
-  - Missing documentation for complex logic
-  - Inconsistent code style
-  - Complex boolean expressions
-
-  **Target:**
-  $ARGUMENTS
-
-  **Output:**
-  1. Priority-ranked list of refactorings (high/medium/low impact)
-  2. For each suggestion:
-     - Before/after code comparison
-     - Rationale (why this improves the code)
-     - Estimated effort (quick win / medium / large refactor)
-  3. No-regret moves (safe refactorings with minimal risk)
-
-  If no target specified, analyze files changed in the last commit.
-  Provide actionable, specific suggestions with code examples.

package/scripts/templates/commands/review.yml

@@ -1,62 +0,0 @@
-# Code Review Command
-# Performs comprehensive code review with best practices
-# Usage: /review [file-or-commit]
-
-name: review
-description: Perform comprehensive code review
-usage: /review [file-or-commit]
-aliases: [cr, check]
-prompt: |
-  Conduct a thorough code review of the specified changes. Evaluate:
-
-  **Correctness:**
-  - Logic errors and bugs
-  - Off-by-one errors
-  - Null pointer/undefined access
-  - Race conditions and concurrency issues
-  - Error handling completeness
-
-  **Code Quality:**
-  - Readability and maintainability
-  - Naming conventions (clear, consistent)
-  - Function/method length and complexity
-  - Code duplication (DRY principle)
-  - Single Responsibility Principle
-
-  **Performance:**
-  - Algorithmic complexity (O(n) analysis)
-  - Unnecessary database queries (N+1 problems)
-  - Memory inefficiencies
-  - Blocking operations in async contexts
-
-  **Testing:**
-  - Test coverage for new code
-  - Test quality (meaningful assertions)
-  - Edge cases covered
-  - Mocking strategy appropriateness
-
-  **Security:**
-  - Input validation
-  - SQL injection, XSS, CSRF risks
-  - Authentication/authorization checks
-  - Sensitive data exposure
-
-  **Architecture:**
-  - Consistency with project patterns
-  - API design (backward compatibility)
-  - Dependency management
-  - Separation of concerns
-
-  **Target:**
-  $ARGUMENTS
-
-  **Output Format:**
-  1. Overall assessment (LGTM, Needs Work, Requires Changes)
-  2. Critical issues (must fix before merge)
-  3. Suggestions (nice-to-have improvements)
-  4. Positive feedback (what's done well)
-  5. Line-specific comments with file:line references
-
-  If no target specified, review the current staged changes.
-  Be constructive and specific. Provide code snippets for fixes.
-  Balance thoroughness with pragmatism.

package/scripts/templates/commands/security.yml

@@ -1,51 +0,0 @@
-# Security Analysis Command
-# Analyzes git diffs for security vulnerabilities and issues
-# Usage: /security [file-or-commit]
-
-name: security
-description: Analyze git changes for security vulnerabilities
-usage: /security [file-or-commit]
-aliases: [sec, vuln]
-prompt: |
-  Perform a comprehensive security analysis of the git diff. Focus on:
-
-  **Critical Security Issues:**
-  - SQL injection vulnerabilities (unsanitized input in queries)
-  - XSS vulnerabilities (unescaped output in HTML/templates)
-  - Command injection (unsanitized shell execution)
-  - Path traversal (directory traversal attacks via user input)
-  - Authentication/authorization bypass
-  - Hardcoded secrets, API keys, passwords, or tokens
-  - Insecure cryptography (weak algorithms, hardcoded keys)
-  - CSRF vulnerabilities (missing tokens on state-changing operations)
-
-  **High-Priority Issues:**
-  - Input validation gaps (missing sanitization, type checking)
-  - Unsafe deserialization
-  - Race conditions in concurrent code
-  - Information disclosure in error messages
-  - Insecure defaults or misconfigurations
-  - Missing security headers
-  - Weak password policies
-
-  **Best Practices:**
-  - Principle of least privilege violations
-  - Missing rate limiting
-  - Inadequate logging of security events
-  - Unencrypted sensitive data transmission
-  - Missing input length/size limits
-
-  **Analysis Target:**
-  $ARGUMENTS
-
-  **Output Format:**
-  1. Executive Summary (severity: critical/high/medium/low)
-  2. Detailed findings with:
-     - File path and line numbers
-     - Vulnerability type (OWASP category)
-     - Proof of concept/exploit scenario
-     - Remediation code snippet
-  3. Risk assessment and prioritization
-
-  If no target specified, analyze the current staged changes (git diff --staged).
-  Be thorough but concise. Flag false positives as "Needs Review".

package/scripts/templates/commands/test.yml

@@ -1,50 +0,0 @@
-# Test Generation Command
-# Generates comprehensive test cases for code
-# Usage: /test [file-or-function]
-
-name: test
-description: Generate comprehensive test cases
-usage: /test [file-or-function]
-aliases: [tests, spec]
-prompt: |
-  Generate comprehensive test cases for the specified code. Cover:
-
-  **Test Types:**
-  - Unit tests (isolated function/class behavior)
-  - Integration tests (component interaction)
-  - Edge cases and boundary conditions
-  - Error handling and exceptions
-  - Async/concurrent behavior (if applicable)
-
-  **Coverage Areas:**
-  - Happy path (normal expected inputs)
-  - Invalid inputs (type errors, null/undefined, empty values)
-  - Boundary values (min/max, empty collections, single item)
-  - Error conditions (network failures, timeouts, rejected promises)
-  - State transitions (if stateful)
-  - Side effects (file I/O, database, external APIs)
-
-  **Test Quality:**
-  - Arrange-Act-Assert pattern
-  - Clear test names describing behavior
-  - Minimal mocking (use real objects when possible)
-  - One assertion per test (where logical)
-  - Setup/teardown for resource cleanup
-
-  **Target:**
-  $ARGUMENTS
-
-  **Output:**
-  1. Test file structure (describe/it blocks or equivalent)
-  2. Test cases with:
-     - Descriptive test name
-     - Setup code (arrange)
-     - Invocation (act)
-     - Assertions (assert)
-     - Mock/stub setup if needed
-  3. Coverage estimate (% of code paths tested)
-  4. Missing test scenarios (if any)
-
-  Use the project's testing framework (detect from package.json/imports).
-  If no target specified, analyze the most recently modified files.
-  Prioritize high-value tests over exhaustive coverage.