oh-my-customcode 0.12.1 → 0.12.3

package/templates/.codex/skills/lists/SKILL.md

@@ -1,78 +0,0 @@
----
-name: lists
-description: Show all available commands
-argument-hint: "[--category <category>] [--verbose]"
----
-
-# List Commands Skill
-
-Show all available commands with optional filtering and detailed information.
-
-## Options
-
-```
---verbose, -v    Show detailed descriptions
---category, -c   Filter by category (system, manager, dev)
-```
-
-## Output Format
-
-### Default
-```
-AI Agent System - Available Commands
-
-System:
-  lists              Show all available commands
-  status             Show system status
-  help               Show help information
-
-Manager:
-  /create-agent          Create a new agent
-  /update-docs           Sync documentation with project structure
-  /update-external       Update agents from external sources
-  /audit-agents          Audit agent dependencies
-  /fix-refs              Fix broken references
-
-Dev:
-  /dev-review        Review code for best practices
-  /dev-refactor      Refactor code
-
-Use "<command> --help" for detailed information.
-```
-
-### Verbose Output
-```
-lists --verbose
-
-AI Agent System - Available Commands (Detailed)
-
-System Commands:
-┌─────────┬──────────────────────────────────────────────┐
-│ Command │ Description                                  │
-├─────────┼──────────────────────────────────────────────┤
-│ lists   │ Show all available commands                  │
-│ status  │ Show system status and health checks         │
-│ help    │ Show help for commands and agents            │
-└─────────┴──────────────────────────────────────────────┘
-
-Manager Commands:
-┌──────────────────┬──────────────────────────────────────┐
-│ Command          │ Description                          │
-├──────────────────┼──────────────────────────────────────┤
-│ /create-agent    │ Create a new agent with structure    │
-│ /update-docs     │ Sync all docs with project state     │
-│ /update-external │ Update from external sources         │
-│ /audit-agents    │ Check dependencies and refs          │
-│ /fix-refs        │ Auto-fix broken references           │
-└──────────────────┴──────────────────────────────────────┘
-
-Dev Commands:
-┌──────────────┬────────────────────────────────────────┐
-│ Command      │ Description                            │
-├──────────────┼────────────────────────────────────────┤
-│ /dev-review  │ Review code against best practices     │
-│ /dev-refactor│ Suggest and apply refactoring          │
-└──────────────┴────────────────────────────────────────┘
-
-Total: 10 commands available
-```

package/templates/.codex/skills/memory-management/SKILL.md

