oh-my-customcode 0.12.0 → 0.12.2

package/templates/.codex/skills/de-lead-routing/SKILL.md

@@ -1,243 +0,0 @@
----
-name: de-lead-routing
-description: Routes data engineering tasks to the correct DE expert agent. Use when user requests data pipeline design, DAG authoring, SQL modeling, stream processing, or warehouse optimization.
-user-invocable: false
----
-
-# DE Lead Routing Skill
-
-## Purpose
-
-Routes data engineering tasks to appropriate DE expert agents. This skill contains the coordination logic for orchestrating data engineering agents across orchestration, modeling, processing, streaming, and warehouse specializations.
-
-## Engineers Under Management
-
-| Type | Agents | Purpose |
-|------|--------|---------|
-| de/orchestration | de-airflow-expert | DAG authoring, scheduling, testing |
-| de/modeling | de-dbt-expert | SQL modeling, testing, documentation |
-| de/processing | de-spark-expert | Distributed data processing |
-| de/streaming | de-kafka-expert | Event streaming, topic design |
-| de/warehouse | de-snowflake-expert | Cloud DWH, query optimization |
-| de/architecture | de-pipeline-expert | Pipeline design, cross-tool patterns |
-
-## Tool/Framework Detection
-
-### Keyword Mapping
-
-| Keyword | Agent |
-|---------|-------|
-| "airflow", "dag", "scheduling", "orchestration" | de-airflow-expert |
-| "dbt", "modeling", "sql model", "analytics engineering" | de-dbt-expert |
-| "spark", "pyspark", "distributed processing", "distributed" | de-spark-expert |
-| "kafka", "streaming", "event", "consumer", "producer" | de-kafka-expert |
-| "snowflake", "warehouse", "clustering key" | de-snowflake-expert |
-| "pipeline", "ETL", "ELT", "data quality", "lineage" | de-pipeline-expert |
-| "iceberg", "table format" | de-snowflake-expert or de-pipeline-expert |
-
-### File Pattern Mapping
-
-| Pattern | Agent |
-|---------|-------|
-| `dags/*.py`, `airflow.cfg`, `airflow_settings.yaml` | de-airflow-expert |
-| `models/**/*.sql`, `dbt_project.yml`, `schema.yml` | de-dbt-expert |
-| Spark job files, `spark-submit` configs | de-spark-expert |
-| Kafka configs, `*.properties` (Kafka), `streams/*.java` | de-kafka-expert |
-| Snowflake SQL, warehouse DDL | de-snowflake-expert |
-
-## Command Routing
-
-```
-DE Request → Detection → Expert Agent
-
-Airflow DAG → de-airflow-expert
-dbt model   → de-dbt-expert
-Spark job   → de-spark-expert
-Kafka topic → de-kafka-expert
-Snowflake   → de-snowflake-expert
-Pipeline    → de-pipeline-expert
-Multi-tool  → Multiple experts (parallel)
-```
-
-## Routing Rules
-
-### 1. Pipeline Development Workflow
-
-```
-1. Receive pipeline task request
-2. Identify tools and components:
-   - DAG orchestration → de-airflow-expert
-   - SQL transformations → de-dbt-expert
-   - Distributed processing → de-spark-expert
-   - Event streaming → de-kafka-expert
-   - Warehouse operations → de-snowflake-expert
-   - Architecture decisions → de-pipeline-expert
-3. Select appropriate experts
-4. Distribute tasks (parallel if 2+ tools)
-5. Aggregate results
-6. Present unified report
-```
-
-Example:
-```
-User: "Design a pipeline that runs dbt models from Airflow and loads into Snowflake"
-
-Detection:
-  - Airflow DAG → de-airflow-expert
-  - dbt model → de-dbt-expert
-  - Snowflake loading → de-snowflake-expert
-  - Pipeline architecture → de-pipeline-expert
-
-Route (parallel where independent):
-  Task(de-pipeline-expert → overall architecture design)
-  Task(de-airflow-expert → DAG structure)
-  Task(de-dbt-expert → model design)
-  Task(de-snowflake-expert → warehouse setup)
-
-Aggregate:
-  Pipeline architecture defined
-  Airflow DAG: 5 tasks designed
-  dbt: 12 models structured
-  Snowflake: warehouse + schema configured
-```
-
-### 2. Data Quality Workflow
-
-```
-1. Analyze data quality requirements
-2. Route to appropriate experts:
-   - dbt tests → de-dbt-expert
-   - Pipeline validation → de-pipeline-expert
-   - Source freshness → de-airflow-expert
-3. Coordinate cross-tool quality strategy
-```
-
-### 3. Multi-Tool Projects
-
-For projects spanning multiple DE tools:
-
-```
-1. Detect all DE tools in project
-2. Identify primary tool (most files/configs)
-3. Route to appropriate experts:
-   - If task spans multiple tools → parallel experts
-   - If task is tool-specific → single expert
-4. Coordinate cross-tool consistency
-```
-
-## Sub-agent Model Selection
-
-### Model Mapping by Task Type
-
-| Task Type | Recommended Model | Reason |
-|-----------|-------------------|--------|
-| Pipeline architecture | `opus` | Deep reasoning required |
-| DAG/model review | `sonnet` | Balanced quality judgment |
-| Implementation | `sonnet` | Standard code generation |
-| Quick validation | `haiku` | Fast response |
-
-### Model Mapping by Agent
-
-| Agent | Default Model | Alternative |
-|-------|---------------|-------------|
-| de-pipeline-expert | `sonnet` | `opus` for architecture |
-| de-airflow-expert | `sonnet` | `haiku` for DAG validation |
-| de-dbt-expert | `sonnet` | `haiku` for test checks |
-| de-spark-expert | `sonnet` | `opus` for optimization |
-| de-kafka-expert | `sonnet` | `opus` for topology design |
-| de-snowflake-expert | `sonnet` | `opus` for warehouse design |
-
-### Task Call Examples
-
-```
-# Complex pipeline architecture
-Task(
-  subagent_type: "general-purpose",
-  prompt: "Design end-to-end pipeline architecture following de-pipeline-expert guidelines",
-  model: "opus"
-)
-
-# Standard DAG review
-Task(
-  subagent_type: "general-purpose",
-  prompt: "Review Airflow DAGs in dags/ following de-airflow-expert guidelines",
-  model: "sonnet"
-)
-
-# Quick dbt test validation
-Task(
-  subagent_type: "Explore",
-  prompt: "Find all dbt models missing schema tests",
-  model: "haiku"
-)
-```
-
-## Parallel Execution
-
-Following R009:
-- Maximum 4 parallel instances
-- Independent tool/module operations
-- Coordinate cross-tool consistency
-
-Example:
-```
-User: "Review all DE configs"
-
-Detection:
-  - dags/ → de-airflow-expert
-  - models/ → de-dbt-expert
-  - kafka/ → de-kafka-expert
-
-Route (parallel):
-  Task(de-airflow-expert role → review dags/, model: "sonnet")
-  Task(de-dbt-expert role → review models/, model: "sonnet")
-  Task(de-kafka-expert role → review kafka/, model: "sonnet")
-```
-
-## Display Format
-
-```
-[Analyzing] Detected: Airflow, dbt, Snowflake
-
-[Delegating] de-airflow-expert:sonnet → DAG design
-[Delegating] de-dbt-expert:sonnet → Model structure
-[Delegating] de-snowflake-expert:sonnet → Warehouse config
-
-[Progress] ███████████░ 2/3 experts completed
-
-[Summary]
-  Airflow: DAG with 5 tasks designed
-  dbt: 12 models across 3 layers
-  Snowflake: Warehouse + schema configured
-
-Pipeline design completed.
-```
-
-## Integration with Other Routing Skills
-
-- **dev-lead-routing**: Hands off to DE lead when data engineering keywords detected
-- **secretary-routing**: DE agents accessible through secretary for management tasks
-- **qa-lead-routing**: Coordinates with QA for data quality testing
-
-## Agent Teams Awareness
-
-Before routing via Task tool, check if Agent Teams is available (`CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1` or TeamCreate/SendMessage tools present).
-
-**Self-check:** Does this task need 3+ agents, shared state, or inter-agent communication? If yes, prefer Agent Teams over Task tool. See R018 for the full decision matrix.
-
-| Scenario | Preferred |
-|----------|-----------|
-| Single-tool DE task | Task Tool |
-| Multi-tool pipeline design (3+ tools) | Agent Teams |
-| Cross-tool data quality analysis | Agent Teams |
-| Quick DAG/model validation | Task Tool |
-
-## Usage
-
-This skill is NOT user-invocable. It should be automatically triggered when the main conversation detects data engineering intent.
-
-Detection criteria:
-- User requests pipeline design or data engineering
-- User mentions DE tool names (Airflow, dbt, Spark, Kafka, Snowflake)
-- User provides DE-related file paths (dags/, models/, etc.)
-- User requests data quality or lineage work

