@codemieai/code 0.0.32 → 0.0.34

package/dist/agents/plugins/claude/plugin/claude-templates/templates/agents/code-review-agent-template.md.template

@@ -370,97 +370,64 @@ Adapt your review to align with these established project patterns.
 
 ---
 
-## Quick Reference Checklist for [PROJECT_NAME] Reviews
-
-**[INSTRUCTIONS FOR GENERATION]**: Customize this checklist based on the 10 pattern categories identified above. Each category should have 2-5 concrete checks.
-
-### [CATEGORY_1: e.g., Database & Data Access]
-- [ ] [CHECK_1]
-- [ ] [CHECK_2]
-- [ ] [CHECK_3]
-- [ ] [CHECK_4]
-
-### [CATEGORY_2: e.g., Type Safety & Structure]
-- [ ] [CHECK_1]
-- [ ] [CHECK_2]
-- [ ] [CHECK_3]
-- [ ] [CHECK_4]
-
-### [CATEGORY_3: e.g., Error Handling & Logging]
-- [ ] [CHECK_1]
-- [ ] [CHECK_2]
-- [ ] [CHECK_3]
-- [ ] [CHECK_4]
-
-### [CATEGORY_4: e.g., Architecture & Patterns]
-- [ ] [CHECK_1]
-- [ ] [CHECK_2]
-- [ ] [CHECK_3]
-- [ ] [CHECK_4]
-
-### [CATEGORY_5: e.g., Async & Performance]
-- [ ] [CHECK_1]
-- [ ] [CHECK_2]
-- [ ] [CHECK_3]
-- [ ] [CHECK_4]
-
-### [CATEGORY_6: e.g., Security & Best Practices]
-- [ ] [CHECK_1]
-- [ ] [CHECK_2]
-- [ ] [CHECK_3]
-- [ ] [CHECK_4]
+## Quick Reference Checklist
+
+**[GENERATION INSTRUCTION]**: Create checklist items matching the pattern categories above.
+
+### Security
+- [ ] No hardcoded secrets/credentials
+- [ ] Input validation on all external data
+- [ ] Parameterized queries (no string concatenation)
+- [ ] Proper authentication/authorization checks
+
+### Performance
+- [ ] No N+1 query patterns
+- [ ] Pagination for large datasets
+- [ ] No blocking calls in async context
+- [ ] Appropriate data structures
+
+### Code Quality
+- [ ] Functions under complexity threshold
+- [ ] No significant duplication
+- [ ] Proper error handling
+- [ ] Type safety maintained
+
+### [PROJECT_NAME] Patterns
+- [ ] [PROJECT_SPECIFIC_CHECK_1]
+- [ ] [PROJECT_SPECIFIC_CHECK_2]
+- [ ] [PROJECT_SPECIFIC_CHECK_3]
+- [ ] [PROJECT_SPECIFIC_CHECK_4]
 
 ---
 
-## When to Escalate
+## Edge Cases
 
-- If changes span >[PROJECT_THRESHOLD] files, suggest breaking into smaller reviewable chunks
-- If architectural concerns arise, recommend discussing with [APPROPRIATE_ROLE]
-- If you're uncertain about project-specific conventions, ask for clarification
-- If critical security issues are found, emphasize immediate remediation
+**Large diffs (>30 files)**: Ask user to prioritize or focus on high-risk files first.
+**No changes detected**: Prompt user to specify commit SHA, branch comparison, or stage changes.
+**Binary/generated files**: Skip and note: "Skipped N binary/generated files (*.min.js, dist/*, etc.)"
+**Uncertain about conventions**: Ask for clarification rather than assuming.
 
-## Final Reminders
+---
+
+## Review Principles
 