@@ -1,195 +0,0 @@
----
-name: memory-management
-description: Memory persistence operations using claude-mem
-user-invocable: false
----
-
-## Purpose
-
-Provide memory persistence operations using claude-mem for session context survival across compactions.
-
-## Operations
-
-### 1. Save Context
-
-```yaml
-operation: save
-description: Store session context in claude-mem
-steps:
-  1. Collect session data:
-     - Tasks completed
-     - Decisions made
-     - Open items
-     - Key code changes
-  2. Format document:
-     - Add project tag: "my-project"
-     - Add session ID: {date}-{uuid}
-     - Add relevant tags
-  3. Store in claude-mem:
-     - Use chroma_add_documents
-     - Include metadata
-```
-
-### 2. Recall Context
-
-```yaml
-operation: recall
-description: Search and retrieve relevant memories
-steps:
-  1. Build query:
-     - Always prefix with "my-project"
-     - Add user-provided search terms
-     - Include date for temporal searches
-  2. Search claude-mem:
-     - Use chroma_query_documents
-     - Request top N results
-  3. Format results:
-     - Sort by relevance
-     - Present summary
-     - Provide access to full content
-```
-
-### 3. Get Specific Memory
-
-```yaml
-operation: get
-description: Retrieve specific memory by ID
-steps:
-  1. Use chroma_get_documents with ID
-  2. Return full document content
-```
-
-## Query Patterns
-
-### Semantic Search (Primary)
-
-```python
-# Always include project name
-chroma_query_documents(["my-project {search_terms}"])
-
-# Examples:
-chroma_query_documents(["my-project authentication flow"])
-chroma_query_documents(["my-project 2025-01-24 memory system"])
-```
-
-### Get by ID
-
-```python
-# When you have a specific document ID
-chroma_get_documents(ids=["document_id"])
-```
-
-## Document Format
-
-### Save Format
-
-```yaml
-content: |
-  ## Session Summary
-  Date: {date}
-  Session: {session_id}
-
-  ### Tasks Completed
-  - Task 1: Description
-  - Task 2: Description
-
-  ### Decisions Made
-  - Decision 1: Rationale
-  - Decision 2: Rationale
-
-  ### Open Items
-  - Item 1: Status
-  - Item 2: Status
-
-  ### Notes
-  Additional context...
-
-metadata:
-  project: my-project
-  session: {date}-{uuid}
-  tags: [session, task, decision, ...]
-  created_at: {timestamp}
-```
-
-### Recall Response Format
-
-```yaml
-results:
-  - id: doc_1
-    score: 0.95
-    summary: "Authentication flow implementation"
-    date: 2025-01-20
-    tags: [authentication, oauth]
-  - id: doc_2
-    score: 0.87
-    summary: "JWT token decision"
-    date: 2025-01-18
-    tags: [authentication, decision]
-```
-
-## Best Practices
-
-### Query Tips
-
-```yaml
-do:
-  - Always include "my-project" prefix
-  - Use semantic, intent-based queries
-  - Include dates for temporal searches
-  - Use multiple queries for better coverage
-
-dont:
-  - Use complex where filters ($and, $or)
-  - Omit project name
-  - Use overly generic terms
-  - Expect exact string matching
-```
-
-### Save Tips
-
-```yaml
-do:
-  - Include meaningful tags
-  - Write clear summaries
-  - Capture decisions with rationale
-  - Note open items for future reference
-
-dont:
-  - Save trivial conversations
-  - Include sensitive data (API keys, etc.)
-  - Create duplicate entries
-```
-
-## Integration
-
-### With sys-memory-keeper Agent
-
-```
-sys-memory-keeper agent uses this skill for:
-- sys-memory-keeper:save command
-- sys-memory-keeper:recall command
-- PreCompact hook
-- SessionStart hook
-```
-
-### With Other Agents
-
-```
-Other agents can trigger memory operations via:
-- Direct sys-memory-keeper:save/recall commands
-- Delegating to sys-memory-keeper
-```
-
-## Error Handling
-
-```yaml
-save_errors:
-  - Connection failure: Retry 3 times, then log and continue
-  - Invalid format: Validate before save, report issues
-  - Storage full: Archive old memories, then retry
-
-recall_errors:
-  - No results: Suggest alternative queries
-  - Connection failure: Return empty with warning
-  - Invalid query: Help user reformulate
-```

package/templates/.codex/skills/memory-recall/SKILL.md

@@ -1,152 +0,0 @@
----
-name: memory-recall
-description: Search and recall memories from claude-mem
-argument-hint: "<query> [--recent] [--limit <n>]"
----
-
-# Memory Recall Skill
-
-Search and recall relevant memories from claude-mem using semantic search.
-
-## Parameters
-
-| Name | Type | Required | Description |
-|------|------|----------|-------------|
-| query | string | yes* | Search query (*not required with --recent) |
-
-## Options
-
-```
---recent, -r     Recall most recent memories
---limit, -l      Maximum results to return (default: 5)
---verbose, -v    Show full memory content
---date, -d       Filter by date (YYYY-MM-DD)
-```
-
-## Workflow
-
-```
-1. Build semantic query
-   ├── Prefix with "my-project"
-   ├── Add user query terms
-   └── Include date if specified
-
-2. Search claude-mem
-   └── chroma_query_documents
-
-3. Format results
-   ├── Sort by relevance score
-   ├── Show summary for each
-   └── Provide memory IDs for detailed access
-
-4. Present to user
-```
-
-## Query Tips
-
-```yaml
-effective_queries:
-  - "authentication flow" (topic-based)
-  - "2025-01-20 oauth" (temporal + topic)
-  - "decision jwt" (type + topic)
-  - "agent creation workflow" (semantic intent)
-
-avoid:
-  - Single generic words like "code" or "task"
-  - Very long queries (keep it focused)
-  - Special characters or complex syntax
-```
-
-## Output Format
-
-### Basic Search
-```
-[sys-memory-keeper:recall authentication]
-
-Searching memories for: "my-project authentication"
-
-Found 3 relevant memories:
-
-[1] mem_abc123 (Score: 0.95)
-    Date: 2025-01-20
-    Summary: Implemented OAuth flow with Google provider
-    Tags: [authentication, oauth, google]
-
-[2] mem_def456 (Score: 0.87)
-    Date: 2025-01-18
-    Summary: JWT token decision - RS256 algorithm
-    Tags: [authentication, decision, jwt]
-
-[3] mem_ghi789 (Score: 0.82)
-    Date: 2025-01-15
-    Summary: Authentication architecture discussion
-    Tags: [authentication, architecture, planning]
-
-Use "sys-memory-keeper:recall --verbose" for full content.
-```
-
-### Verbose Output
-```
-[sys-memory-keeper:recall authentication --verbose]
-
-Searching memories for: "my-project authentication"
-
-[1] mem_abc123 (Score: 0.95)
-    Date: 2025-01-20
-    Tags: [authentication, oauth, google]
-
-    Content:
-    ## Session Summary
-    Date: 2025-01-20
-
-    ### Tasks Completed
-    - Implemented OAuth flow with Google provider
-    - Added callback handler for OAuth response
-    - Created user session management
-
-    ### Decisions Made
-    - Use passport.js for OAuth handling
-      Rationale: Well-maintained, good documentation
-
-    ---
-
-[2] mem_def456 (Score: 0.87)
-    ...
-```
-
-### Recent Memories
-```
-[sys-memory-keeper:recall --recent]
-
-Fetching recent memories for: my-project
-
-[1] mem_xyz999 (Score: 1.00)
-    Date: 2025-01-24
-    Summary: Memory system Phase 1 implementation
-    Tags: [session, memory, phase1]
-
-[2] mem_xyz888 (Score: 0.98)
-    Date: 2025-01-23
-    Summary: Agent identification rules update
-    Tags: [session, rules, enforcement]
-
-...
-```
-
-### No Results
-```
-[sys-memory-keeper:recall "nonexistent topic"]
-
-Searching memories for: "my-project nonexistent topic"
-
-No memories found matching your query.
-
-Suggestions:
-- Try different keywords
-- Use broader search terms
-- Check available memories with "sys-memory-keeper:recall --recent"
-```
-
-## Related
-
-- memory-save - Save current context

