oh-my-customcode 0.12.1 → 0.12.3

package/templates/.codex/skills/npm-audit/SKILL.md

@@ -1,72 +0,0 @@
----
-name: npm-audit
-description: Audit npm dependencies for security and updates
-argument-hint: "[--fix] [--production]"
----
-
-# NPM Audit Skill
-
-Audit npm dependencies for security vulnerabilities and outdated packages.
-
-## Options
-
-```
---fix            Automatically fix vulnerabilities where possible
---production     Only audit production dependencies
---json           Output in JSON format
-```
-
-## Workflow
-
-```
-1. Run npm audit for security vulnerabilities
-2. Analyze vulnerability severity
-3. Check for outdated dependencies
-4. Generate health report
-5. Suggest remediation steps
-```
-
-## Output Format
-
-### Success
-```
-[NPM Audit] package-name
-
-Security:
-  Critical: 0
-  High: 0
-  Moderate: 2
-  Low: 1
-
-Outdated:
-  Major updates: 3
-  Minor updates: 5
-  Patch updates: 12
-
-Status: Needs attention (2 moderate vulnerabilities)
-
-Recommendations:
-  1. npm update lodash
-  2. npm update axios
-```
-
-### Failure
-```
-[NPM Audit] Failed
-
-Error: {error_message}
-Hint: Ensure package-lock.json exists
-```
-
-## Examples
-
-```bash
-# Full dependency audit with report
-npm-audit
-
-# Audit and fix vulnerabilities
-npm-audit --fix
-
-# Audit only production dependencies
-npm-audit --production
-```

package/templates/.codex/skills/npm-publish/SKILL.md

@@ -1,63 +0,0 @@
----
-name: npm-publish
-description: Publish package to npm registry with pre-checks
-argument-hint: "[--tag <tag>] [--dry-run]"
-disable-model-invocation: true
----
-
-# NPM Publish Skill
-
-Publish package to npm registry with comprehensive pre-publish checks and validation.
-
-## Options
-
-```
---tag            npm dist-tag (default: latest)
---dry-run        Run all checks without publishing
---skip-tests     Skip test execution
-```
-
-## Workflow
-
-```
-1. Validate package.json configuration
-2. Check version against registry
-3. Run pre-publish checks (tests, lint, build)
-4. Execute npm pack (dry-run)
-5. Publish with appropriate tag
-6. Verify publication success
-```
-
-## Output Format
-
-### Success
-```
-[NPM Publish] package-name@1.2.3
-
-Pre-checks: All passed
-Registry: https://registry.npmjs.org
-Tag: latest
-
-Package published successfully.
-```
-
-### Failure
-```
-[NPM Publish] Failed
-
-Error: {error_message}
-Suggested fix: {fix_suggestion}
-```
-
-## Examples
-
-```bash
-# Publish to npm with all checks
-npm-publish
-
-# Publish to beta tag
-npm-publish --tag beta
-
-# Validate without publishing
-npm-publish --dry-run
-```

package/templates/.codex/skills/npm-version/SKILL.md

@@ -1,75 +0,0 @@
----
-name: npm-version
-description: Manage semantic versions for npm packages
-argument-hint: "<major|minor|patch> [--no-tag] [--no-commit]"
-disable-model-invocation: true
----
-
-# NPM Version Management Skill
-
-Manage semantic versions for npm packages with automatic changelog and git integration.
-
-## Arguments
-
-```
-major            Bump major version (x.0.0)
-minor            Bump minor version (0.x.0)
-patch            Bump patch version (0.0.x)
-```
-
-## Options
-
-```
---no-tag         Skip git tag creation
---no-commit      Skip commit creation (only update files)
-```
-
-## Workflow
-
-```
-1. Analyze current version from package.json
-2. Determine version bump type
-3. Update package.json version field
-4. Update CHANGELOG.md if exists
-5. Create version commit
-6. Create git tag (optional)
-```
-
-## Output Format
-
-### Success
-```
-[NPM Version] package-name
-
-Previous: 1.2.3
-Current:  1.2.4
-
-Changes:
-  - package.json updated
-  - Commit: "chore: bump version to 1.2.4"
-  - Tag: v1.2.4
-```
-
-### Failure
-```
-[NPM Version] Failed
-
-Error: {error_message}
-Hint: Ensure clean git working directory
-```
-
-## Examples
-
-```bash
-# Bump patch version (1.2.3 -> 1.2.4)
-npm-version patch
-
-# Bump minor version (1.2.3 -> 1.3.0)
-npm-version minor
-
-# Bump major version (1.2.3 -> 2.0.0)
-npm-version major
-
-# Update version without creating git tag
-npm-version patch --no-tag
-```

