codymaster 4.5.4 → 4.8.0

package/skills/cm-frappe-agent/commands/frappe-backend.md

@@ -1,162 +0,0 @@
----
-description: Invoke the Frappe backend agent for server-side Python development including controllers, APIs, database operations, and background jobs
-allowed-tools: Bash, Read, Write, Edit, Glob, Grep, Task, TodoWrite
-argument-hint: <task_description>
----
-
-# Frappe Backend Development
-
-You are invoking the specialized Frappe backend agent for server-side Python development.
-
-## Request
-
-$ARGUMENTS
-
-## Agent Invocation
-
-Use the Task tool to spawn the `frappe-fullstack:frappe-backend` agent with the following configuration:
-
-**IMPORTANT:** The agent name MUST be fully qualified: `frappe-fullstack:frappe-backend`
-
-### Agent Prompt Template
-
-```
-You are working on a Frappe/ERPNext backend task.
-
-## Task
-{user's task description}
-
-## Context
-- Working directory: {current directory}
-- Site: {detect from sites/currentsite.txt if available}
-
-## Your Responsibilities
-
-1. **Analyze the Request**
-   - Understand what backend functionality is needed
-   - Identify which DocTypes are involved
-   - Determine if this is controller logic, API, or background job
-
-2. **Explore the Codebase**
-   - Find relevant existing code patterns
-   - Check existing controllers for conventions
-   - Identify utility functions that can be reused
-
-3. **Implement the Solution**
-   - Write clean, well-documented Python code
-   - Follow Frappe coding conventions
-   - Include proper error handling
-   - Add validation where needed
-
-4. **Provide Complete Code**
-   - Controller methods with lifecycle hooks
-   - Whitelisted APIs with proper decorators
-   - Database queries using frappe.db API
-   - Background jobs if long-running operations
-
-## Output Requirements
-- Provide complete, working code
-- Include file paths for where code should go
-- Explain any configuration needed (hooks.py, etc.)
-- List commands to run (migrate, clear-cache, etc.)
-```
-
-## Capabilities
-
-The frappe-backend agent excels at:
-
-### Controller Development
-- Document lifecycle hooks (validate, before_save, on_submit, etc.)
-- Custom validation logic
-- Calculated fields and totals
-- Status management
-- Related document operations
-
-### Whitelisted APIs
-```python
-@frappe.whitelist()
-def my_api_endpoint(param1, param2):
-    # API logic
-    return result
-```
-
-### Database Operations
-```python
-# Query
-results = frappe.db.get_all("DocType", filters={}, fields=[])
-
-# Update
-frappe.db.set_value("DocType", "name", "field", "value")
-
-# Raw SQL
-frappe.db.sql("SELECT * FROM `tabDocType` WHERE condition")
-```
-
-### Background Jobs
-```python
-frappe.enqueue(
-    "myapp.tasks.heavy_task",
-    queue="long",
-    timeout=600,
-    **kwargs
-)
-```
-
-### Scheduled Tasks (hooks.py)
-```python
-scheduler_events = {
-    "daily": ["myapp.tasks.daily_task"],
-    "hourly": ["myapp.tasks.hourly_task"]
-}
-```
-
-## Common Tasks
-
-1. **"Add validation to prevent negative quantities"**
-   → Controller validate method
-
-2. **"Create API to fetch customer dashboard data"**
-   → Whitelisted method with aggregation queries
-
-3. **"Send email notification when order is approved"**
-   → on_update hook with email logic
-
-4. **"Sync data from external API daily"**
-   → Scheduled background job
-
-5. **"Calculate running totals across child table"**
-   → Controller validate with iteration
-
-## Tools Available to Agent
-
-- **Glob**: Find Python files and patterns
-- **Grep**: Search for existing implementations
-- **Read**: Read existing code for context
-- **Write**: Create new files
-- **Edit**: Modify existing code
-- **Bash**: Run bench commands, check structure
-
-## Post-Implementation
-
-After the agent completes:
-
-1. **Run Migration** (if DocType changed)
-   ```bash
-   bench --site <site> migrate
-   ```
-
-2. **Clear Cache**
-   ```bash
-   bench --site <site> clear-cache
-   ```
-
-3. **Test the Code**
-   ```bash
-   bench --site <site> console
-   # Test your functions
-   ```
-
-4. **Run Tests**
-   ```bash
-   bench --site <site> run-tests --module <module>
-   ```