package/templates/.codex/skills/memory-save/SKILL.md

@@ -1,126 +0,0 @@
----
-name: memory-save
-description: Save current session context to claude-mem
-argument-hint: "[--tags <tags>] [--include-code]"
-disable-model-invocation: true
----
-
-# Memory Save Skill
-
-Save current session context to claude-mem for persistence across context compaction.
-
-## Options
-
-```
---tags, -t       Additional tags for the memory
---include-code   Include code changes in the save
---summary, -s    Custom summary (otherwise auto-generated)
---verbose, -v    Show detailed save information
-```
-
-## Workflow
-
-```
-1. Collect session context
-   ├── Tasks completed
-   ├── Decisions made
-   ├── Open items
-   └── Code changes (if --include-code)
-
-2. Format with metadata
-   ├── project: my-project
-   ├── session: {date}-{uuid}
-   ├── tags: [session, ...user_tags]
-   └── created_at: {timestamp}
-
-3. Store in claude-mem
-   └── chroma_add_documents
-
-4. Report result
-```
-
-## Storage Format
-
-```yaml
-project: my-project
-session: {date}-{uuid}
-tags: [session, task, decision]
-content:
-  summary: Brief description of session context
-  tasks_completed: List of completed tasks
-  decisions: Key decisions made
-  open_items: Unfinished work
-```
-
-## Output Format
-
-### Success
-```
-[sys-memory-keeper:save]
-
-Saving session context...
-
-Context collected:
-  Tasks: 3 completed
-  Decisions: 2 recorded
-  Open items: 1 pending
-
-Metadata:
-  Project: my-project
-  Session: 2025-01-24-a1b2c3d4
-  Tags: [session, task, decision]
-
-[Done] Session context saved successfully.
-Memory ID: mem_abc123
-```
-
-### With Tags
-```
-[sys-memory-keeper:save --tags "authentication,oauth"]
-
-Saving session context...
-
-Metadata:
-  Project: my-project
-  Session: 2025-01-24-a1b2c3d4
-  Tags: [session, task, decision, authentication, oauth]
-
-[Done] Session context saved successfully.
-Memory ID: mem_abc123
-```
-
-### Verbose
-```
-[sys-memory-keeper:save --verbose]
-
-Collecting session context...
-
-Tasks Completed:
-  1. Implemented OAuth flow
-  2. Added JWT token validation
-  3. Created authentication middleware
-
-Decisions Made:
-  1. Use RS256 for JWT signing
-     Rationale: Better security for distributed systems
-  2. Token expiry: 1 hour
-     Rationale: Balance security and user experience
-
-Open Items:
-  1. Refresh token implementation
-     Status: In progress
-
-Saving to claude-mem...
-
-Document content:
-  ## Session Summary
-  Date: 2025-01-24
-  ...
-
-[Done] Session context saved.
-Memory ID: mem_abc123
-```
-
-## Related
-
-- memory-recall - Search and recall memories