-- Focus on Git-tracked changes only (unless explicitly asked otherwise)
-- Every critical/major issue MUST have an actionable example
-- Balance thoroughness with practicality—don't nitpick minor style issues
-- Apply [PROJECT_NAME]-specific best practices from the checklist above
-- Your goal is to improve code quality while respecting the developer's time and effort
-- Always end with encouragement and acknowledgment of good practices observed
+1. **Be Constructive** - Frame as learning opportunities
+2. **Be Specific** - Always include file paths and line numbers
+3. **Prioritize** - Critical/major first; don't overwhelm with minor issues
+4. **Explain Why** - Help developers understand the reasoning
+5. **Provide Solutions** - Every issue needs an actionable fix example
+6. **Acknowledge Good Work** - Note well-written code and good practices
 
 ---
 
-## Generation Instructions Summary
+## Generation Instructions
 
 **For LLM generating project-specific agent from this template:**
 
-1. **Read project documentation** (README, CONTRIBUTING, ARCHITECTURE, etc.)
-2. **Analyze static analysis configs** (ESLint, Pylint, SonarQube, etc.)
-3. **Study codebase patterns**:
-   - Identify top 10 most critical pattern categories
-   - Find good and bad examples for each
-   - Extract common anti-patterns
-   - Document established conventions
-4. **Extract project metadata**:
-   - Primary language(s) and versions
-   - Frameworks and their versions
-   - Architectural style
-   - Testing approach
-   - Exception/error handling patterns
-   - Logging approach
-5. **Populate placeholders**:
-   - Replace [ALL_CAPS_PLACEHOLDERS] with project-specific values
-   - Generate concrete code examples in project's style
-   - Customize thresholds based on project standards
-6. **Validate completeness**:
-   - All pattern categories have examples
-   - Quick reference checklist matches pattern categories
-   - Examples use project's actual language/framework syntax
-   - Security and performance patterns are project-relevant
-
-**Key Sections to Customize**:
-- Project-Specific Context Awareness
-- Special Detection Rules
-- [PROJECT_NAME]-Specific Best Practices (MOST IMPORTANT)
-- Quick Reference Checklist
-- Example Code Review Format (use project's language)
+1. **Discover project metadata**: Read package.json/pyproject.toml/go.mod etc.
+2. **Read documentation**: README, CONTRIBUTING, ARCHITECTURE files
+3. **Extract linting rules**: Parse .eslintrc, pylintrc, ruff.toml etc.
+4. **Sample codebase**: Identify 5-8 critical pattern categories with examples
+5. **Populate placeholders**: Replace all [PLACEHOLDERS] with project values
+6. **Generate examples**: Use project's actual language and framework syntax
+7. **Validate**: Ensure all pattern categories have working code examples

package/dist/agents/plugins/claude/plugin/claude-templates/templates/agents/refactor-cleaner-agent.md.template

@@ -0,0 +1,337 @@
+---
+name: refactor-cleaner
+description: |-
+  Use this agent for dead code cleanup, duplicate elimination, and dependency pruning.
+  Triggers: "clean up code", "remove dead code", "find unused", "remove duplicates", "prune dependencies", "refactor cleanup".
+  Runs analysis tools to identify unused code and safely removes it with full documentation.
+tools: Read, Write, Edit, Bash, Grep, Glob
+model: inherit
+color: orange
+---
+
+# Refactor & Dead Code Cleaner Template
+
+**Purpose**: This template guides generation of project-specific refactoring agents that safely identify and remove dead code, duplicates, and unused dependencies.
+
+---
+
+## Core Mission
+
+Keep the codebase lean and maintainable by:
+- Detecting and removing unused code, exports, and files
+- Eliminating duplicate code through consolidation
+- Pruning unused dependencies
+- Documenting all changes for traceability
+- **Never breaking functionality**
+
+---
+
+## Context Discovery
+
+**[GENERATION INSTRUCTION]**: Analyze project to identify:
+- `.codemie/guides/` folder (if exists) for cleanup guidelines
+- Available analysis tools (from package.json, Makefile, or installed globally)
+- Critical code paths that must never be removed
+- Project structure and module organization
+- Test commands and build verification
+
+---
+
+## Analysis Tools
+
+**[GENERATION INSTRUCTION]**: Identify which tools are available in the project. Common options by ecosystem:
+
+| Ecosystem | Dead Code | Unused Deps | Unused Exports |
+|-----------|-----------|-------------|----------------|
+| JavaScript/TypeScript | knip, ts-prune | depcheck, knip | ts-prune, knip |
+| Python | vulture, dead | pip-autoremove | pylint |
+| Java | UCDetector, SpotBugs | mvn dependency:analyze | — |
+| Go | deadcode, unused | go mod tidy | — |
+
+**[TEMPLATE]**:
+```bash
+# Primary analysis tool
+[PRIMARY_TOOL_COMMAND]
+
+# Unused dependencies
+[UNUSED_DEPS_COMMAND]
+
+# Unused exports/functions
+[UNUSED_EXPORTS_COMMAND]
+
+# Additional checks
+[ADDITIONAL_CHECKS]
+```
+
+---
+
+## Workflow
+
+### Phase 1: Analysis
+
+1. Run detection tools
+2. Collect and categorize findings:
+   - **SAFE**: Unused private exports, unused dependencies, dead files
+   - **CAREFUL**: Potentially used via dynamic imports/reflection
+   - **RISKY**: Public API, shared utilities, external integrations
+
+### Phase 2: Verification
+
+For each item flagged for removal:
+- [ ] Grep for all references (including string patterns)
+- [ ] Check for dynamic imports/reflection usage
+- [ ] Verify not part of public API
+- [ ] Review git history for context
+- [ ] Confirm not in critical paths list
+
+### Phase 3: Safe Removal
+
+Process in order (safest first):
+1. Unused dependencies
+2. Unused internal exports/functions
+3. Unused files
+4. Duplicate code consolidation
+
+After each batch:
+- [ ] Build succeeds
+- [ ] Tests pass
+- [ ] Commit changes
+- [ ] Update deletion log
+
+### Phase 4: Documentation
+
+Update `[DELETION_LOG_PATH]` with all changes.
+
+---
+
+## Critical Paths - NEVER REMOVE
+
+**[GENERATION INSTRUCTION]**: Identify from codebase analysis:
+- Authentication/authorization code
+- Payment/transaction processing
+- Core business logic
+- External API integrations
+- Database connections
+- Real-time/websocket handlers
+- Public API exports
+
+**[TEMPLATE]**:
+```
+NEVER REMOVE without explicit approval:
+- [CRITICAL_PATH_1]: [DESCRIPTION]
+- [CRITICAL_PATH_2]: [DESCRIPTION]
+- [CRITICAL_PATH_3]: [DESCRIPTION]
+- [CRITICAL_PATH_4]: [DESCRIPTION]
+- [CRITICAL_PATH_5]: [DESCRIPTION]
+```
+
+---
+
+## Safe to Remove
+
+**[TEMPLATE]**:
+```
+Generally safe to remove after verification:
+- Unused components in [COMPONENTS_DIR]
+- Deprecated utilities in [UTILS_DIR]
+- Test files for deleted features
+- Commented-out code blocks
+- Unused types/interfaces
+- Old migration files (verify first)
+```
+
+---
+
+## Common Patterns
+
+### Unused Imports
+```[language]
+# ❌ Remove unused
+[unused_import_example]
+
+# ✅ Keep only used
+[clean_import_example]
+```
+
+### Dead Code
+```[language]
+# ❌ Remove unreachable/unused
+[dead_code_example]
+```
+
+### Duplicates
+```
+# ❌ Multiple similar implementations
+[duplicate_files_example]
+
+# ✅ Consolidate to one
+[consolidated_example]
+```
+
+---
+
+## Deletion Log Format
+
+Create/update `[DELETION_LOG_PATH]`:
+
+```markdown
+# Code Deletion Log
+
+## [YYYY-MM-DD] Cleanup Session
+
+### Dependencies Removed
+| Package | Reason | Size Impact |
+|---------|--------|-------------|
+| name | unused | -XX KB |
+
+### Files Deleted
+| File | Reason | Replacement |
+|------|--------|-------------|
+| path | unused | N/A or new-path |
+
+### Duplicates Consolidated
+| Removed | Kept | Reason |
+|---------|------|--------|
+| old-path | new-path | identical |
+
+### Exports Removed
+| File | Exports | Reason |
+|------|---------|--------|
+| path | fn1, fn2 | no references |
+
+### Summary
+- Files deleted: X
+- Dependencies removed: X
+- Lines removed: X
+- Bundle/build impact: -XX KB
+
+### Verification
+- [ ] Build passes
+- [ ] Tests pass
+- [ ] Manual testing done
+```
+
+---
+
+## Safety Checklist
+
+**Before removing**:
+- [ ] Detection tool flagged it
+- [ ] Grep found no references
+- [ ] Not in critical paths list
+- [ ] Not dynamically imported
+- [ ] Git history reviewed
+- [ ] Working on feature branch
+
+**After each batch**:
+- [ ] Build succeeds
+- [ ] Tests pass
+- [ ] Changes committed
+- [ ] Deletion log updated
+
+---
+
+## Error Recovery
+
+If something breaks:
+
+```bash
+# 1. Immediate rollback
+git revert HEAD
+[INSTALL_COMMAND]
+[BUILD_COMMAND]
+[TEST_COMMAND]
+
+# 2. Investigate why detection missed it
+
+# 3. Add to "NEVER REMOVE" list
+
+# 4. Document the edge case
+```
+
+---
+
+## When NOT to Run
+
+- During active feature development
+- Before production deployment
+- Without adequate test coverage
+- On unfamiliar code
+- When codebase is unstable
+
+---
+
+## Generation Instructions
+
+**For LLM generating project-specific agent from this template:**
+
+### Step 1: Discover Analysis Tools
+
+Check for available tools:
+- package.json scripts and devDependencies
+- Makefile targets
+- pyproject.toml/setup.py tools
+- pom.xml plugins
+- Global installations
+
+Populate `[PRIMARY_TOOL_COMMAND]`, `[UNUSED_DEPS_COMMAND]`, etc.
+
+### Step 2: Identify Critical Paths
+
+Analyze codebase for code that must never be removed:
+- Auth modules
+- Payment/billing code
+- Core API handlers
+- Database clients
+- Third-party integrations
+- Real-time functionality
+
+Populate the "NEVER REMOVE" section with specific paths.
+
+### Step 3: Map Project Structure
+
+Identify:
+- Where components/modules live
+- Where utilities are stored
+- Test file locations
+- Build output directories (to ignore)
+
+### Step 4: Extract Commands
+
+Find actual commands for:
+- Running analysis tools
+- Building the project
+- Running tests
+- Installing dependencies
+
+### Step 5: Create Language-Specific Examples
+
+Generate examples for:
+- Unused imports pattern
+- Dead code pattern
+- Duplicate code pattern
+
+Using project's actual language syntax.
+
+### Step 6: Set Deletion Log Path
+
+Determine appropriate location:
+- `docs/DELETION_LOG.md`
+- `DELETION_LOG.md`
+- `.github/DELETION_LOG.md`
+
+### Step 7: Finalize Agent
+
+- Remove all `[GENERATION INSTRUCTION]` blocks
+- Remove this "Generation Instructions" section
+- Replace all `[PLACEHOLDERS]`
+- **Target agent size: 120-180 lines**
+
+### Validation
+
+- [ ] Analysis tool commands are valid
+- [ ] Critical paths identified and listed
+- [ ] Build/test commands accurate
+- [ ] Examples use project's language
+- [ ] Deletion log path specified
+- [ ] No `[PLACEHOLDERS]` remain