package/templates/.codex/skills/dev-lead-routing/SKILL.md

@@ -1,94 +0,0 @@
----
-name: dev-lead-routing
-description: Routes development tasks to the correct language or framework expert agent. Use when user requests code review, implementation, refactoring, or debugging.
-user-invocable: false
----
-
-# Dev Lead Routing
-
-## Engineers
-
-| Type | Agents |
-|------|--------|
-| Language | lang-golang-expert, lang-python-expert, lang-rust-expert, lang-kotlin-expert, lang-typescript-expert, lang-java21-expert |
-| Frontend | fe-vercel-agent, fe-vuejs-agent, fe-svelte-agent |
-| Backend | be-fastapi-expert, be-springboot-expert, be-go-backend-expert, be-nestjs-expert, be-express-expert |
-| Tooling | tool-npm-expert, tool-optimizer, tool-bun-expert |
-| Database | db-supabase-expert, db-postgres-expert, db-redis-expert |
-| Architect | arch-documenter, arch-speckit-agent |
-| Infra | infra-docker-expert, infra-aws-expert |
-
-## File Extension Mapping
-
-| Extension | Agent |
-|-----------|-------|
-| `.go` | lang-golang-expert |
-| `.py` | lang-python-expert |
-| `.rs` | lang-rust-expert |
-| `.kt`, `.kts` | lang-kotlin-expert |
-| `.ts`, `.tsx` | lang-typescript-expert |
-| `.java` | lang-java21-expert |
-| `.js/.jsx` (React) | fe-vercel-agent |
-| `.vue` | fe-vuejs-agent |
-| `.svelte` | fe-svelte-agent |
-| `.sql` (PG) | db-postgres-expert |
-| `.sql` (Supabase) | db-supabase-expert |
-| `Dockerfile`, `*.dockerfile` | infra-docker-expert |
-| `*.tf`, `*.tfvars` | infra-aws-expert |
-| `*.yaml`, `*.yml` (CloudFormation) | infra-aws-expert |
-
-## Keyword Mapping
-
-| Keywords | Agent |
-|----------|-------|
-| go, golang | lang-golang-expert |
-| python, py | lang-python-expert |
-| rust | lang-rust-expert |
-| kotlin | lang-kotlin-expert |
-| typescript, ts | lang-typescript-expert |
-| java | lang-java21-expert |
-| react, next.js, vercel | fe-vercel-agent |
-| vue | fe-vuejs-agent |
-| svelte | fe-svelte-agent |
-| fastapi | be-fastapi-expert |
-| spring, springboot | be-springboot-expert |
-| nestjs | be-nestjs-expert |
-| express | be-express-expert |
-| npm | tool-npm-expert |
-| optimize, bundle | tool-optimizer |
-| bun | tool-bun-expert |
-| postgres, postgresql, psql, pg_stat | db-postgres-expert |
-| redis, cache, pub/sub, sorted set | db-redis-expert |
-| supabase, rls, edge function | db-supabase-expert |
-| docker, dockerfile, container, compose | infra-docker-expert |
-| aws, cloudformation, vpc, iam, s3, lambda, cdk, terraform | infra-aws-expert |
-| architecture, adr, openapi, swagger, diagram | arch-documenter |
-| spec, specification, tdd, requirements | arch-speckit-agent |
-
-## Model Selection
-
-| Task | Model |
-|------|-------|
-| Architecture analysis | opus |
-| Code review/implementation | sonnet |
-| Quick validation/search | haiku |
-
-## Routing Rules
-
-Multi-language: detect all languages, route to parallel experts (max 4). Single-language: route to matching expert. Cross-layer (frontend + backend): multiple experts in parallel.
-
-## Agent Teams Awareness
-
-Before routing via Task tool, check if Agent Teams is available (`CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1` or TeamCreate/SendMessage tools present).
-
-**Self-check:** Does this task need 3+ agents, shared state, or inter-agent communication? If yes, prefer Agent Teams over Task tool. See R018 for the full decision matrix.
-
-| Scenario | Preferred |
-|----------|-----------|
-| Single-language review | Task Tool |
-| Multi-language code review (3+) | Agent Teams |
-| Code review + fix cycle | Agent Teams |
-| Cross-layer debugging (FE + BE + DB) | Agent Teams |
-| Simple file search/validation | Task Tool |
-
-Not user-invocable. Auto-triggered on development intent.