package/skills/cm-frappe-agent/commands/frappe-bench.md

@@ -1,254 +0,0 @@
----
-description: Execute Frappe Bench CLI commands safely with site awareness and common operation shortcuts
-allowed-tools: Bash, Read, Grep, Glob
-argument-hint: <command> [--site <sitename>]
----
-
-# Execute Bench Command
-
-Safely execute Frappe Bench CLI commands with proper site context and validation.
-
-## Arguments
-
-Parse the user's input: $ARGUMENTS
-
-Common commands:
-- `migrate` - Run database migrations
-- `build` - Build JavaScript/CSS assets
-- `clear-cache` - Clear Redis cache
-- `console` - Open Python console
-- `start` - Start development server
-- `update` - Update apps and migrate
-- `backup` - Backup site
-- `restore` - Restore from backup
-
-## Process
-
-### Step 1: Detect Bench Directory
-
-Find the frappe-bench directory:
-```bash
-# Check if we're in a bench directory
-if [ -f "sites/apps.txt" ]; then
-    echo "Bench directory found: $(pwd)"
-else
-    # Try to find bench directory
-    find ~ -name "frappe-bench" -type d 2>/dev/null | head -3
-fi
-```
-
-### Step 2: Identify Available Sites
-
-```bash
-# List available sites
-ls sites/ | grep -v "apps.txt\|common_site_config.json\|assets"
-```
-
-### Step 3: Determine Current Site
-
-```bash
-# Check default site
-cat sites/currentsite.txt 2>/dev/null || echo "No default site set"
-```
-
-### Step 4: Execute Command
-
-Based on the requested operation:
-
-#### Migrate
-```bash
-bench --site <sitename> migrate
-```
-
-**Safety checks:**
-- Warn about uncommitted changes in apps
-- Suggest backup before migrate
-- Check for pending patches
-
-#### Build
-```bash
-# Build all apps
-bench build
-
-# Build specific app
-bench build --app <app_name>
-
-# Build with verbose output
-bench build --verbose
-
-# Production build
-bench build --production
-```
-
-#### Clear Cache
-```bash
-bench --site <sitename> clear-cache
-```
-
-#### Console
-```bash
-bench --site <sitename> console
-
-# Example usage in console:
-# >>> doc = frappe.get_doc("Customer", "CUST-001")
-# >>> frappe.db.sql("SELECT * FROM tabCustomer LIMIT 5", as_dict=True)
-```
-
-#### Start Development Server
-```bash
-bench start
-```
-
-**Note:** This will occupy the terminal. Use Ctrl+C to stop.
-
-#### Update
-```bash
-# Full update
-bench update
-
-# Update without backup
-bench update --no-backup
-
-# Update specific apps
-bench update --apps frappe,erpnext
-
-# Update without migrations
-bench update --no-migrations
-```
-
-**Safety checks:**
-- Warn about production sites
-- Suggest backup first
-- Check for uncommitted changes
-
-#### Backup
-```bash
-# Basic backup
-bench --site <sitename> backup
-
-# With files
-bench --site <sitename> backup --with-files
-```
-
-Output location: `sites/<sitename>/private/backups/`
-
-#### Restore
-```bash
-bench --site <sitename> restore <path_to_backup.sql.gz>
-
-# With files
-bench --site <sitename> restore <backup.sql.gz> \
-    --with-private-files <private.tar> \
-    --with-public-files <public.tar>
-```
-
-**Safety checks:**
-- Confirm before restore
-- Warn about data loss
-
-#### Other Common Commands
-
-```bash
-# Set admin password
-bench --site <sitename> set-admin-password <newpassword>
-
-# Add system manager
-bench --site <sitename> add-system-manager <email>
-
-# Enable/disable scheduler
-bench --site <sitename> enable-scheduler
-bench --site <sitename> disable-scheduler
-
-# Show pending jobs
-bench --site <sitename> show-pending-jobs
-
-# Doctor - check site health
-bench --site <sitename> doctor
-
-# MariaDB console
-bench --site <sitename> mariadb
-
-# Export fixtures
-bench --site <sitename> export-fixtures
-
-# Run tests
-bench --site <sitename> run-tests --app <app_name>
-```
-
-## Safety Guidelines
-
-### Destructive Commands (Require Confirmation)
-- `drop-site` - Deletes entire site
-- `reinstall` - Drops and recreates database
-- `restore` - Overwrites current data
-- `reset` - Resets to fresh install
-
-### Production Warnings
-Before running on production:
-1. Confirm site is in maintenance mode
-2. Ensure backup exists
-3. Check for active users
-
-### Command Validation
-
-For any command, check:
-1. Is the site name valid?
-2. Is the command recognized by bench?
-3. Are there any pending migrations?
-
-## Error Handling
-
-Common issues:
-
-### "Site not found"
-```bash
-# Check available sites
-ls sites/
-```
-
-### "Module not found"
-```bash
-# Rebuild environment
-bench setup env
-pip install -e apps/frappe -e apps/erpnext
-```
-
-### "Migration failed"
-```bash
-# Check error logs
-tail -100 logs/frappe.log
-
-# Skip failing patches
-bench --site <sitename> migrate --skip-failing
-```
-
-### "Build failed"
-```bash
-# Clear node modules and rebuild
-rm -rf node_modules
-yarn install
-bench build
-```
-
-## Output
-
-After command execution:
-1. Show command output
-2. Report success/failure
-3. Suggest next steps if applicable
-4. Warn about any issues detected
-
-## Quick Reference
-
-| Task | Command |
-|------|---------|
-| Start dev server | `bench start` |
-| Migrate database | `bench --site <site> migrate` |
-| Clear cache | `bench --site <site> clear-cache` |
-| Build assets | `bench build` |
-| Backup site | `bench --site <site> backup` |
-| View logs | `tail -f logs/frappe.log` |
-| Python console | `bench --site <site> console` |
-| MySQL console | `bench --site <site> mariadb` |
-| Run tests | `bench --site <site> run-tests` |
-| Check health | `bench --site <site> doctor` |