package/templates/.codex/skills/optimize-analyze/SKILL.md

@@ -1,55 +0,0 @@
----
-name: optimize-analyze
-description: Analyze bundle size and performance metrics
-argument-hint: "[target] [--verbose]"
----
-
-# Bundle Analysis Skill
-
-Analyze bundle size and performance metrics for web applications.
-
-## Arguments
-
-```
-target           Build output path or project root (optional, auto-detects)
-```
-
-## Options
-
-```
---verbose, -v    Show detailed analysis
-```
-
-## Workflow
-
-```
-1. Identify build tool (webpack, vite, rollup, esbuild)
-2. Locate build output
-3. Analyze bundle composition
-4. Calculate size metrics
-5. Identify large dependencies
-6. Detect unused code/exports
-7. Generate analysis report
-```
-
-## Output
-
-- Total bundle size
-- Size breakdown by chunk/module
-- Top dependencies by size
-- Tree-shaking status
-- Dead code detection
-- Optimization recommendations
-
-## Examples
-
-```bash
-# Analyze current project
-optimize-analyze
-
-# Analyze specific output directory
-optimize-analyze ./dist
-
-# Verbose analysis
-optimize-analyze --verbose
-```

package/templates/.codex/skills/optimize-bundle/SKILL.md

@@ -1,67 +0,0 @@
----
-name: optimize-bundle
-description: Apply bundle size optimizations
-argument-hint: "[--dry-run] [--safe]"
-disable-model-invocation: true
----
-
-# Bundle Optimization Skill
-
-Apply bundle size optimizations to reduce build output and improve performance.
-
-## Options
-
-```
---dry-run        Show what would be changed without applying
---safe           Only apply safe, reversible optimizations
-```
-
-## Workflow
-
-```
-1. Run full bundle analysis
-2. Identify optimization opportunities
-3. Prioritize by impact and risk
-4. Apply recommended changes (or show dry-run)
-5. Rebuild if changes applied
-6. Verify improvements
-7. Report before/after metrics
-```
-
-## Optimization Levels
-
-### Safe
-- Configure code splitting
-- Enable tree-shaking for ESM
-- Add terser/minification
-- Configure chunk optimization
-
-### Moderate
-- Replace heavy dependencies with lighter alternatives
-- Add dynamic imports for routes
-- Configure asset optimization
-
-### Aggressive
-- Remove unused dependencies
-- Inline small modules
-- Configure aggressive minification
-
-## Output
-
-- Applied changes list
-- Before/after size comparison
-- Build time comparison
-- Risk assessment for each change
-
-## Examples
-
-```bash
-# Apply all safe optimizations
-optimize-bundle
-
-# Preview changes without applying
-optimize-bundle --dry-run
-
-# Only apply safe optimizations
-optimize-bundle --safe
-```

package/templates/.codex/skills/optimize-report/SKILL.md

@@ -1,74 +0,0 @@
----
-name: optimize-report
-description: Generate comprehensive optimization report
-argument-hint: "[--baseline <file>] [--format <format>]"
----
-
-# Optimization Report Skill
-
-Generate comprehensive optimization report with analysis, metrics, and recommendations.
-
-## Options
-
-```
---baseline       Compare against previous report
---format         Output format (text, json, markdown)
-                 Default: text
-```
-
-## Workflow
-
-```
-1. Run full analysis
-2. Collect all metrics
-3. Compare against baseline (if provided)
-4. Calculate performance scores
-5. Generate recommendations
-6. Format report
-```
-
-## Report Sections
-
-### Bundle Analysis
-- Total size (raw and gzipped)
-- Chunk breakdown
-- Dependency tree
-
-### Performance Metrics
-- Estimated load times
-- Core Web Vitals impact
-- Build performance
-
-### Code Quality
-- Tree-shaking effectiveness
-- Dead code percentage
-- Duplicate code detection
-
-### Recommendations
-- High impact optimizations
-- Quick wins
-- Long-term improvements
-
-### Comparison (if baseline)
-- Size delta
-- Performance delta
-- Trend analysis
-
-## Output
-
-- Formatted report in requested format
-- Performance grade (A-F)
-- Priority action items
-
-## Examples
-
-```bash
-# Generate current report
-optimize-report
-
-# Compare against previous report
-optimize-report --baseline ./previous-report.json
-
-# Generate markdown report
-optimize-report --format markdown
-```

package/templates/.codex/skills/pipeline-architecture-patterns/SKILL.md