package/templates/.codex/skills/dev-refactor/SKILL.md

@@ -1,123 +0,0 @@
----
-name: dev-refactor
-description: Refactor code for better structure and patterns
-argument-hint: "<file-or-directory> [--lang <language>]"
----
-
-# Code Refactoring Skill
-
-Refactor code for better structure, naming, and patterns using language-specific expert agents.
-
-## Parameters
-
-| Name | Type | Required | Description |
-|------|------|----------|-------------|
-| path | string | yes | File or directory to refactor |
-
-## Options
-
-```
---lang, -l       Language (auto-detected if not specified)
-                 Values: go, python, rust, kotlin, typescript, java
---focus, -f      Focus area (structure, naming, patterns, all)
---dry-run        Show proposed changes without applying
---verbose, -v    Detailed output
-```
-
-## Workflow
-
-```
-1. Detect language (or use --lang)
-2. Select appropriate expert agent
-3. Load language-specific skill
-4. Analyze code structure
-5. Propose refactoring changes
-6. Apply changes (if not --dry-run)
-```
-
-## Agent Selection
-
-| File Extension | Agent | Skill |
-|----------------|-------|-------|
-| .go | lang-golang-expert | go-best-practices |
-| .py | lang-python-expert | python-best-practices |
-| .rs | lang-rust-expert | rust-best-practices |
-| .kt | lang-kotlin-expert | kotlin-best-practices |
-| .ts, .tsx | lang-typescript-expert | typescript-best-practices |
-| .java | be-springboot-expert | springboot-best-practices |
-| .jsx, .js (React) | fe-vercel-agent | react-best-practices |
-
-## Refactoring Categories
-
-| Category | Description |
-|----------|-------------|
-| structure | File/module organization, package structure |
-| naming | Variable, function, type naming conventions |
-| patterns | Design patterns, idiomatic code |
-| duplication | Extract common code, reduce repetition |
-| complexity | Simplify complex functions, reduce nesting |
-
-## Output Format
-
-### Dry Run
-```
-[dev:refactor src/utils.go --dry-run]
-
-┌─ Agent: lang-golang-expert (sw-engineer)
-├─ Skill: go-best-practices
-└─ File: src/utils.go
-
-Analysis:
-
-[Structure] Lines 10-45
-  Issue: Function too long (35 lines)
-  Suggest: Extract helper functions
-
-[Naming] Line 12
-  Issue: Abbreviation in function name
-  Found: func procData()
-  Suggest: func processData()
-
-[Patterns] Lines 20-30
-  Issue: Repeated error handling pattern
-  Suggest: Create handleError() helper
-
-Proposed Changes:
-  1. Extract lines 15-25 into validateInput()
-  2. Rename procData → processData
-  3. Create handleError() helper function
-
-No changes made (dry-run mode).
-Run without --dry-run to apply changes.
-```
-
-### Apply Changes
-```
-[dev:refactor src/utils.go]
-
-┌─ Agent: lang-golang-expert (sw-engineer)
-├─ Skill: go-best-practices
-└─ File: src/utils.go
-
-Refactoring:
-
-[1/3] Extracting validateInput()...
-  ✓ Created function at line 50
-  ✓ Updated calls at lines 15, 22
-
-[2/3] Renaming procData → processData...
-  ✓ Renamed function definition
-  ✓ Updated 3 call sites
-
-[3/3] Creating handleError() helper...
-  ✓ Created function at line 60
-  ✓ Replaced 5 error handling blocks
-
-Summary:
-  Changes applied: 3
-  Lines modified: 28
-  Functions added: 2
-  Functions renamed: 1
-
-Recommendation: Run tests to verify changes.
-```