package/skills/cm-frappe-agent/commands/frappe-debug.md

@@ -1,263 +0,0 @@
----
-description: Invoke the Frappe debugger agent for troubleshooting errors, analyzing logs, debugging permissions, and investigating performance issues
-allowed-tools: Bash, Read, Grep, Glob, Task
-argument-hint: <error_or_issue_description>
----
-
-# Frappe Debug & Troubleshoot
-
-You are invoking the specialized Frappe debugger agent for investigating and resolving issues.
-
-## Request
-
-$ARGUMENTS
-
-## Agent Invocation
-
-Use the Task tool to spawn the `frappe-fullstack:frappe-debugger` agent with the following configuration:
-
-**IMPORTANT:** The agent name MUST be fully qualified: `frappe-fullstack:frappe-debugger`
-
-### Agent Prompt Template
-
-```
-You are debugging a Frappe/ERPNext issue.
-
-## Issue
-{user's error or issue description}
-
-## Context
-- Working directory: {current directory}
-- Check logs, database, permissions, cache
-
-## Your Responsibilities
-
-1. **Gather Information**
-   - Check error logs
-   - Identify the error type
-   - Find relevant stack traces
-   - Check recent changes
-
-2. **Analyze the Problem**
-   - Determine root cause
-   - Check for common issues
-   - Verify configuration
-   - Test hypotheses
-
-3. **Provide Solution**
-   - Step-by-step fix
-   - Commands to run
-   - Code changes if needed
-   - Prevention tips
-
-## Output Requirements
-- Clear diagnosis of the issue
-- Root cause explanation
-- Solution steps
-- Verification commands
-```
-
-## Capabilities
-
-The frappe-debugger agent excels at:
-
-### Log Analysis
-```bash
-# Check error logs
-tail -100 logs/frappe.log | grep -i error
-
-# Check web errors
-tail -50 logs/web.error.log
-
-# Check worker errors
-tail -50 logs/worker.error.log
-
-# Site-specific logs
-tail -100 sites/<site>/logs/frappe.log
-```
-
-### Error Types
-
-| Error | Common Causes |
-|-------|---------------|
-| `ValidationError` | Failed validation in controller |
-| `PermissionError` | Missing role or user permission |
-| `LinkValidationError` | Referenced document doesn't exist |
-| `MandatoryError` | Required field is empty |
-| `DuplicateEntryError` | Unique constraint violation |
-| `TimestampMismatchError` | Concurrent edit conflict |
-
-### Permission Debugging
-```python
-# In bench console
-frappe.session.user
-frappe.get_roles()
-frappe.has_permission("DocType", "write", "doc_name")
-```
-
-### Database Issues
-```sql
--- Check for orphaned records
-SELECT * FROM `tabChild`
-WHERE parent NOT IN (SELECT name FROM `tabParent`);
-
--- Check table sizes
-SELECT table_name, ROUND(data_length/1024/1024, 2) as MB
-FROM information_schema.tables
-WHERE table_schema = DATABASE()
-ORDER BY data_length DESC;
-```
-
-### Cache Issues
-```bash
-# Clear all cache
-bench --site <site> clear-cache
-
-# Clear Redis
-redis-cli FLUSHALL
-
-# Clear specific
-frappe.cache().delete_value("key")
-```
-
-### Background Job Issues
-```bash
-# Check pending jobs
-bench --site <site> show-pending-jobs
-
-# Check scheduler
-bench --site <site> show-scheduler-status
-
-# View failed jobs
-bench --site <site> console
->>> from rq import Queue
->>> from frappe.utils.background_jobs import get_redis_conn
->>> q = Queue("failed", connection=get_redis_conn())
->>> for job in q.jobs: print(job.exc_info)
-```
-
-## Common Issues & Solutions
-
-### 1. "Document not found"
-```bash
-# Check if document exists
-bench --site <site> console
->>> frappe.db.exists("DocType", "name")
-```
-
-### 2. "Permission denied"
-```bash
-# Check user roles and permissions
-bench --site <site> console
->>> frappe.get_roles("user@email.com")
->>> frappe.get_all("DocPerm", filters={"parent": "DocType"})
-```
-
-### 3. "Module not found"
-```bash
-# Reinstall apps
-pip install -e apps/frappe
-pip install -e apps/my_app
-```
-
-### 4. "Migration failed"
-```bash
-# Check what's failing
-bench --site <site> migrate --skip-failing
-
-# Check patches
-cat apps/my_app/my_app/patches.txt
-```
-
-### 5. "Assets not loading"
-```bash
-# Rebuild assets
-bench build --force
-
-# Check for JS errors in browser console
-# Hard refresh: Ctrl+Shift+R
-```
-
-### 6. "Slow performance"
-```bash
-# Enable slow query log
-# In site_config.json: "log_slow_queries": 1
-
-# Check slow queries
-grep "slow_query" logs/frappe.log
-```
-
-### 7. "Background job stuck"
-```bash
-# Check workers
-ps aux | grep worker
-
-# Restart workers
-sudo supervisorctl restart frappe-bench-workers:*
-```
-
-### 8. "Redis connection refused"
-```bash
-# Check Redis
-redis-cli ping
-
-# Restart Redis
-sudo systemctl restart redis
-```
-
-## Diagnostic Commands
-
-```bash
-# Site health check
-bench --site <site> doctor
-
-# Show database size
-bench --site <site> mariadb -e "
-SELECT table_name,
-       ROUND(data_length/1024/1024, 2) as data_mb
-FROM information_schema.tables
-WHERE table_schema = DATABASE()
-ORDER BY data_length DESC
-LIMIT 10"
-
-# Check scheduler status
-bench --site <site> show-scheduler-status
-
-# List installed apps
-bench --site <site> list-apps
-
-# Check versions
-bench version
-```
-
-## Debug Checklist
-
-1. [ ] Check logs: `tail -100 logs/frappe.log`
-2. [ ] Identify error type from traceback
-3. [ ] Check permissions if PermissionError
-4. [ ] Check document exists if LinkValidationError
-5. [ ] Clear cache: `bench --site <site> clear-cache`
-6. [ ] Check Redis is running
-7. [ ] Check background workers if job-related
-8. [ ] Verify recent code changes with git log
-9. [ ] Test in bench console
-10. [ ] Check browser console for JS errors
-
-## Tools Available to Agent
-
-- **Bash**: Run diagnostic commands, check logs
-- **Read**: Read log files, config files
-- **Grep**: Search logs and code for errors
-- **Glob**: Find relevant files
-
-**Note**: Debug agent has read-only focus to investigate without making changes. Solutions are provided for user to implement.
-
-## Output Format
-
-The debugger will provide:
-
-1. **Diagnosis**: What's wrong and why
-2. **Root Cause**: The underlying issue
-3. **Solution**: Step-by-step fix
-4. **Verification**: How to confirm it's fixed
-5. **Prevention**: How to avoid in future