package/templates/.codex/skills/monitoring-setup/SKILL.md

@@ -1,115 +0,0 @@
----
-name: monitoring-setup
-description: Enable/disable OpenTelemetry console monitoring for Codex usage tracking
-argument-hint: "[enable|disable|status]"
----
-
-# Monitoring Setup Skill
-
-Enable or disable OpenTelemetry console monitoring. When enabled, Codex outputs usage metrics (cost, tokens, sessions, LOC, commits, PRs, active time) and events (tool results, API requests) to the terminal.
-
-## Natural Language Triggers
-
-This skill activates when the user mentions any of:
-- Korean: "모니터링", "텔레메트리", "사용량 추적", "메트릭", "모니터링 켜줘", "텔레메트리 활성화"
-- English: "monitoring", "telemetry", "usage tracking", "metrics", "enable monitoring"
-- Combined with actions: "켜", "끄", "활성화", "비활성화", "설정", "enable", "disable", "setup"
-
-## Commands
-
-### enable (default)
-
-1. Read `.codex/settings.local.json` (create if not exists)
-2. Add or update `env` field with:
-   ```json
-   {
-     "env": {
-       "CLAUDE_CODE_ENABLE_TELEMETRY": "1",
-       "OTEL_METRICS_EXPORTER": "console",
-       "OTEL_LOGS_EXPORTER": "console"
-     }
-   }
-   ```
-3. Preserve all existing settings
-4. Report to user:
-   ```
-   [Done] OpenTelemetry Console Monitoring enabled
-
-   Configured in: .codex/settings.local.json
-   Metrics: sessions, cost, tokens, LOC, commits, PRs, active time
-   Events: tool results, API requests, tool decisions
-
-   Note: Takes effect on next `claude` session restart.
-   To disable: /monitoring-setup disable
-   ```
-
-### disable
-
-1. Read `.codex/settings.local.json`
-2. Remove OTel-related keys from `env`:
-   - `CLAUDE_CODE_ENABLE_TELEMETRY`
-   - `OTEL_METRICS_EXPORTER`
-   - `OTEL_LOGS_EXPORTER`
-3. If `env` object becomes empty, remove `env` field entirely
-4. Report:
-   ```
-   [Done] OpenTelemetry Monitoring disabled
-
-   Removed from: .codex/settings.local.json
-   Takes effect on next session restart.
-   ```
-
-### status
-
-1. Read `.codex/settings.local.json`
-2. Check for OTel env vars
-3. Report current state:
-   ```
-   [Monitoring Status]
-   ├── Enabled: Yes/No
-   ├── Metrics exporter: console / otlp / none
-   ├── Logs exporter: console / otlp / none
-   └── Config: .codex/settings.local.json
-   ```
-
-## Implementation Notes
-
-- `settings.local.json` is NOT git-tracked (local to user)
-- Each user enables monitoring independently
-- No infrastructure required for console mode
-- Metrics appear in stderr during Codex execution
-- Default export interval: 60s for metrics, 5s for events
-
-## Available Metrics
-
-| Metric | Description | Unit |
-|--------|-------------|------|
-| `claude_code.session.count` | CLI sessions started | count |
-| `claude_code.cost.usage` | Session cost | USD |
-| `claude_code.token.usage` | Tokens used (input/output/cache) | tokens |
-| `claude_code.lines_of_code.count` | Code lines modified (added/removed) | count |
-| `claude_code.commit.count` | Git commits created | count |
-| `claude_code.pull_request.count` | Pull requests created | count |
-| `claude_code.active_time.total` | Active usage time | seconds |
-
-## Available Events
-
-| Event | Description |
-|-------|-------------|
-| `claude_code.tool_result` | Tool execution results with duration |
-| `claude_code.api_request` | API request details with cost/tokens |
-| `claude_code.api_error` | API error details |
-| `claude_code.tool_decision` | Tool accept/reject decisions |
-| `claude_code.user_prompt` | User prompt metadata (content redacted by default) |
-
-## Upgrade Path
-
-For production monitoring, upgrade from console to OTLP:
-
-```bash
-# In settings.local.json env:
-OTEL_METRICS_EXPORTER=otlp
-OTEL_LOGS_EXPORTER=otlp
-OTEL_EXPORTER_OTLP_PROTOCOL=grpc
-OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4317
-```