@@ -1,83 +0,0 @@
----
-name: pipeline-architecture-patterns
-description: Data pipeline architecture patterns for ETL/ELT design, orchestration, and data quality frameworks
-user-invocable: false
----
-
-# Data Pipeline Architecture Patterns
-
-## Pipeline Architectures
-
-### ETL vs ELT (CRITICAL)
-- **ETL**: Extract → Transform (staging) → Load
-  - Traditional, on-premise data warehouses
-  - Pre-aggregation, complex transformations
-- **ELT**: Extract → Load (raw) → Transform (in warehouse)
-  - Cloud warehouses (Snowflake, BigQuery)
-  - Leverage warehouse compute power
-
-### Lambda Architecture
-- Batch layer: historical data processing
-- Speed layer: real-time stream processing
-- Serving layer: merge batch + real-time views
-- Complexity: maintain two codebases
-
-### Kappa Architecture
-- Stream-only processing
-- Single codebase for batch + real-time
-- Reprocessing via replay
-- Simpler than Lambda
-
-### Medallion Architecture
-- **Bronze**: Raw data (append-only)
-- **Silver**: Cleaned, conformed data
-- **Gold**: Business-level aggregations
-- Databricks pattern
-
-## Orchestration Patterns
-
-### DAG-Based Orchestration
-- Airflow, Prefect, Dagster
-- Task dependencies as DAG
-- Retries, backfills, scheduling
-
-### Event-Driven Orchestration
-- Kafka, Pub/Sub triggers
-- Real-time, low-latency
-- Decoupled producers/consumers
-
-### Hybrid Orchestration
-- Scheduled batch + event-driven streams
-- Example: Airflow DAG triggered by Kafka event
-
-## Data Quality Frameworks
-
-### Data Contracts (CRITICAL)
-- Define schema, freshness, volume expectations
-- Producer-consumer agreement
-- Break build on violation
-
-### Validation Frameworks
-- **Great Expectations**: Python-based expectations
-- **dbt tests**: SQL-based tests
-- **Soda**: YAML-based checks
-
-### Data Lineage
-- Track data origin and transformations
-- Debug data quality issues
-- Compliance and auditing
-
-## Idempotency Patterns
-
-### Idempotent Design (CRITICAL)
-- Same input → same output (no side effects)
-- Upserts instead of inserts
-- Partition replacement instead of append
-
-### Deduplication
-- Use unique keys
-- Window-based deduplication
-- Consumer group offset management
-
-## References
-- [Data Engineering Design Patterns](https://www.oreilly.com/library/view/data-engineering-design/9781098130725/)

package/templates/.codex/skills/postgres-best-practices/SKILL.md

@@ -1,66 +0,0 @@
----
-name: postgres-best-practices
-description: PostgreSQL best practices for database design, query optimization, and performance tuning
-user-invocable: false
----
-
-# PostgreSQL Best Practices
-
-## Query Optimization
-
-### EXPLAIN ANALYZE (CRITICAL)
-- Use `EXPLAIN ANALYZE` to understand query plans
-- Identify slow operations: Seq Scan, Nested Loop
-- Check row estimates vs actual rows
-- Monitor buffers: shared hit vs read
-
-### Indexing (CRITICAL)
-- B-tree: default, most use cases
-- GIN: JSONB, arrays, full-text search
-- GiST: geometry, range types
-- BRIN: large sequential tables (time-series)
-- Partial indexes: filtered queries
-- Covering indexes (INCLUDE): avoid heap fetches
-
-### Index Maintenance
-- Create indexes concurrently: `CREATE INDEX CONCURRENTLY`
-- Monitor usage: `pg_stat_user_indexes`
-- Remove unused indexes
-- Reindex bloated indexes
-
-## Table Design
-
-### Partitioning (HIGH)
-- Range partitioning: time-series data
-- List partitioning: categorical data
-- Hash partitioning: even distribution
-- Declarative partitioning (PG 10+)
-
-### Data Types
-- Use appropriate types (int vs bigint, varchar vs text)
-- JSONB for semi-structured data
-- Arrays for multi-value columns
-- UUIDs for distributed IDs
-
-## Performance Tuning
-
-### Vacuum and Autovacuum
-- Autovacuum: default enabled
-- Monitor bloat: `pg_stat_user_tables`
-- Tune autovacuum thresholds
-- Manual VACUUM for large updates
-
-### Connection Pooling
-- Use pgBouncer or PgPool
-- Transaction pooling for short transactions
-- Session pooling for long transactions
-- Max connections: tune based on workload
-
-### Configuration
-- `shared_buffers`: 25% of RAM
-- `work_mem`: per operation, tune carefully
-- `effective_cache_size`: 50-75% of RAM
-- `random_page_cost`: 1.1 for SSD
-
-## References
-- [PostgreSQL Performance Optimization](https://wiki.postgresql.org/wiki/Performance_Optimization)