oh-my-customcode 0.12.1 → 0.12.3

package/templates/.codex/rules/MUST-sync-verification.md

@@ -1,125 +0,0 @@
-# [MUST] Sync Verification Rules
-
-> **Priority**: MUST - ENFORCED | **ID**: R016
-
-## Core Rule
-
-After modifying agents, skills, or guides: run full verification before committing AND pushing. Never ask to commit/push before `mgr-sauron:watch` passes.
-
-Every `git push` requires: `mgr-sauron:watch` → all pass → `git push`
-
-## Verification Phases
-
-### Phase 1: Manager Verification (5 rounds)
-
-| Round | Actions |
-|-------|---------|
-| 1-2 | mgr-supplier:audit, mgr-sync-checker:check, fix issues |
-| 3-4 | Re-verify + mgr-updater:docs, fix remaining |
-| 5 | Final: all counts match, frontmatter valid, skill refs exist, memory scopes valid, routing patterns updated |
-
-Also run: mgr-claude-code-bible:verify (official spec compliance)
-
-### Phase 2: Deep Review (3 rounds)
-
-| Round | Focus |
-|-------|-------|
-| 1 | Workflow alignment: routing skills have complete agent mappings |
-| 2 | References: no orphans, no circular refs, valid skill/memory refs |
-| 3 | Philosophy: R006 separation, R009 parallel, R010 delegation, R007/R008 identification |
-
-### Phase 3: Fix all discovered issues
-
-### Phase 4: Commit via mgr-gitnerd
-
-### Phase 5: Push via mgr-gitnerd (only after sauron passes)
-
-## Self-Check Before Commit and Push
-
-```
-╔══════════════════════════════════════════════════════════════════╗
-║  BEFORE COMMITTING, ASK YOURSELF:                                ║
-║                                                                   ║
-║  1. Did I complete all 5 rounds of manager verification?         ║
-║  2. Did I complete all 3 rounds of deep review?                  ║
-║  3. Did I fix ALL discovered issues?                             ║
-║  4. Are all counts matching across all sources?                  ║
-║  5. Am I delegating to mgr-gitnerd for the commit?               ║
-║                                                                   ║
-║  If NO to ANY → DO NOT COMMIT                                    ║
-╚══════════════════════════════════════════════════════════════════╝
-
-╔══════════════════════════════════════════════════════════════════╗
-║  BEFORE PUSHING, ASK YOURSELF:                                   ║
-║                                                                   ║
-║  1. Did mgr-sauron:watch complete successfully?                  ║
-║  2. Were ALL issues from sauron verification fixed?              ║
-║  3. Am I delegating to mgr-gitnerd for the push?                 ║
-║                                                                   ║
-║  If NO to ANY → DO NOT PUSH                                      ║
-║                                                                   ║
-║  SAURON VERIFICATION IS MANDATORY FOR ALL PUSHES.                ║
-╚══════════════════════════════════════════════════════════════════╝
-```
-
-## When Required
-
-Any change to: agents, agent frontmatter, skills, guides, routing patterns, rules.
-
-## Quick Verification Commands
-
-```bash
-# Agent count check
-ls .codex/agents/*.md | wc -l
-
-# Skill count check
-find .codex/skills -name "SKILL.md" | wc -l
-
-# Frontmatter validation (check for missing YAML headers)
-for f in .codex/agents/*.md; do head -1 "$f" | grep -q "^---" || echo "MISSING FRONTMATTER: $f"; done
-
-# Check for agents with invalid skill references
-for f in .codex/agents/*.md; do
-  grep "^skills:" -A 10 "$f" | grep "  - " | sed 's/.*- //' | while read skill; do
-    [ -f ".codex/skills/$skill/SKILL.md" ] || echo "INVALID SKILL REF in $f: $skill"
-  done
-done
-
-# Routing skill pattern coverage
-grep -c "agent_patterns:" .codex/skills/secretary-routing/SKILL.md
-grep -c "agent_patterns:" .codex/skills/dev-lead-routing/SKILL.md
-grep -c "agent_patterns:" .codex/skills/qa-lead-routing/SKILL.md
-
-# Memory field validation
-for f in .codex/agents/*.md; do
-  mem=$(grep "^memory:" "$f" | awk '{print $2}')
-  if [ -n "$mem" ] && [ "$mem" != "project" ] && [ "$mem" != "user" ] && [ "$mem" != "local" ]; then
-    echo "INVALID MEMORY SCOPE in $f: $mem"
-  fi
-done
-
-# Hook count check
-ls .codex/hooks/*.json 2>/dev/null | wc -l
-
-# Context count check
-ls .codex/contexts/*.md 2>/dev/null | wc -l
-
-# Guide count check
-find guides -mindepth 1 -maxdepth 1 -type d | wc -l
-
-# Agent name accuracy (compare AGENTS.md table with actual files)
-# Extract agent names from files
-ls .codex/agents/*.md | xargs -I{} basename {} .md | sort > /tmp/actual-agents.txt
-
-# Slash command skill existence
-for cmd in $(grep "^| \`/" AGENTS.md | sed 's/.*`\///' | sed 's/`.*//' | sed 's/ .*//')
-do
-  [ -d ".codex/skills/$cmd" ] || echo "MISSING SKILL: $cmd"
-done
-
-# Routing skill completeness check
-ls -d .codex/skills/*-routing 2>/dev/null | xargs -I{} basename {} | sort
-
-# Verify routing skill names in AGENTS.md
-grep -oP '(secretary|dev-lead|de-lead|qa-lead)-routing' AGENTS.md | sort -u
-```

package/templates/.codex/rules/MUST-tool-identification.md

@@ -1,82 +0,0 @@
-# [MUST] Tool Usage Identification Rules
-
-> **Priority**: MUST - ENFORCED | **ID**: R008
-
-## Core Rule
-
-Every tool call MUST be prefixed with agent and model identification:
-
-```
-[agent-name][model] → Tool: <tool-name>
-[agent-name][model] → Target: <file/path/url>
-```
-
-For parallel calls: list ALL identifications BEFORE the tool calls.
-
-### Common Violations to Avoid
-
-```
-❌ WRONG: Calling tools without identification
-   "먼저 JD 내용을 확인하겠습니다."
-   <tool_call>WebFetch(...)</tool_call>
-
-❌ WRONG: Missing model in identification
-   [secretary] → Tool: WebFetch
-   [secretary] → Fetching: https://example.com/jd.md
-
-✓ CORRECT: Always identify with agent AND model
-   "먼저 JD 내용을 확인하겠습니다."
-   [secretary][reasoning] → Tool: WebFetch
-   [secretary][reasoning] → Fetching: https://example.com/jd.md
-   <tool_call>WebFetch(...)</tool_call>
-
-❌ WRONG: Parallel calls without listing all identifications
-   <tool_call>WebFetch(url1)</tool_call>
-   <tool_call>WebFetch(url2)</tool_call>
-   <tool_call>Bash(cmd)</tool_call>
-
-✓ CORRECT: List all identifications with models, then call
-   [secretary][reasoning] → Tool: WebFetch
-   [secretary][reasoning] → Fetching: url1
-   [secretary][reasoning] → Tool: WebFetch
-   [secretary][reasoning] → Fetching: url2
-   [secretary][reasoning] → Tool: Bash
-   [secretary][reasoning] → Running: cmd
-   <tool_call>WebFetch(url1)</tool_call>
-   <tool_call>WebFetch(url2)</tool_call>
-   <tool_call>Bash(cmd)</tool_call>
-```
-
-## Models
-
-| Model | Use |
-|-------|-----|
-| `reasoning` | Complex reasoning, architecture |
-| `balanced` | General tasks, code generation (default) |
-| `fast` | Fast simple tasks, file search |
-
-## Tool Categories
-
-| Category | Tools | Verb |
-|----------|-------|------|
-| File Read | Read, Glob, Grep | Reading / Searching |
-| File Write | Write, Edit | Writing / Editing |
-| Network | WebFetch | Fetching |
-| Execution | Bash, Task | Running / Spawning |
-
-## Task Tool Format
-
-```
-Task(subagent_type):model → description
-```
-
-`subagent_type` MUST match actual Task tool parameter. Custom names not allowed.
-
-## Example
-
-```
-[mgr-creator][balanced] → Write: .codex/agents/new-agent.md
-[secretary][reasoning] → Spawning:
-  [1] Task(lang-golang-expert):balanced → Go code review
-  [2] Task(lang-python-expert):balanced → Python code review
-```

package/templates/.codex/rules/SHOULD-agent-teams.md

@@ -1,39 +0,0 @@
-# [SHOULD] Agent Teams Rules
-
-> **Priority**: SHOULD | **ID**: R017 | **Condition**: Agent Teams enabled locally
-
-## Detection
-
-Available when `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1` or TeamCreate/SendMessage tools present.
-
-## Decision Matrix
-
-| Scenario | Preferred |
-|----------|-----------|
-| Simple independent subtasks | Task Tool |
-| Multi-step with shared state | Agent Teams |
-| Research requiring discussion | Agent Teams |
-| Cost-sensitive batch ops | Task Tool |
-| Complex debugging across modules | Agent Teams |
-| Code review + fix cycle | Agent Teams |
-| Single file operations | Task Tool |
-
-**Self-check before Task tool:** Is Agent Teams available? Does task need 3+ agents, shared state, or inter-agent communication? If yes, use Agent Teams.
-
-## Team Patterns
-
-- **Research**: researcher-1 + researcher-2 + synthesizer
-- **Development**: implementer + reviewer + tester
-- **Debug**: investigator-1 + investigator-2 + fixer
-
-## Lifecycle
-
-TeamCreate → TaskCreate → Task(spawn) → SendMessage(coordinate) → TaskUpdate → shutdown → cleanup
-
-## Fallback
-
-When Agent Teams unavailable: use Task tool with R009/R010 rules. Both approaches produce results; Agent Teams adds coordination richness.
-
-## Cost
-
-Agent Teams uses more tokens (full context per member + message passing). Use Task tool if task < 3 min or no inter-agent communication needed.

package/templates/.codex/rules/SHOULD-ecomode.md

@@ -1,37 +0,0 @@
-# [SHOULD] Ecomode Rules
-
-> **Priority**: SHOULD | **ID**: R013
-
-## Activation
-
-Auto-activates when: 4+ parallel tasks, batch operations, 80%+ context usage, or explicit "ecomode on".
-
-## Behaviors
-
-**Compact Output**: Agents return `status + summary (1-2 sentences) + key_data only`. Skip intermediate steps, verbose explanations, repeated context, full file contents.
-
-**Aggregation Format**:
-```
-[Batch Complete] {n}/{total}
-├── {agent}: ✓/✗/⚠ {summary}
-```
-
-**Compression**: File lists -> count only (unless < 5), error traces -> first/last 3 lines, code -> path:line ref only.
-
-## Config
-
-```yaml
-ecomode:
-  threshold: 4
-  result_format: summary
-  max_result_length: 200
-```
-
-## Example
-
-Normal: Full agent header + step-by-step analysis + detailed results.
-Ecomode: `[lang-golang-expert] ✓ src/main.go reviewed: 1 naming issue (handle_error -> handleError)`
-
-## Override
-
-Disable with: "ecomode off", "verbose mode", or "show full details".

package/templates/.codex/rules/SHOULD-error-handling.md

@@ -1,33 +0,0 @@
-# [SHOULD] Error Handling Rules
-
-> **Priority**: SHOULD | **ID**: R004
-
-## Error Classification
-
-| Level | Symptom | Response |
-|-------|---------|----------|
-| Warning | Task completes but needs attention | Output warning, continue |
-| Error | Current task fails, others possible | Stop task, report cause, suggest alternative |
-| Critical | Cannot proceed at all | Stop all, preserve state, report immediately |
-
-## Error Report Format
-
-```
-[Error] {type} — Location: {file:line} — Cause: {cause} — Impact: {effect}
-Attempted: 1. {try1} -> Failed  2. {try2} -> Failed
-Recommended: {action1}, {action2}
-```
-
-## Recovery
-
-| Type | Strategy |
-|------|----------|
-| Retryable | Retry up to 3x with backoff (1s, 2s, 4s), then report |
-| Non-recoverable | Save state, rollback if possible, detailed report, wait for user |
-
-## Validation
-
-| When | Checks |
-|------|--------|
-| Before action | Target exists, permissions available, dependencies met |
-| After action | Expected = actual, file integrity, no side effects |

package/templates/.codex/rules/SHOULD-hud-statusline.md

@@ -1,32 +0,0 @@
-# [SHOULD] HUD Statusline Rules
-
-> **Priority**: SHOULD | **ID**: R012
-
-## Format
-
-```
-─── [Agent] {name} | [Progress] {n}/{total} | [Parallel] {count} ───
-```
-
-## When to Display
-
-Multi-step tasks, parallel execution, long-running operations. Skip for single brief operations.
-
-## Hook Implementation
-
-Implemented in `.codex/hooks/hooks.json` (PreToolUse → Task matcher):
-
-```
-─── [Spawn] {subagent_type}:{model} | {description} ───
-─── [Resume] {subagent_type}:{model} | {description} ───
-```
-
-## Display with Parallel
-
-```
-─── [Agent] secretary | [Parallel] 4 ───
-  [1] Task(mgr-creator):balanced → Create agent
-  [2] Task(lang-golang-expert):fast → Code review
-```
-
-Integrates with R007 (Agent ID), R008 (Tool ID), R009 (Parallel).

package/templates/.codex/rules/SHOULD-interaction.md

@@ -1,34 +0,0 @@
-# [SHOULD] Interaction Rules
-
-> **Priority**: SHOULD | **ID**: R003
-
-## Response Principles
-
-| Principle | Do | Don't |
-|-----------|-----|-------|
-| Brevity | Key info first, answer only what's asked | Over-explanation, repetitive confirmation |
-| Clarity | Specific expressions, executable code | Abstract descriptions, "maybe"/"probably" |
-| Transparency | State actions, report changes, acknowledge uncertainty | Hide actions, present guesses as facts |
-
-## Status Format
-
-```
-[Start] {task name}
-[Progress] {current step} ({n}/{total})
-[Done] {task name} — Result: {summary}
-[Failed] {task name} — Cause: {reason} — Alternative: {solutions}
-```
-
-## Request Handling
-
-| Type | Action |
-|------|--------|
-| Clear | Execute immediately |
-| Ambiguous | `[Confirm] Understood "{request}" as {interpretation}. Proceed?` |
-| Risky | `[Warning] This action has {risk}. Continue? Yes: {action} / No: Cancel` |
-
-## Multiple Tasks
-
-- Dependent: Sequential
-- Independent: Parallel allowed
-- Report: `[Task 1/3] Done` / `[Task 2/3] In progress...` / `[Task 3/3] Pending`

package/templates/.codex/rules/SHOULD-memory-integration.md

@@ -1,39 +0,0 @@
-# [SHOULD] Memory Integration Rules
-
-> **Priority**: SHOULD | **ID**: R011
-
-## Architecture
-
-**Primary**: Native auto memory (`memory` field in agent frontmatter). No external dependencies.
-**Supplementary**: claude-mem MCP (optional, for cross-session search and temporal queries).
-
-Rule: If native auto memory can handle it, do NOT use claude-mem.
-
-## Native Auto Memory
-
-Agent frontmatter `memory: project|user|local` enables persistent memory:
-- System creates memory directory, loads first 200 lines of MEMORY.md into prompt
-- Read/Write/Edit tools auto-enabled for memory directory
-
-| Scope | Location | Git Tracked |
-|-------|----------|-------------|
-| `user` | `~/.codex/agent-memory/<name>/` | No |
-| `project` | `.codex/agent-memory/<name>/` | Yes |
-| `local` | `.codex/agent-memory-local/<name>/` | No |
-
-## When to Use claude-mem
-
-| Scenario | Native | claude-mem |
-|----------|--------|------------|
-| Agent learns project patterns | Yes | |
-| Search across sessions | | Yes |
-| Temporal queries | | Yes |
-| Cross-agent sharing | | Yes |
-
-## Best Practices
-
-- Consult memory before starting work
-- Update after discovering patterns
-- Keep MEMORY.md under 200 lines
-- Do not store sensitive data or duplicate AGENTS.md content
-- Memory write failures should not block main task

package/templates/.codex/rules/index.yaml

@@ -1,141 +0,0 @@
-# Global Rules
-# Priority: MUST > SHOULD > MAY
-
-rules:
-  # MUST - Never violate
-  - id: R000
-    name: language-policy
-    title: Language & Delegation Policy
-    path: ./MUST-language-policy.md
-    priority: MUST
-    scope: all
-
-  - id: R001
-    name: safety
-    title: Safety Rules
-    path: ./MUST-safety.md
-    priority: MUST
-    scope: all
-
-  - id: R002
-    name: permissions
-    title: Permission Rules
-    path: ./MUST-permissions.md
-    priority: MUST
-    scope: all
-
-  - id: R007
-    name: agent-identification
-    title: Agent Identification Rules
-    path: ./MUST-agent-identification.md
-    priority: MUST
-    scope: all
-
-  - id: R008
-    name: tool-identification
-    title: Tool Usage Identification Rules
-    path: ./MUST-tool-identification.md
-    priority: MUST
-    scope: all
-
-  - id: R009
-    name: parallel-execution
-    title: Parallel Execution Rules
-    path: ./MUST-parallel-execution.md
-    priority: MUST
-    scope: all
-
-  # Agent Design - MUST
-  - id: R006
-    name: agent-design
-    title: Agent Design Rules
-    path: ./MUST-agent-design.md
-    priority: MUST
-    scope: agents
-
-  # Orchestrator Coordination - MUST
-  - id: R010
-    name: orchestrator-coordination
-    title: Orchestrator Coordination Rules
-    path: ./MUST-orchestrator-coordination.md
-    priority: MUST
-    scope: agents
-
-  # Intent Transparency - MUST
-  - id: R014
-    name: intent-transparency
-    title: Intent Transparency Rules
-    path: ./MUST-intent-transparency.md
-    priority: MUST
-    scope: orchestrator
-
-  # Continuous Improvement - MUST
-  - id: R015
-    name: continuous-improvement
-    title: Continuous Improvement Rules
-    path: ./MUST-continuous-improvement.md
-    priority: MUST
-    scope: all
-
-  # Sync Verification - MUST
-  - id: R016
-    name: sync-verification
-    title: Sync Verification Rules
-    path: ./MUST-sync-verification.md
-    priority: MUST
-    scope: all
-
-  # SHOULD - Strongly recommended
-  - id: R003
-    name: interaction
-    title: Interaction Rules
-    path: ./SHOULD-interaction.md
-    priority: SHOULD
-    scope: all
-
-  - id: R004
-    name: error-handling
-    title: Error Handling Rules
-    path: ./SHOULD-error-handling.md
-    priority: SHOULD
-    scope: all
-
-  # Memory Integration - SHOULD
-  - id: R011
-    name: memory-integration
-    title: Memory Integration Rules
-    path: ./SHOULD-memory-integration.md
-    priority: SHOULD
-    scope: all
-
-  # HUD Statusline - SHOULD
-  - id: R012
-    name: hud-statusline
-    title: HUD Statusline Rules
-    path: ./SHOULD-hud-statusline.md
-    priority: SHOULD
-    scope: all
-
-  # Ecomode - SHOULD
-  - id: R013
-    name: ecomode
-    title: Ecomode Rules
-    path: ./SHOULD-ecomode.md
-    priority: SHOULD
-    scope: all
-
-  # Agent Teams - SHOULD
-  - id: R017
-    name: agent-teams
-    title: Agent Teams Rules
-    path: ./SHOULD-agent-teams.md
-    priority: SHOULD
-    scope: orchestrator
-
-  # MAY - Optional
-  - id: R005
-    name: optimization
-    title: Optimization Guide
-    path: ./MAY-optimization.md
-    priority: MAY
-    scope: all

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

@@ -1,56 +0,0 @@
----
-name: airflow-best-practices
-description: Apache Airflow best practices for DAG authoring, testing, and production deployment
-user-invocable: false
----
-
-# Apache Airflow Best Practices
-
-## DAG Authoring
-
-### Top-Level Code (CRITICAL)
-- Avoid heavy computation at module level (executed on every DAG parse)
-- Minimize imports at module level
-- Use `@task` decorator (TaskFlow API) for Python tasks
-- Keep DAG file under 1000 lines
-
-### Scheduling
-- Use cron expressions or timetables
-- Set `catchup=False` for most cases
-- Use data-aware scheduling (datasets) for dependencies
-- Configure SLA monitoring
-
-### Task Dependencies
-- Use `>>` / `<<` for clarity
-- Group related tasks with TaskGroup
-- Avoid deep nesting (max 3 levels)
-
-## Testing
-
-### Unit Tests
-- Test DAG import without errors
-- Detect cycles in dependencies
-- Mock external connections
-- Test task logic independently
-
-### Integration Tests
-- Use Airflow test mode
-- Validate end-to-end workflows
-- Test with sample data
-
-## Production Deployment
-
-### Performance
-- Lazy-load heavy libraries inside tasks
-- Use connection pooling
-- Minimize DAG parse time
-- Enable parallelism
-
-### Reliability
-- Set appropriate retries and retry_delay
-- Use SLA callbacks for monitoring
-- Implement proper error handling
-- Log important events
-
-## References
-- [Airflow Best Practices](https://airflow.apache.org/docs/apache-airflow/stable/best-practices.html)