package/templates/.codex/skills/dev-review/SKILL.md

@@ -1,81 +0,0 @@
----
-name: dev-review
-description: Review code against language-specific best practices
-argument-hint: "<file-or-directory> [--lang <language>]"
----
-
-# Code Review Skill
-
-Review code for best practices using language-specific expert agents.
-
-## Parameters
-
-| Name | Type | Required | Description |
-|------|------|----------|-------------|
-| path | string | yes | File or directory to review |
-
-## Options
-
-```
---lang, -l       Language (auto-detected if not specified)
-                 Values: go, python, rust, kotlin, typescript, java
---focus, -f      Focus area (style, performance, security, all)
---verbose, -v    Detailed output
-```
-
-## Workflow
-
-```
-1. Detect language (or use --lang)
-2. Select appropriate expert agent
-3. Load language-specific skill
-4. Analyze code against best practices
-5. Generate review report
-```
-
-## Agent Selection
-
-| File Extension | Agent | Skill |
-|----------------|-------|-------|
-| .go | lang-golang-expert | go-best-practices |
-| .py | lang-python-expert | python-best-practices |
-| .rs | lang-rust-expert | rust-best-practices |
-| .kt | lang-kotlin-expert | kotlin-best-practices |
-| .ts, .tsx | lang-typescript-expert | typescript-best-practices |
-| .java | be-springboot-expert | springboot-best-practices |
-| .jsx, .js (React) | fe-vercel-agent | react-best-practices |
-
-## Output Format
-
-```
-[dev:review src/main.go]
-
-┌─ Agent: lang-golang-expert (sw-engineer)
-├─ Skill: go-best-practices
-└─ File: src/main.go
-
-Review Results:
-
-[Style] Line 15
-  Issue: Variable name should be camelCase
-  Found: user_name
-  Suggest: userName
-
-[Error Handling] Line 42
-  Issue: Error not checked
-  Found: file.Close()
-  Suggest: if err := file.Close(); err != nil { ... }
-
-[Performance] Line 78
-  Issue: Inefficient string concatenation in loop
-  Found: str += item
-  Suggest: Use strings.Builder
-
-Summary:
-  Style: 1 issue
-  Error Handling: 1 issue
-  Performance: 1 issue
-  Total: 3 issues
-
-Recommendation: Fix error handling issues first.
-```